Privacy Notice
How Masters Run handles your training and health data
Masters Run is a wellness-focused training guidance platform for runners. It is not a medical device, and the data you connect is used to support coaching-style recommendations, not diagnosis or treatment.
What data the app stores
The platform stores account details, connected integration status, training activities, health metrics, training plans, uploaded biomechanics records, and recommendation audit snapshots needed to explain how daily guidance was produced.
What the data is used for
Imported data is used to calculate training guidance, readiness context, plan adherence, source freshness, and support review. The current platform does not use imported training or health data to train external AI models.
Retention
Activity, health, biomechanics, and recommendation records follow the rolling 12-month retention window unless a shorter operational purge is required for an incident or user deletion request.
Your controls
You can disconnect integrations, clear specific imported datasets where supported, and delete your account from Settings. Account deletion removes the associated records and linked integrations for that user.
Connected sources
Strava is the primary activity source when connected. Activities are received via real-time webhooks. We request read-only access (scopes: read, activity:read_all, profile:read_all) and never modify your Strava data. Disconnect removes all Strava-derived data immediately.
Garmin provides activity data and optional health metrics (HRV, sleep, stress) when connected. Data is synced daily. Garmin's API terms permit retention for the reasonable operation of the application.
Striv provides optional supplementary biomechanics data from uploaded session files. The uploaded files are not stored - only the extracted biomechanics records are retained.
How we handle Strava data
When you connect your Strava account, we read your running activities, heart rate streams, and training zones via the Strava API. This data is processed on arrival into derived analytics metrics - training load scores, heart rate zone distributions, pace statistics, and injury risk calculations. We do not retain raw Strava API responses beyond a short processing window. The derived analytics metrics are retained within our 12-month rolling retention window to enable trend analysis. When you disconnect Strava, all Strava-derived data is immediately and permanently deleted from our systems, and your OAuth token is revoked with Strava. We request read-only access to your Strava account and never modify your Strava data.
AI-powered insights
Our AI features generate natural-language training narratives using pre-computed analytics scores such as risk levels, readiness scores, and threshold comparisons. Raw activity data from connected platforms is never provided to AI models. No user data of any kind is used to train, fine-tune, or improve AI models. AI features use inference only - generating text from structured analytics input, similar to a template engine with natural language output.
Your data, your control
Your training data originates from your devices and platforms. We store derived analytics computed from this data to provide you with training insights. You can disconnect any integration at any time, which immediately deletes all data from that source. You can delete your account entirely from Settings, which removes all associated records. We never sell, share, or expose your data to other users - each account is fully isolated.
Last updated: March 2026