Privacy policy
Last updated: 2026-08-19.
What we collect
Account data — your email, display name, password hash (managed by Supabase Auth), avatar, optional bio, and public handle. If you are subject to our age gate, we also store your date of birth and the timestamp it was verified, plus the version and timestamp of the Terms of Service and Privacy Policy you accepted, kept as proof of consent and re-collected whenever we change either document.
Adventure data — anything you log: vehicles, gear, adventures, locations, service records, pets. You own this. We never sell it.
Social and community data — if you use the public profile, groups, marketplace listings, comments, or follows, that content is visible to whoever the feature says it is visible to (for example, your profile-visibility setting).
Billing data — paid plans exist but checkout is not live yet; we have not enabled Stripe or any other payment processor in this deployment. Once it is live, subscribing will store your Stripe customer and subscription IDs and invoice records (amounts, dates, status). Your card details will go straight to Stripe and never touch our servers.
Connected-app data — if you link MuscleBuddy, we store the recovery and nutrition data it shares under the scopes you approved. If you instead grant MuscleBuddy read access to AdventureOS, we store which scopes you granted and when, never the access token MuscleBuddy uses, which is only ever kept as a one-way hash.
Credentials — if you add a certification (WFR/WFA, an avalanche level, a dive card, a pilot certificate, a medical, an inspection, and the like), we store its name, issuing body, identifier, and dates, plus a scanned card or other evidence file if you attach one. A credential is private by default; it appears on your public profile only if you explicitly mark it shared, and even then your profile-visibility setting still decides who can reach it.
Organization asset custody — if you belong to an organization that owns gear (a club trailer, radios, rental equipment), we store who currently holds each item, when they checked it out, when it is due back, and any condition notes recorded at handover.
Organization catalog and location claims — if an organization claims stewardship of a reference catalog entry or an official claim on a location, we store which organization made the claim, its review status, and any evidence it submitted in support.
Operational data — error logs and anonymous usage metrics (page views). If you accept the "Analytics" cookie category, Google Analytics (GA4) also collects this on our behalf; it never runs otherwise. If you accept the "Advertising" cookie category, Meta Pixel collects page views and device/browser details to measure our ad campaigns; it never runs otherwise, and neither runs while it is not configured for this deployment.
How we use it
To run the service: serve your data back to you when you sign in.
To improve the product: anonymous, aggregated usage trends inform what we build next.
To contact you about your account: sign-up verification, password resets, and magic-link sign-in emails, sent by Supabase Auth, our identity provider, rather than by us directly.
How long we keep it
Retention windows, by category. Anything not listed here is kept for as long as your account exists and deleted when it does — see “Delete” under Your rights.
Account, adventure and social data — kept for as long as your account exists.
Offline cached API responses, used to replay a mutation you made while offline so it cannot double-execute — 30 days from when we cached them, swept daily.
MuscleBuddy OAuth handshake state, the short-lived authorization codes and link requests either direction of the MuscleBuddy connection generates mid-flow — kept only until they expire, whether or not the flow ever completed, swept daily.
Billing records, meaning Stripe invoice history and webhook-processing records — kept indefinitely, for accounting and fraud-prevention obligations.
Audit logs — kept indefinitely, as the record of security-relevant account actions.
Connected recovery and nutrition data from MuscleBuddy — kept for as long as the connection is active, and deleted immediately when you disconnect it.
The crons that enforce the swept windows above are recorded in this repository’s data retention register, apps/server/src/lib/retention-register.ts, which is checked in CI to name every job that bulk-deletes data.
Children’s privacy
AdventureOS is not directed to children, and we do not knowingly collect personal information from anyone under 13. Sign-up requires a date of birth, and an account that fails that age check is blocked outright rather than created and restricted. If we learn that we have collected information from a child under 13, we will delete it. If you believe a child under 13 has an account or has otherwise provided us information, email privacy@adventureos.net and we will investigate and remove it.
Your rights
Access — your adventure data is visible throughout the app wherever you logged it: vehicles and gear in your library, sessions and adventures in each module.
Export — download a complete, machine-readable copy of your account from Settings → Privacy & data while signed in.
Delete — erase your account from Settings → Privacy & data while signed in. Deletion removes your profile, adventure data, connected-app grants and sign-in identity immediately; it is not reversible and there is no grace period. Content other members are reading — comments, articles, marketplace listings, group events — stays up credited to “Deleted user” rather than being removed from their threads.
Correct — edit your name, handle, avatar, bio and profile visibility from Settings → Profile. For anything else that is wrong, email privacy@adventureos.net.
Contact
Privacy questions: privacy@adventureos.net.