Run Ragged Ltd ("we", "us", "our"), a company registered in England and Wales and based in Devon, UK, operates the Run Ragged mobile application (the "App"). This policy explains what information the App accesses, how it's used, and your rights over it.
If you have questions about this policy, contact us at hello@runragged.app.
Run Ragged is designed to keep your data on your device wherever possible. Your health data, profile details, and training history are never sent to us — they stay on your device and in your own private iCloud account.
Three optional features are the exception, because they cannot work without a server: live run sharing, Raggamuffins (group distance challenges), and the in-app feedback form. Each only sends data when you actively choose to use it, and each is described in detail in section 2 below. None of them is on by default.
The third parties involved are Apple (for Health, Calendar, Notifications, iCloud sync, and processing App Store payments), RevenueCat (for managing subscriptions), OneSignal (for optional workout reminder notifications), Supabase (the hosting provider for the three features above), Open-Meteo and OpenStreetMap (for weather and map lookups, described in 2.13), and Strava (only if you choose to connect a Strava account).
2.1 Apple Health (HealthKit)
With your permission, the App reads workout data from Apple Health, including running workouts (distance, duration, pace, splits), heart rate data associated with your runs, GPS route data associated with your runs, and calories/elevation data where available.
If you record a run using the Run Ragged Apple Watch app, the App also writes that workout to Apple Health — the run itself (distance, duration, heart rate, calories) and its GPS route — so your runs are saved to your own permanent Health record alongside workouts from any other app. This is the only data the App writes to Apple Health.
Health data read from or written to Apple Health is processed and stored locally on your device, and is used to display your stats, generate training plans, and let you share your own run summaries. It is not transmitted to us, except where you explicitly choose to use one of the optional features described in 2.7 to 2.10 below.
2.2 Profile information
You may optionally enter a name, date of birth, weight, height, and gender, and choose a profile photo. This information is stored locally on your device and used only to personalise BMI calculations, fuelling guidance, and training plan generation. It is not sent to us or shared with any third party.
2.3 Calendar
With your permission, the App can add your training plan sessions to your device calendar so you can see upcoming workouts alongside the rest of your schedule. This creates a calendar on your device; we do not access or read your existing calendar entries beyond what's needed to add and manage these events.
2.4 Notifications
The App can schedule local notifications to remind you of upcoming workouts. These are generated and scheduled entirely on your device, with no data sent anywhere.
Separately, if you turn on the optional "Reminders" setting in your Profile, the App uses OneSignal, a third-party push notification service, to send you a reminder if you haven't logged a run in a while. This requires OneSignal to assign your device an anonymous identifier (created automatically whenever the App is used, regardless of whether Reminders is turned on) and to receive the date of your most recent run, so it knows when a reminder is due. OneSignal does not receive your name or any other health or profile data. OneSignal's own privacy policy governs how they handle this information, available at onesignal.com/privacy_policy.
2.5 Subscription and payment information
Subscriptions are processed through the Apple App Store and managed using RevenueCat, a third-party subscription management platform. Apple processes your payment directly — we never see or store your payment card details. RevenueCat receives purchase/transaction information (such as your subscription status and an anonymised app-specific identifier) in order to validate your subscription and unlock premium features. RevenueCat's own privacy policy governs how they handle this information, available at revenuecat.com/privacy.
2.6 iCloud Sync
If you're signed into iCloud on your device, the App uses Apple's iCloud Key-Value Storage to back up your Profile settings, your active training plan, and any race results you've logged manually, so this information isn't lost if you lose or replace your device. This uses your own private iCloud account — Run Ragged has no access to this data, and it is governed by Apple's own iCloud terms and privacy policy.
2.7 Live run sharing
If you choose to share a run, the App creates a tracking link and sends the following to our server (hosted by Supabase): a runner label (the name you've set in your Profile, so recipients know whose run they're watching), your current GPS position, elapsed time and distance, and your miles/kilometres preference. Position updates continue for as long as the run is active. A trail of the positions recorded during the share is also stored, so the tracking page can draw your route rather than just a moving dot.
Anyone who has the link can view that run's live position while the share is active — the link itself is the only thing required, so treat it as you would any private link and send it only to people you trust. Each share stops being viewable four hours after it is created, or as soon as you end the run. The share and its position trail are then permanently deleted from our servers — within about an hour of you ending the run, and in all cases within four hours and fifteen minutes of it being created. We do not keep an archive of where you have run.
This is the only feature that transmits your location to us, it is never on by default, and it only ever runs when you explicitly start a share.
2.8 Safety Contacts
With your permission, you can pick up to three contacts from your device's address book to use as Safety Contacts for the sharing feature above. Their names and phone numbers are stored on your device (and, if iCloud Sync is on, in your own private iCloud account). They are never sent to us or to any third party. When you share a run, the App pre-fills your device's own messaging app with those recipients and the tracking link — you send the message yourself, from your own phone number, and we have no involvement in or record of it.
2.9 Raggamuffins (group distance challenges)
If you create or join a Raggamuffins challenge, the following is stored on our server (Supabase): the challenge's name, goal distance and dates, the display name of whoever created it, and, for each participant, a display name and the total distance they have covered towards the goal. Display names are visible to everyone else in that challenge — that's the point of a shared leaderboard — so choose a name you're comfortable sharing. No health data, route data, or individual run details are sent; only a running distance total.
2.10 In-app feedback form
If you send feedback or a feature suggestion through the App's Help screen, we receive your message, the category you chose, your app and iOS version, the name from your Profile, and an email address if (and only if) you choose to provide one for a reply. This is stored on our server (Supabase) and triggers an email to us so we can read and respond to it. Nothing is sent unless you actively submit the form.
2.11 Strava
Connecting a Strava account is entirely optional, and is offered so that runs recorded by other devices (such as a Garmin watch) can have their GPS routes matched to your runs. If you connect, you authorise Run Ragged through Strava's own login page — we never see your Strava password. The authorisation step passes through our server so that our application secret is not embedded in the App itself. Your Strava access tokens are stored on your device, and the activity data retrieved is used only to match routes to your existing runs. You can disconnect at any time in Profile, and revoke access from your Strava account settings. Strava's own privacy policy governs their handling of your data.
2.12 Location
The App uses your location on your Apple Watch, to record the GPS route of a run (saved to Apple Health as described in 2.1), and on your iPhone, with your permission, to find parkrun events near you and to look up local weather. Location is only transmitted to our server if you use live run sharing (2.7). It is also sent to the third-party weather and map services described in 2.13, which is how those features work at all — see that section for exactly what each one receives.
2.13 Weather and map lookups
Several features need to know what the weather is doing where you are or where you ran — current conditions on your Dashboard, the Golden Window's forecast-aware scheduling, and heat-adjusted pace for past runs. To provide these, the App sends the relevant coordinates to Open-Meteo, a third-party weather service. This happens for your current area and for the locations of past runs.
Separately, the Challenge Generator's route-based missions (for example "cross three bridges") need to know what map features exist near where you ran. To check this, the App sends a bounding box — a rectangle covering roughly the area of your run, not the route itself — to the OpenStreetMap Overpass API.
Neither service receives your name, your identity, or any other information about you, and neither is used for advertising or tracking. Both are queried directly from your device; we do not receive or store the results.
We do not operate analytics, advertising, or tracking services within the App. We do not sell, rent, or share your personal data with third parties for marketing purposes. We do not require you to create an account, and we have no way to identify you across devices.
We do not have access to your HealthKit data, profile details, calendar contents, Safety Contacts, or training history — these remain on your device and in your own private iCloud account. The only information that reaches our servers is what you actively send by using live run sharing, Raggamuffins, or the feedback form, each described in section 2 above.
Because your health, profile, and training data is stored locally on your device rather than on our servers, deleting the App from your device will delete this data (subject to Apple Health's own data retention, which is managed independently through the Health app). Calendar events created by the App will remain in your device calendar until you delete them manually. Data backed up via iCloud Sync (see 2.6) is stored in your own iCloud account and persists there independently of the App being deleted, subject to Apple's own iCloud data retention and your own iCloud storage management.
Data held on our servers. The three features described in 2.7, 2.9 and 2.10 store data with us. Live shares and their position trails are deleted automatically, by a scheduled job that runs every fifteen minutes — roughly an hour after you end a run, and in all cases within four hours and fifteen minutes of the share being created. No manual request is needed, and nothing about your location is kept afterwards. Raggamuffins challenge records and feedback submissions are retained, so that challenges remain viewable to the people taking part and so we can follow up on what you've told us.
Because the App has no user accounts, we cannot identify which records belong to you from within the App itself. Live shares need no request — they delete themselves as described above. If you would like a challenge entry or feedback submission removed, email us at hello@runragged.app with enough detail to identify it (for example the challenge name, or the date and rough content of your message) and we will delete it.
Run Ragged is not directed at children under the age of 13, and we do not knowingly collect personal information from children.
If you are in the UK or EU, you have rights under UK GDPR / GDPR, including the right to access, correct, or delete personal information, and the right to lodge a complaint with the UK Information Commissioner's Office (ico.org.uk) if you believe your data has been mishandled. Because Run Ragged does not hold your personal data on our servers, most of these rights are exercised directly through your device (e.g. via the Health app's own privacy controls, or by deleting the App).
We may update this policy from time to time, for example if we introduce new features that change how data is handled. We'll update the "last updated" date above when we do.