Data & Privacy
How Coach Watts handles your training data, health information, and privacy rights.
Coach Watts processes training, health, and nutrition data to provide AI coaching. This page summarizes what we collect and your controls.
For the full legal terms, see our Privacy Policy and Terms of Service.
What we collect
| Category | Examples | Source |
|---|---|---|
| Account | Email, name, timezone | Sign-up and profile |
| Training | Workouts, power, pace, GPS, TSS | Strava, Garmin, Intervals.icu, uploads |
| Health | HRV, sleep, resting HR, weight | Oura, WHOOP, Garmin, Withings, Fitbit |
| Nutrition | Calories, macros, meals | Manual entry, Yazio |
| AI interactions | Chat messages, recommendations | In-app Chat, Telegram, MCP |
Health data consent
During onboarding, you explicitly consent to health data processing. Without this consent, AI coaching features that depend on biometrics remain limited.
You can review consent status in your account settings.
Who can see your data
| Access | Who |
|---|---|
| You | Full access to all your data |
| Connected coaches | Athletes you invite via coach codes |
| OAuth apps | Third-party apps you authorize (with scoped permissions) |
| MCP clients | AI tools you connect (e.g., Cursor) — revocable from Settings → Apps |
Coaches cannot access your data without your explicit invite. You can revoke coach access at any time.
Data controls
- Export — available in Settings → Danger Zone
- Delete account — permanently removes your data
- Revoke integrations — disconnect any app from Settings → Apps
- Revoke coach access — from Coaching → My Coaches
- Revoke MCP/OAuth — from Settings → Apps
How AI uses your data
The AI coach accesses your training history, recovery metrics, plans, and nutrition to generate recommendations and analysis. Data is processed to provide coaching — not sold to third parties.
Chat conversations are persisted to maintain context across sessions. See Interacting with your AI Coach.
Security
- OAuth tokens are encrypted at rest
- API access requires authentication and scoped permissions
- Webhook payloads require secret verification for developer apps
Questions
Contact us via the Help Center or review the full Privacy Policy.