What we store
Short version: the rides you record, the email address on your account, and a log of how the app and your trainer talked to each other. No body metrics, ever.
What leaves your device
Riding needs an account, and an account is an email address and a password. Signing in is the only step that needs a network: a session runs entirely in your browser, and the recording is kept there first.
When you are online, each ride is uploaded to your account, so your history follows you between devices. A ride that could not be uploaded stays on the device and goes up next time. The app tells you which happened at the end of every ride.
Two other things go up. The outcome of the readiness screen (cleared or not, which version of the questions, and the date) is kept against your account so a second device does not ask again. Your answers to the individual questions are not kept and are not sent. And after each ride a log of the app's conversation with the trainer is uploaded, so a ride that went wrong can be understood. It names the trainer's make, model and firmware and what was said over the link. It does not contain you.
What a ride contains
- Power, cadence, speed and heart rate as your trainer reported them, with timestamps.
- The running totals your trainer keeps for itself (distance covered, energy expended and its own clock), where it reports them. These are readings we cannot take again once a ride is over, so we keep what the machine said rather than working out our own version later.
- Which part of the session each moment belonged to.
- Which trainer it was, and whether that trainer measures power or calculates it.
- Any adjustment you made to the load, recorded as the adjustment you made.
What it does not contain is anything worked out from that. No scores, no derived load figures, no rating of the session. Those are opinions about a ride under one way of looking at it, and the ride itself outlives any of them.
What is never collected
Age, sex, weight and height are not collected anywhere in this product, and the software is built so they cannot be. There are no fields for them, and a test fails the build if one appears.
This is not a promise we are asking you to take on trust. It is a constraint on the code, and the reason is simple: data that is never collected cannot be lost, sold, subpoenaed or leaked.
Measurements of trainers
Separately from rides, the app has a survey tool for measuring what a trainer is and how its brake behaves. It is a bench instrument rather than part of riding: nothing on the ride path runs it, and it does nothing unless you go to it and start it.
What it sends is about the machine, not about you, but it does include the identifiers the machine publishes about itself, such as a serial number. The tool shows exactly what it sent, and it says so on the page before you run it.