The MotoJournal is built for riders, not data extraction.

The platform stores the account, profile, billing, motorcycle, ride, journal, review, message, notification, support, content, community, and integration records needed to run the features you use.

Examples include your name, email, username, profile image, profile biography, social links you choose to publish, motorcycles in your garage, maintenance notes, rides, journal entries, goals, settings, messages, notifications, support tickets, content subscriptions, supporter status, and audit records for important account actions.

Your data is used to provide the MotoJournal product: profile pages, journaling, ride intelligence, garage records, community features, content feeds, messaging, notifications, support, billing, and your account settings.

We may use aggregated operational information to understand whether the platform is working, to prevent abuse, to improve features, and to plan development. This is not a license to sell or package your personal data for advertising.

Google sign-in is used only to confirm who you are. Calendar and Drive access are separate choices you make from settings, and you can remove them at any time.

Map and weather services may receive the location or route details needed to show maps, forecasts, travel time, and rider weather insight. Sponsors do not receive those details.

Browser GPS and imported GPX files can contain precise start, end, and route coordinates. A route stays in MotoJournal as a private record unless you choose another audience. Map, routing, or weather providers receive only the location details needed for the request you initiate; their processing is governed by their own policies.

Beacon sharing starts only after you review its audience, profile visibility, update interval, expiry, and pinned-place shield. Successful pings are retained as part of the Beacon session so the active state and safety history can be explained. Browser background updates are best-effort and may pause when a device locks.

Turning Beacon off ends new sharing immediately. The pinned-place shield reduces exposure near a saved sensitive place, but it is not a guarantee of anonymity and should be reviewed before every session.

Public profile fields and content marked public can be visible on the open web. Member, friend, group, and private audiences are enforced separately. Blocking prevents contact and discovery according to the safety controls; muting hides activity without notifying the other person.

Reports, moderation records, and limited audit evidence may be retained to protect riders and document decisions even after the reported content is hidden.

Supporter subscriptions are processed by Stripe. The MotoJournal stores subscription status, contribution amount, customer linkage, entitlement state, and billing event evidence. Card details are handled by Stripe, not stored directly in MotoJournal records.

Public supporter recognition is optional where applicable. You can manage billing and recognition preferences from account settings.

You can manage your profile, display preferences, notification preferences, content preferences, billing, cloud connections, and public profile information from your settings. You can revoke Google cloud connections from cloud settings and your Google Account.

Some records, such as audit logs, billing event evidence, support history, moderation history, and security records, may be retained where needed for platform integrity, safety, fraud prevention, accounting, or legal obligations.

You can download a machine-readable account export from Your Data settings. Account deletion is scheduled with a 14-day cancellation window so an accidental request is recoverable; the page explains any records that must be retained.

Journal entries, rides, motorcycles, and other supported records moved to Recently Deleted are recoverable for 30 days. Account deletion removes or de-identifies ordinary canonical records after the cooling-off period, while minimal security, financial, consent, moderation, and legal evidence may be retained for the applicable obligation.

Private journal entries stay private. Including an entry in a retrospective and allowing an AI-assisted reflection are separate choices. AI work is reviewable and does not silently publish, edit, or share canonical journal records.

When an AI-assisted feature is used, the interface identifies the evidence being considered and the generated result remains a proposal until you or an authorized human reviews it. AI job logs retain bounded operational evidence without granting the model permission to mutate canonical records.

Support tickets can include the page path you deliberately attach, uploaded evidence, and the description you provide. Secret-shaped query values such as reset tokens, OAuth codes, invite codes, signatures, passwords, and keys are removed before support context is stored. You can review the full ticket and its status from Support.

Use the support page to ask a privacy question, request help with your account, or report a concern. This policy will evolve as The MotoJournal grows, but the core boundary remains the same: the platform exists for riders, not for harvesting rider data.