Data privacy
A privacy checklist for athletes and coaches
What to look for before you connect your health, route, wearable, or coach-sharing data to any training app.
Data privacy context
Privacy guidance is still training guidance.
Consent, imports, and sharing controls all lead back to real athlete data and real training decisions.
Start with consent and only what you need
Before an app asks for your health, motion, location, or wearable data, it needs to tell you why. And it needs to ask for as little as it can get away with.
That is how we approach it. Our public copy separates your personal planning data from what a coach can see, and we never imply we are quietly passing your raw health streams around.
Route detail is not performance summary
Route data can reveal where you live, where you work out, and when you are usually out. A good coach or team dashboard can show you completion, missed sessions, readiness buckets, and upcoming workload — without ever showing exact GPS coordinates.
Same idea for social features. Friends and coaches probably need different levels of context, and your private notes stay private unless you decide otherwise.
Consent controls
Privacy controls have to stay visible.
Athletes and coaches can make better decisions when consent, sharing, and data boundaries remain inspectable.
API access is a moving target
Wearable and social APIs change. Strava lays out OAuth requirements, Garmin has an approval and licensing process for health data, and Apple emphasizes HealthKit privacy controls.
That is why we cite sources and dates on our integration copy — so you know when we checked, and what kind of data flow we described.