Start with consent and the minimum data
Before an app asks for your health, motion, location or wearable data, it needs to tell you why. It also needs to ask for as little as it can.
That's our approach too. Our public copy keeps your personal planning data separate from what a coach can see, and nothing in it suggests we pass your raw health streams around.
Routes reveal more than performance
Route data can show where you live, where you train and when you're usually out. A good coach or team dashboard can show completion, missed sessions, readiness buckets and upcoming workload without a single exact GPS coordinate.
The same goes for social features. Friends and coaches probably need different amounts of context, and your private notes stay private unless you choose to share them.
Privacy controls have to stay visible.
Athletes and coaches can make better decisions when consent, sharing, and data boundaries remain inspectable.
Integration rules keep changing
Wearable and social APIs change. Strava sets out OAuth requirements, Garmin has an approval and licensing process for health data, and Apple puts HealthKit privacy controls up front.
That's why our integration pages cite sources and dates, so you can see when we checked and which data flow we were describing.