Privacy Policy
Last updated: 29 September 2026
In short
Runnr handles data differently depending on the features you choose:
- The running app works without an account. By default, your routes, runs and history stay on your phone. When you sign in or connect a fitness service, only the information needed for the feature you choose is synced.
- Connected fitness services are optional. Strava receives only the Runnr runs for which you have enabled uploads. A future Garmin connection will only become active if you approve it.
- The social side requires an account. What you publish, comment on and like is stored on a server, because other people are meant to see it. That is the entire point of sharing.
We do not sell data and we do not show ads inside Runnr. We use Meta App Events to measure whether Runnr's own ads lead to an install, onboarding completion, trial or subscription. Advertising identifiers are used only with your consent.
Data controller
Runnr, Denmark. Contact: support@runnr.dk.
If you have questions about how we handle your information, write to us. We reply within 30 days.
Part 1: Without an account
Location
Runnr uses your position to build routes that start where you are, to follow the route as you run, and to give spoken guidance.
- Your position is shown and processed on the phone.
- When you generate a route, a starting point and a target distance are sent to our own routing server in Denmark (Hetzner, Falkenstein). The server calculates the route and answers. The request is not tied to you and is not kept as a profile.
- Without an account, your GPS trace stays on the phone. When you are signed in, completed runs recorded and verified by Runnr, including distance, time and GPS trace, are synced to your Runnr account so history and leaderboards can follow you across devices. A run is not made public unless you choose to share it.
- Maps are provided by Mapbox. To draw the map around you, Mapbox sends your location and a random device identifier to their servers, where it is also used for their own analytics. You can turn that analytics off inside the app: tap the ⓘ in the corner of the map. Mapbox' processing is covered by Mapbox' privacy policy. The watch and a few older views still use Apple MapKit, covered by Apple's privacy policy.
You can decline location access. The app still works, you just cannot get routes from where you are.
Saved routes and runs
Generated routes, saved runs, distances, times, pace and your streak are stored locally on the device. When you are signed in, runs recorded and verified by Runnr are also synced to your account. You can delete local data individually or all at once under Settings. Runnr excludes routes, runs and temporary sharing images from Android cloud backup.
Health and runs from other apps
On iPhone, Runnr can—with your permission—read sleep, resting heart rate, heart rate variability, body mass and workouts from Apple Health and write runs to it. On Android, Runnr can—with your permission—read workouts, routes and selected workout metrics from Health Connect and write exercise, route, distance and active calories to it.
Information read directly from Apple Health or Health Connect is processed on the device. Imported runs and other health data are not automatically sent to Runnr Social, Strava, Garmin Connect or other third parties. Access is controlled in your phone settings and can be withdrawn at any time.
Usage statistics
The iPhone app uses Google Firebase Analytics to see how the app is used: how many people build a route, how many run it, and where things go wrong. The current Android app does not use Firebase Analytics. Analytics are not linked to your name or email.
Both apps use Meta App Events for a limited set of advertising events: app activation, completed onboarding, paywall view, checkout start, free trial and subscription. We do not send your name, email, Firebase ID, location, GPS traces or health data to Meta. On iPhone, IDFA is used only if you allow it through Apple's App Tracking Transparency prompt. On Android, the advertising ID remains disabled until you choose Allow in Runnr's own prompt. You can later change this choice under Settings → Privacy and data → Measure Runnr ads. If you decline or turn measurement off, the advertising ID is not used.
Purchases
Payment is handled by the Apple App Store on iPhone and Google Play on Android. We never see your card details. We receive a purchase identifier or receipt and store subscription status on your profile so Runnr can provide premium access across your devices.
Reminders
Run reminders are local notifications scheduled by the phone itself. We send no push messages, and we cannot see whether you open them.
Part 2: Connected fitness services
Connecting a fitness service is optional. It requires a Runnr account and your explicit consent with the selected service. You can disconnect the service again in Runnr.
Strava: When you connect Strava and enable automatic uploads, Runnr sends new runs recorded directly in Runnr to Strava. The transfer may include the activity name and type, start time, duration, distance, GPS trace and elevation data. Runnr does not retrieve your existing Strava history, and runs imported from Apple Health, Health Connect, Garmin Connect or other services are not automatically forwarded to Strava.
Garmin Connect: Runnr may offer a direct Garmin Connect connection in the future. It is not active until you connect your Garmin account and approve the specific permissions. The connection may be used to receive selected activities, including time, type, duration, distance, GPS trace, elevation, heart rate and cadence when available, and to send a route or course that you select in Runnr to Garmin Connect and a compatible Garmin device. Garmin data is not automatically forwarded to Strava.
To maintain a connection, we may store the service user ID and display name, the permissions you granted, connection settings, and encrypted access and refresh tokens in Supabase in the EU. If you disconnect Strava, access is revoked and the connection details are deleted by Runnr. If you disconnect Garmin, tokens and Garmin data received by Runnr through the connection are deleted. Activities or routes already stored by Strava or Garmin remain there until you delete them with the relevant service.
Part 3: With an account (the social side)
With an account you can publish routes, follow others, like and comment. Accounts are created with Sign in with Apple or Sign in with Google. We receive your name and email address from the provider, plus a user ID. If you use Apple's Hide My Email, we only ever see the relay address.
What we store
- Profile: name, username, bio, city, profile picture, and when you last started a run (so others can see that someone is running, never where).
- Posts: title, description, tags, artwork and the route's actual geography. Publishing a route publishes its path, which can reveal where you run and where you start. A rounded city point (about 1 km) is also stored for search.
- Actions: likes, saved posts, comments, follows and friend requests, and the fact that you completed a route.
- Moderation: reports you submit, users you block, and, if it becomes necessary, that an account has been banned and why.
This data is held by Supabase on servers in the EU (Stockholm). Profile pictures are stored in the same place.
Runnart: images you upload
When you build a figure from a photo, the image is sent to our server in Denmark and on to OpenAI, which first checks it for inappropriate content and then redraws it as line art.
- The photo is not stored by us. Only the finished figure, the line itself, is kept on your account.
- If an image is rejected, it is not stored - only the fact that something was rejected.
- Do not upload pictures of other people without their consent.
Profile pictures
A profile picture is checked by OpenAI for inappropriate content before it is uploaded. If the check cannot be completed, the image is rejected. Approved images are stored in Supabase and are publicly accessible, because they appear next to your posts.
Text you write
Titles, descriptions, tags, name, username, bio and comments are sent to OpenAI's moderation service before they become public. The text is used only to decide whether it can be published.
When you ask for a route in words
If you type or say a route request - "10 km past the harbour" - the text is sent to our server in Denmark and on to OpenAI, which turns it into settings: distance, route profile, surface and place names. The name of the town you are in is sent along with the text, so "the harbour" can become your harbour rather than a random one. The town is derived on your phone from your location; no coordinates are sent. We do not store the text, and we only count how many requests you have used of your monthly allowance.
If you speak the request instead of typing it, the speech recognition happens on your phone. The recording never leaves the device - only the finished text is sent on.
Legal bases
- Contract (GDPR art. 6(1)(b)): account, profile, posts, likes, comments, follows and subscription. This is the service you asked for.
- Consent (art. 6(1)(a), and art. 9(2)(a) for health): location, health data, photos, photo library access, connected fitness services and use of an advertising identifier for Meta measurement. You give it in the system or service dialogs. Meta consent can be withdrawn under Settings → Privacy and data in Runnr; other permissions can be changed in your phone's settings or by disconnecting the selected service.
- Legitimate interests (art. 6(1)(f)): moderation, abuse prevention, security, debugging and aggregate usage statistics. Our interest is keeping a public feed decent and the app running.
- Legal obligation (art. 6(1)(c)): accounting and responding to lawful requests from authorities.
Who receives your information?
We do not sell data. We use these processors and suppliers:
- Apple (Ireland/USA): App Store, payment, maps, Sign in with Apple.
- Google / Firebase / Google Play (Ireland/USA): sign-in, iPhone usage statistics, Android distribution and payment.
- Meta Platforms (Ireland/USA): measuring and optimising Runnr's own ads using the limited app events described above.
- Supabase (EU, Stockholm): database, file storage and encrypted connection details.
- Hetzner (Germany): our routing server and figure service.
- Mapbox (USA): map display. Receives your location and a random device identifier.
- OpenAI (USA): moderation of text and images, redrawing of Runnart artwork, and turning your route requests into settings.
- Strava: receives activity data only when you connect Strava and ask Runnr to send runs there. Strava processes the information under the Strava Privacy Policy.
- Garmin: if you connect Garmin Connect, Runnr receives the activities you approved and Garmin receives the routes you choose to send. Garmin processes the information under the Garmin Connect Privacy Policy.
Transfers outside the EU/EEA: Depending on the service, Google, Apple, Meta, Mapbox, OpenAI, Strava and Garmin may process data outside the EU/EEA. They describe their processing locations and transfer safeguards in their own privacy policies. Where Runnr itself makes a transfer, we use a lawful transfer mechanism, such as the European Commission's Standard Contractual Clauses or, where applicable, the EU-US Data Privacy Framework.
Anything you publish on the social side can be seen by other users - and for posts set to "Everyone", by anyone who opens the app, including people without an account.
How long do we keep it?
- Local data: until you delete it or delete the app.
- Account and posts: for as long as you have an account.
- Strava and Garmin: tokens and connection settings are kept only while the connection is active. Garmin data received through the connection is deleted when you disconnect or withdraw consent.
- Deleted posts: marked as deleted immediately and gone for everyone. The row is purged within 90 days.
- Reports and bans: up to 2 years, so that repeat offences can be recognised as a pattern. This is necessary for moderation to work at all.
- Usage statistics: according to Firebase's standard retention, at most 14 months.
- Purchase records: 5 years under Danish bookkeeping law. Handled by Apple or Google depending on where you purchased.
Deleting your account
You can delete your account in the app under Profile → Delete account. This deletes your profile, synced runs, the local copy of account runs, posts, comments, likes, saved posts and associated images. Disconnect connected fitness services in Runnr settings before deleting the account; this revokes access and deletes the tokens and connection details held by Runnr. If you have already deleted the account without disconnecting a service, contact support@runnr.dk. Data already sent to Strava or Garmin must be deleted with the relevant service. Generated routes and runs recorded without signing in are kept and can be deleted under Settings. If you no longer have access to the app, use our account deletion page.
Your rights
Under the GDPR you have the right of access, rectification, erasure, restriction, data portability, and to object to processing based on legitimate interests. Where you have given consent, you can withdraw it at any time without affecting the lawfulness of processing already carried out.
Write to support@runnr.dk. Much of it you can do yourself, immediately, in the app: edit your profile, delete posts, delete your account, delete local data.
If you are unhappy with how we handle your information, you can complain to the Danish Data Protection Agency, Datatilsynet, Carl Jacobsens Vej 35, 2500 Valby, Denmark, datatilsynet.dk.
Children
The social side is not intended for children under 13, and you must be at least 13 to create an account. If you are under 18, a parent or guardian must have accepted the terms. If we become aware of an account created by a child under 13, we delete it.
Security
All traffic is encrypted. Access to the social database is governed by row-level rules, so your account can only touch its own data. OAuth tokens for connected fitness services are encrypted on the server. Keys with elevated privileges exist only on our servers, never in the app.
Changes
If we change this policy, the date at the top is updated. You will be told about significant changes in the app before they take effect.