Run Supreme privacy policy
Run Supreme is a running app with no account, no ads and no analytics of our own. This page says plainly what stays on your phone, what two outside services receive so the app can work, and what you can turn off.
1. Your runs stay on your phone unless you choose to send them
Everything Run Supreme records is stored on your device: your recorded route (GPS points), lap and rep times, pace, heart rate from a paired strap, the verdicts and trends the app computes from them, your settings, and any plan you follow. We do not run a server, we do not have an account for you, and we never see any of this.
Android's automatic backup may copy your run files to your Google account as part of your device backup, under Google's backup terms and your device settings. You can turn device backup off in Android settings. Files you export (JSON, TCX or GPX) go wherever you choose to send them.
Health Connect (Android's health data store) is one of those services. It is off by default. If you switch it on, or tap Send to Health Connect on a run, Run Supreme writes that run to Health Connect on your phone: the exercise session with its laps and pauses, the heart rate, the distance and, if you allow it, the route (without the first and last 200 m). Sending the same run again replaces it, never duplicates it. From there, the apps you allow in Health Connect can read it under their own policies. Run Supreme does not read anything from Health Connect.
Run detail has a Send button. It makes a TCX or GPX file of that run (the first and last 200 m of the route are left out) and opens Android's share sheet, so you pick the app that receives it. The Strava row only opens Strava's upload page in your browser; you upload the file yourself. Start's session card and a saved route have Send to watch: it makes a workout file (.fit) of the session, or a GPX course of the route, and opens the same share sheet. The course holds the whole route, including where it starts and ends, because a watch needs the full line to navigate it. Settings has a Send runs to section for services that can receive runs automatically. Every one is off by default, and a run goes to a service only after you switch it on. Once a file is with another app or service, that app's own privacy policy applies.
Intervals.icu (only if you connect it)
Intervals.icu receives data from Run Supreme only after you connect your own account: in Settings, Send runs to, you paste your personal API key and athlete id (both come from Intervals.icu, Settings, Developer settings). Nothing is sent to Intervals.icu before that, and nothing is sent for runs recorded before you switched it on. When it is connected, Run Supreme uploads a run's TCX file (route, lap times and heart rate, with the first and last 200 m of the route left out), the run's title, and the run's id, which Intervals.icu uses to refuse a second copy of the same run. You can also send a single run from its Send button. The key is stored in your phone's Android Keystore-backed secure storage, is sent only to Intervals.icu, is never written to logs, and is not part of Android's device backup. Settings, Send runs to, Intervals.icu, Manage connection, Disconnect deletes the key from the phone. Runs already uploaded stay in your Intervals.icu account, where Intervals.icu's own privacy policy applies; you can delete them there.
If Intervals.icu is connected, Send to watch can also add a planned workout to your Intervals.icu calendar, only when you tap Add for today or Add for tomorrow. That sends the session's name and steps (lengths, any heart rate or pace range, repeats), the date you chose, and an id that lets a second send replace the first. It contains no run, route or heart rate history. Intervals.icu then passes it on to the watch service you linked there (for example Garmin, COROS or Suunto), under their policies. Delete it from your Intervals.icu calendar to remove it.
Routes you follow
Start has a "Follow a route" choice for Free, Trail and Goal runs. You can pick a GPX or TCX file with Android's file picker, or turn one of your own past runs into a route. Run Supreme reads only the file you pick, on your phone, and keeps a simplified copy of the route (its points and, if the file has them, elevations) in the app's own storage. The file itself is not copied or sent anywhere, and nothing about the route leaves the phone: the distance left, the "off route" alert and the turn hints (worked out from the route's shape, not from any map or trail data) are all calculated on the phone, and the alert and hints are spoken by your phone's own voice. When you run a route, a copy of it, and how long you spent off it, is saved with that run's file, so run detail can show the route you meant against the one you ran; it goes wherever the run goes if you export it as JSON (a TCX or GPX Send carries only your own track). Saved routes are part of the app's stored data, so they are included in Android's automatic backup with your runs, and you can delete any of them from Start, Follow a route.
2. Google Maps
After a run, and during a run if you switch the record screen to MAP, Run Supreme draws your route on a Google map (for Free and Trail runs, Google's terrain map with its contour lines; a route you are following is drawn on top by Run Supreme, and is not sent to Google). The map is provided by the Google Maps SDK for Android, which runs inside the app and talks to Google directly to fetch map tiles. According to Google's own disclosure for this SDK, Google receives:
- your IP address (which gives an approximate location),
- a Maps SDK identifier that Google uses to count daily active users of the SDK,
- request metadata and crash data from the SDK,
- map interaction and camera events, which describe the map area you are viewing. Because the post-run map is zoomed in on your route, that map area amounts to a precise location. The live map during a run follows you, so while MAP is showing, the area Google receives is where you are at that moment.
In short: Google sees the map area you view and your IP address, like any maps app. Google does not receive your run file, your lap times or your heart rate from us. Google's handling of what it receives is covered by the Google Privacy Policy. The map loads when you open a run's detail screen, map images for your recent runs load from Google when Home shows them and are kept on your phone, and the map loads while MAP is selected on the record screen during a run. NUMBERS is the default, and no map loads while it is showing or while the screen is off. Run Supreme does not send your position to Google; Google only sees the map area the map asks for.
Offline maps
Offline maps you choose to download come from our map storage (Cloudflare); the download reveals which region you picked and your IP address, nothing else. Maps then work offline. Nothing else is sent with the download: no account, no device ID, no run data. Cloudflare sees the IP address the request comes from, as any web request does. Maps only download when you tap Download in Settings, under Offline maps.
3. Weather from Open-Meteo
To adjust for heat and humidity, Run Supreme can fetch the weather for each run from Open-Meteo. The request contains your run's location rounded to about 10 km, and the run's date and time. It contains no identifier: no account, no device ID, no name. Open-Meteo's servers see the IP address the request comes from, as any web request does. Weather data is provided by Open-Meteo.com under the CC BY 4.0 licence.
You can turn this off in Settings, under Recording, with the "Weather for each run" switch. With it off, nothing is sent to Open-Meteo.
Place names
Each run shows where it started, for example "Lakeside Dr, Albert Park". Run Supreme asks Android's
built-in geocoder (android.location.Geocoder) to turn the start point of the run into a
street name (never a house number) and a short area name. Run Supreme makes no network request for this itself. The Android geocoder is part
of your phone's system and may use Google Play services, which can send the coordinate to Google to
get the name back, under the Google Privacy Policy.
Only the start point is looked up, never the route, your pace or your heart rate. The names are stored
on your phone with the run; if the lookup fails, the run simply has no place name. A run that starts
within about 300 m of an earlier run reuses that run's area name, and within about 60 m its street
name, without a new lookup. A run saved before street names existed is looked up once, when you open it.
You can rename a run yourself from its detail screen; the title is stored only on your phone.
4. Permissions the app asks for
| Permission | Why |
|---|---|
| Precise location | To record your pace and route with GPS during a run you started. Recording runs as a visible notification while the run is in progress and stops when you press Stop. Run Supreme never records location in the background on its own. |
| Barometer (no permission needed) | If your phone has one, Run Supreme reads its air-pressure sensor during a run you started, to work out climb and descent. The readings stay on your phone: they become the run's elevation, are stored with the run, and are never sent anywhere. |
| Files (no permission needed) | When you choose "Import a GPX or TCX file" under Follow a route, Android's file picker hands Run Supreme the one file you pick. Run Supreme cannot see any other file, and keeps only the simplified route. |
| Nearby devices (Bluetooth) | To pair a heart-rate strap. Bluetooth is not used to work out where you are. |
| Notifications | The recording notification with its LAP and Stop buttons, and cues while your screen is off. |
| Health Connect (write only) | Only if you switch on Health Connect in Settings, Send runs to, or tap Send to Health Connect on a run. Health Connect asks you for four write permissions: exercise, exercise route, heart rate and distance. Run Supreme writes the finished run (its laps and pauses, route, heart rate and distance) and reads nothing back from Health Connect. You can turn it off in Settings, or withdraw the permissions in Health Connect, at any time. |
| Internet | Map tiles from Google, offline maps you choose to download from Cloudflare, and weather from Open-Meteo, as described above. Place names come from your phone's own geocoder, as described above. If you connect Intervals.icu, the runs you send to it and the planned workouts you add to its calendar. Nothing else. |
5. What we do not do
- No accounts, sign-in or profiles.
- No advertising, no ad SDKs.
- No analytics or tracking of our own. The only analytics-type signal is the Maps SDK identifier described in section 2, which belongs to Google's SDK, not to us.
- We do not sell or share your data. We could not: we never hold it.
- Run Supreme is not directed at children and has no features aimed at them.
6. Your controls
- Delete everything: Settings, Data, "Delete all" removes every run and setting from the phone. Uninstalling the app does the same. What Google's Maps SDK already received (section 2) is held by Google, not us; your Google account's privacy controls apply to it.
- Weather: Settings, Recording, "Weather for each run".
- Map: maps appear on a run's detail screen, behind your recent runs on Home (no setting turns that off), and on the record screen while you have MAP selected (NUMBERS is the default and each run type remembers your choice); do not use these if you would rather Google did not receive that map area.
- Routes: Start, Follow a route lists the routes saved on your phone; the bin beside each one deletes it. Uninstalling the app removes them too.
- Intervals.icu: Settings, Send runs to, Intervals.icu. Switch it off to stop automatic sending, or Disconnect to delete the key.
- Backup: Android settings, Google, Backup.
- Export: Settings, Data, "Export all" gives you your data as JSON or TCX.
7. Changes and contact
If the app starts sending anything new off your phone, this page and the app's Settings, About screen change first and the Play listing's data safety section is updated. Questions: privacy@runsolo.app.
The same wording lives in the app under Settings, About. Weather data by Open-Meteo.com.