Privacy Policy

Cadence predicts how a race's distance and climbing will actually feel for your own fitness, and tracks whether that prediction held up once you've raced it. This policy covers exactly what the app and its backend collect to do that, and nothing else.

Last updated October 30, 2026

Information we collect

Account information. If you create an account: your email address, first and last name, and a securely hashed password (manual sign-up), or, for Sign in with Apple/Google, a stable identifier from Apple or Google confirming who you are, never your Apple/Google password. You can use Cadence without an account; some data then stays only on your device.

Fitness data. Benchmarks you type in (critical power/FTP, pace splits, max heart rate, longest run/ride, body weight) and the optional "How hard did you go?" answer after a race result. Earlier versions of Cadence offered a data connection; it has been removed, and the activity data it stored on our servers has been deleted. Figures it had already filled in stay in your profile, labelled “Synced earlier”. This is the one dataset the whole prediction model runs on.

Race data. Which races you've saved or registered for, any course file (GPX) you upload for one, and the result you confirm after race day (actual finish time vs. our predicted range), used to keep predictions calibrated over time.

Location. If you grant permission, your device's location is used once per session to sort Discover's race list by real distance. We don't store a location history.

Usage analytics. Anonymous product-usage events (e.g. that a race was added, a result was confirmed, a plan was upgraded) via TelemetryDeck, tied only to an anonymous per-device identifier, never your email, name, account id, or any race name, search text, or chat message you've typed.

Messages you send us. If you use the contact form on the Support page or send feedback from the app, we receive the name, email address and message you give us, plus the app version and device model that feedback includes. When you ask for a platform we do not support yet (for example COROS or Garmin), the app sends only the platform name, with nothing that identifies you.

Payment information. Subscription purchases go through Apple's own In-App Purchase system. We never see or store your card details; only whether a purchase is currently active, which we verify directly against Apple's systems on your device.

How we use it

  • To generate your race predictions and keep them accurate (fitness + race + course data).
  • To let you sign in and sync your data across devices (account information).
  • To sort races by real proximity, once, per session (location).
  • To understand how the app is actually used and improve it (anonymous analytics, never to identify you).
  • To process your subscription (handled by Apple; we only read the resulting entitlement).

We never sell your data.

Sharing a GPX-derived elevation profile

If you're signed in and upload a GPX file for a race with no elevation data yet, the elevation figures it contains (not the file itself, and nothing about you) may be cached and shown to other athletes viewing the same race, the same way an organizer's own published course data would be. Internally we keep a record of which account contributed it, visible to no other user, solely so you can remove your own contribution later (Clear, in the app). An anonymous upload is never shared this way.

Third parties we work with

  • Apple / Google: only to verify your identity for Sign in with Apple/Google, and to process In-App Purchases (Apple).
  • TelemetryDeck: anonymous product-usage analytics (see above).
  • Resend: the email service that sends account-confirmation emails and delivers support messages to our inbox, so it handles your email address and message text for that purpose only.
  • Public race-listing and course-data sources (RunSignup/BikeSignup, RaceRoster, RideWithGPS, Gran Fondo Guide, provincial cycling associations, OpenTopography, and similar): we query these for public race and course information; we do not send them anything about you.
  • Weather services: race-day weather for predictions. We send only a race's approximate location and date, never anything about you. Forecasts come from the US National Weather Service, from Environment and Climate Change Canada for Canadian races (contains information licensed under the Open Government Licence – Canada), and from MET Norway everywhere else (based on data from MET Norway, licensed CC BY 4.0); typical weather for races further out comes from NASA POWER.
  • Render: our hosting provider, running our database and server.

Security

Passwords are hashed, never stored in plain text. Sessions are server-side and revocable (signing out, or changing your password, invalidates them immediately), not a token that stays valid until it expires on its own.

Your choices

  • Export. Settings → Your Data → Export gives you a real copy of your account data, synced app state, and race-prediction history.
  • Delete. Settings → Your Data → Delete Account permanently removes your account and the data above; Delete everything clears what is stored on your device.
  • Correct anything. Every fitness field has a "this looks wrong" / manual-correction path in Profile.

Children

Cadence is not directed at children under 13 (or the minimum age in your country, if higher), and we don't knowingly collect data from them.

Changes to this policy

If this policy changes in a way that matters, we'll make that clear in the app before it takes effect.

Contact

Questions about this policy: jjcetinkayatri@gmail.com