No data harvesting
The MotoJournal is not built to sell private rider data, journal entries, garage records, ride logs, messages, or location history.
Loading your MotoJournal…
The MotoJournal is being built slowly, intentionally, and independently for riders who care about maintaining themselves, their motorcycles, and their connection to the motorcycle community.
For People. Not a Business Model.
I didn't create The MotoJournal to harvest data, track users' movements, upsell data packages, target people with content, ads, or bait users for more screen time and engagement.
I built TMJ for the greater good of the motorcycle community, and for people with a shared passion for maintaining themselves as well as their motorcycles.
K.
Creator of The MotoJournal.
The MotoJournal is not built to sell private rider data, journal entries, garage records, ride logs, messages, or location history.
Features should help riders reflect, learn, maintain their motorcycles, find useful information, and build real-world connection.
Brand support does not buy access to private user data, rider information, location data, journals, messages, garage records, or targeting infrastructure.
The MotoJournal exists because it is useful to people who ride, write, maintain, reflect, and want a calmer place to keep the motorcycle parts of their life together.
The platform should be funded in ways that keep it accountable to members. That means member support, transparent sponsor involvement where appropriate, and no hidden exchange of private rider information.
If any brand is involved from a funding perspective, that involvement should be public, limited, and for the good of the community. It should never become access to private user data or a targeting engine.
The MotoJournal is built and funded by @zenmotorcyclemaintenance with the intent to grow slowly, sustainably, and with mental health in mind.
Users should understand what they are sharing, what is private, what is public, and how to change those settings.
Maps, weather, Google, Stripe, OpenAI, and other integrations should support a clear MotoJournal feature and stay bounded to that purpose.
Policies, billing, support, and product choices should be explained in plain language instead of hiding behind platform jargon.
Growth should not come at the cost of founder burnout, poor safety decisions, or turning riders into product inventory.
Use the contact form for questions, feedback, ethical concerns, support ideas, or anything that should help keep the platform aligned with the people it exists to serve.