Runly
Privacy Policy
Effective 9 November 2026
Runly is committed to protecting your privacy. This policy explains what data we collect, how we use it, and your rights as a user. By using Runly, you agree to the practices described here.
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.
Before your first Ask Runly message is sent, Pro users are shown an explanation of this processing and asked to agree to sending their messages and relevant training and health data through Supabase to OpenAI. The coach is available only after you agree. Ask Runly does not send anything unless you use it and send a message. Dismissing or declining the prompt does not send that message.
Voice Coaching
Voice Coaching speaks pace, distance, and workout-segment announcements during a run. Before it is turned on, Runly explains this and asks you to agree. Only after you agree are the words of those announcements sent through Supabase to OpenAI so they can be spoken aloud. The audio plays on your device. Runly does not record your microphone.
Nothing is sent if you decline, if Voice Coaching is off, or before you agree. Turning Voice Coaching off withdraws that agreement and stops further announcements from being sent. This permission is separate from Ask Runly.
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.
Strava
If you connect Strava, Runly fetches your activities so they can be imported onto your device and matched to your plan. To keep the connection we store your Strava identifier and OAuth token on our server (Supabase). Those credentials are used only to request activities on your behalf. Disconnecting Strava in the app deletes them. A run summary from an imported activity is included in an Ask Runly request only when you send a coach message.
Subscriptions
Runly Pro is purchased from Apple. We use RevenueCat to check whether your subscription is active. RevenueCat receives an app user identifier and purchase information from Apple. It does not receive your health data, coach messages, or voice announcements. RevenueCat's privacy policy is available at: https://www.revenuecat.com/privacy.
Feedback
If you send feedback from Settings, the message you write is delivered through Kunio so we can read it. Kunio receives that message and the technical details needed to deliver it. It does not receive your health data, coach messages, or voice announcements unless you type them into the feedback yourself.
Usage & Analytics Data
We use PostHog's EU service for product analytics. Events include app lifecycle and feature interactions, onboarding progress and referral choices, and run start, completion and synchronization events. Event properties can include the run type, recording source and, for runs recorded in Runly, completed distance. The SDK also sends technical app and device information and a randomly generated identifier used to associate events from the same installation. These data are pseudonymous and are not limited to aggregated statistics.
We do not include coach messages, workout routes, heart-rate measurements or sleep samples in analytics events. PostHog's privacy policy is available at: https://posthog.com/privacy.
Crash Diagnostics
We use Firebase Crashlytics to diagnose app crashes. Reports can include crash stack traces, app and operating system versions, device information and a Crashlytics installation identifier. We do not attach coach messages, workout routes or health measurements to these reports. See Firebase's privacy information.
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
- Speak pace, distance, and segment announcements when Voice Coaching is on
- Import runs you choose to connect from Strava
- Show your run schedule in a calendar you choose to connect
- Check whether your Runly Pro subscription is active
- Read feedback you choose to send
- Improve app functionality using product analytics as described above
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 are sent to our server only when you send a coach message. Voice Coaching announcement text is sent only while Voice Coaching is on and you have agreed. Your run schedule, when calendar sync is on, is sent to our server (Supabase). Your training plan remains in your private iCloud container as well. OAuth credentials for Garmin, Strava and, if you connect it, Google Calendar are stored on that server and used only to keep the connection. Feedback you submit is stored by Kunio. Analytics data follows all applicable privacy regulations.
05Third-Party Services
| Service | Purpose | Data shared |
|---|---|---|
| Apple HealthKit | Read health & workout data | Read on your device. Run summaries are sent only when you send an Ask Runly message. Voice announcements are sent only while Voice Coaching is on and you have agreed |
| Apple iCloud / CloudKit | Store training plans | Your private iCloud container |
| Garmin Connect API | Sync workouts, push plans to device | See Garmin section |
| Strava API | Import activities you connect | OAuth token and Strava identifier on our server. Activities are fetched for your device. Disconnecting deletes the token |
| OpenAI | Write Ask Runly replies and speak Voice Coaching announcements | Coach requests only when you send a message. Announcement text only while Voice Coaching is on and you have agreed. OpenAI privacy policy |
| Supabase | Deliver coach requests, voice announcements, and the calendar feed | The coach request when you send a message, announcement text when Voice Coaching is on, the calendar schedule if you enable sync, and connection tokens |
| RevenueCat | Check whether Runly Pro is active | App user identifier and Apple purchase information. No health data, coach messages, or voice announcements. RevenueCat privacy policy |
| Kunio | Deliver feedback you send from Settings | The feedback message you write, and the technical details needed to deliver it |
| Apple Calendar, Google Calendar, Outlook | Subscribe to your run schedule | Calendar events as described above, only if you connect that calendar |
| PostHog (EU) | Product analytics | Pseudonymous installation identifier, app/device information and usage events as described above |
| Firebase Crashlytics | Diagnose app crashes | Crash reports, app/device information and a Crashlytics installation identifier |
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