Privacy Policy

01Information We Collect

Apple Health Data

With your permission, Runly reads data from Apple Health, including workouts, workout routes, heart rate, distance, active energy, sleep, heart-rate variability, resting heart rate, biological sex, and date of birth. Today's Form is calculated on your device. Workout routes stay on your device and are not uploaded.

When you use Ask Runly, the in-app coach, the question you type and a summary of your plan are sent to our server so a language model can reply. That summary can include your race, goal time, planned sessions, and, for recent recorded runs, distance, duration, pace, average heart rate, elevation gain, and calories. If the coach needs your readiness, it also sends last night's sleep and your heart-rate variability. It does not send workout routes, biological sex, date of birth, or HealthKit identifiers.

Training Plan & Race Data

Your races and training plans are stored in Apple's iCloud, in your private CloudKit container. A copy of the plan summary described above is sent with each Ask Runly question.

If you turn on calendar sync, the schedule of your runs is stored on our server so Apple Calendar, Google Calendar, or Outlook can subscribe to it. Each event includes the date, run type, and distance, plus the target pace and workout structure for a planned run, or the time and pace for a finished run. Calendar events do not include heart rate, routes, or HealthKit identifiers. You can turn sync off in the app, which removes that schedule from our server.

Garmin Connect Data

If you choose to connect your Garmin account, Runly integrates with the Garmin Connect API. See the dedicated Garmin Connect Integration section below for full details.

Usage & Analytics Data

We use Firebase to collect anonymized, aggregated usage statistics (e.g., feature interactions). This data cannot be used to identify individual users. Firebase's privacy policy can be accessed at: https://firebase.google.com/support/privacy/.

02How We Use Your Data

We use your data solely to:

• Generate personalized marathon and running training plans
• Display workout summaries and performance insights
• Push planned workouts to your Garmin device for on-device tracking
• Answer questions you ask in Ask Runly
• Show your run schedule in a calendar you choose to connect
• Improve app functionality based on anonymized analytics

We do not use your data for advertising or sell it to third parties.

03Garmin Connect Integration

This section describes specifically how Runly handles data obtained through the Garmin Connect Developer Program.

What Garmin data we access

When you connect your Garmin account, Runly accesses your activity data (workouts, runs, and related metrics) via the Garmin Connect API, and pushes planned training sessions from your Runly plan to your Garmin Connect account and Garmin devices so you can track them directly on your device.

How Garmin data is processed

Garmin activity data is used on your device to show run summaries and performance insights. The full activity is not stored on our servers. A run summary can be included in an Ask Runly request, as described in the next subsection.

How Garmin data is stored

Garmin activity data itself is not stored on Runly's servers. To maintain your Garmin connection, we store only your Garmin user identifier and OAuth authorization token on our backend (Supabase). These credentials are used solely to authenticate API requests on your behalf and are not used for any other purpose.

Third-party sharing of Garmin data

Runly does not share your Garmin data with advertising networks or analytics providers. The full Garmin activity, including its route, is not stored on our servers. If you ask the coach about a run that was imported from Garmin, the same summary shown in the app — distance, duration, pace, average heart rate, elevation, and calories — is included in that request and handled as described under Apple Health Data.

Revoking access and data deletion

You can disconnect your Garmin account at any time from within the app. Upon disconnection, your Garmin OAuth token and user identifier are deleted from our systems. Any Garmin activity data previously synced to Apple Health remains there under Apple's data management. You can remove it via the Apple Health app.

04Data Storage & Security

Workout routes and the Health samples used for Today's Form stay on your device. Ask Runly requests, and your run schedule when calendar sync is on, are sent to our server (Supabase). Your training plan remains in your private iCloud container as well. OAuth credentials for Garmin and, if you connect it, Google Calendar are stored on that server and used only to keep the connection. Analytics data follows all applicable privacy regulations.

05Third-Party Services

We do not use your data for advertising and we do not sell it.

06Your Rights (EU / GDPR)

If you are located in the EU or EEA, you have the right to:

• Access the personal data we hold about you
• Correct inaccurate data
• Request deletion of your data
• Restrict or object to processing
• Data portability

To exercise any of these rights, contact us at hello@getrunly.app.

07Policy Updates

We will notify you of material changes to this policy within the app. Continued use of Runly after an update constitutes acceptance of the revised policy.

08Contact

Email: hello@getrunly.app