Privacy
Last updated 20 July 2026.
RideSync plans motorcycle trips that start from your door — which means we hold a few sensitive things. Here is all of it, in plain words.
What we store
- Your account. Sign-in runs on Clerk; your email and name live there, not in our database. Our database keeps an opaque account id.
- Your rider profile. Your home base (the place your rides start from — set it as coarse as you like), riding skill, preferred surfaces, bike and budget preferences.
- Your trips. The plans you build — routes, waypoints, GPX files, version history — plus the rides you mark ridden, your ratings and any notes you add.
- How your buddy learns. Each build keeps a record of the request and the plan that came back, and the compute it used. That history is what tunes RideSync to your taste — it is only ever used for your account.
- What you tell your buddy. When you chat about a trip, or answer a question after a ride, we pick out lasting preferences — “keep days under 350km” — and keep them with your own words and the date, so future plans can say why they look the way they do. Working these out sends that message to the same AI provider that drafts your plans (currently Google). The preferences currently shaping your plans are listed on your profile, where you can switch off or correct any of them. Switching one off stops it affecting your plans; the underlying record stays in your history (deleting your account deletes the lot). Older or superseded ones stay in that history too, unused. They shape your plans only — never shared with another rider, never sent to analytics.
Where it goes
Your data lives in our database (Neon Postgres) in Sydney, Australia, hosted on Vercel — which keeps standard server logs, counts page views for us, and times how fast pages load (cookieless page counts, referrers and load speeds, never tied to your identity). To build a plan, parts of it reach the services that do the work:
- The AI that drafts your plan — your trip brief (including your home base and preferences) is sent to the model provider, currently Google (Gemini) and/or Anthropic (Claude), to produce your plan.
- Routing and geocoding — OpenRouteService receives the coordinates it routes between.
- Weather — Open-Meteo receives the coordinates it forecasts for.
- Email — Resend, if you opt into ride nudges by email, and to tell us that you asked for the app beta.
- The app beta — if you ask for a TestFlight or Play invite, your email address goes to Apple or Google so they can send it, and to us so we know to add you. Only the address, only if you ask, and only to the store you picked.
Road facts and points of interest come from OpenStreetMap, Wikivoyage and Wikidata — no personal data is involved in those lookups.
What we never do
- We never sell your data, and there are no ads.
- No tracking cookies — a session cookie keeps you signed in, and that’s it.
- Your location is never shown to another rider unless you explicitly share a trip — and a share link shows your departure only as a coarse region, never your home.
- That coarsening happens every time a link is opened, not once when you made it. So it covers links you shared long ago, and a fix reaches every link you have ever created.
- It applies to the words as well as the map — the day-by-day write-up is coarsened on the same read, not just the pins.
- The turn-by-turn file never leaves with a share link. A GPX is yours to download; someone opening your link cannot get it.
- Your home base never appears in analytics.
Your controls
- Edit or blank your profile any time.
- You can delete any trip in the app, permanently.
- Want everything gone? Email suren@kr8it.com and your account and its data will be deleted.
Changes
If this page changes, the date at the top changes with it. Questions — suren@kr8it.com.