Privacy policy
Last updated 16 October 2026
Spurt is a game about your own training. This page says what is stored about you, where and why, for how long, and how you download or delete all of it.
Who is responsible
Spurt is made by Eric Lindholm, a private individual in Sweden, who is the data controller for the data described here. Questions about your data: eric@fartlek.io.
What is stored
On your phone: the club, the runners, the diary with your sessions, the money and the results, your settings, and the connection to Strava (in the phone's keychain).
On Spurt's server, when the app is connected to it:
- The save: the club, the runners, the diary with your sessions (date, minutes, type and title), the money and the results, the coach's name and look you chose, and the phone's time zone so time is counted right.
- An anonymous id. No name, no phone number.
- If you save the club with Google or Apple: the e-mail address Google or Apple hands over and the account's id there, only in the sign-in (Supabase Auth) and its log of sign-ins. With Apple (on the iPhone) the address may be a hidden forwarding address from Apple. Link both to the club and both accounts are there. The address is used only to sign you in again and to show which account the club is saved with. Nothing else is fetched from Google or Apple: no name, no picture, no contacts.
- The club's snapshot if you share it, your race entries, and whether you have reported another club's name.
- Your club buddies: which clubs and since when, a code you made (only as a checksum, never the code itself) and when you tried a code.
- The league: the club's points in each race, its division and its final place each season.
- The rankings: your runners' times and the coach's reputation, when they are among the best.
- If you connect Strava: your id at Strava (the athlete's number), your name there, which permissions you gave, when your sessions were last fetched, and weeks with unusually many runs without a GPS track (no points are taken for them). The keys only encrypted (Supabase Vault).
- The last ten versions of the save, so the club can be restored if something goes wrong on the server.
- The server's job log: when the jobs that count weeks and races ran, and which clubs they could not count.
- Error reports from the app when something goes wrong in it: the app's version, the phone's system (Android, iOS or the web), where in the code the error happened and what it is called, under an id that is not the account's. Never the error's text, the save, names or sessions.
- Feedback you send from the Office: the text, the app's version, the phone's system and when.
- Which days you opened the game: the day's first and last opening, the app's version and the phone's system. Nothing else.
- If you turn on the notices from the server: the phone's push token (the app's address at Expo's push service), the phone's language and which notices you chose.
Your town is stored only on the phone. The server only gets the club's area (the regional race town nearest your town, about as coarse as a county) and which races you entered, and a race is named after the town it is run in, within a few dozen kilometres of yours.
The server never gets: your town or where you are, the phone's id, or heart rate and pace from your sessions.
Where
The server is a Supabase project in the EU. Each player reaches only their own data, and it is never sent anywhere else.
The map on the phone fetches map images of your town from OpenFreeMap (map data from OpenStreetMap) when you open it. OpenFreeMap then sees the phone's IP address and which part of the map is shown, nothing else.
The exception is the notices you turn on yourself: a notice from the server goes through Expo's push service and on through Apple's or Google's to the phone. It carries only a runner's first name and what happened (the points for the team, that the race is decided, and the place only if you chose it), never your sessions.
Why
So you can play: the club stays if you change phones, and if you save it with Google or Apple you reach it from another phone. So races against other players work: start fields are built from the clubs' snapshots and entries, and the server scores the races the same for everyone. The error reports so that faults in the app are found and fixed. The feedback and the days opened to see how the game is received and what needs to get better. For nothing else.
What other players see
If you share your club, players in your area (and in the races you enter) see the club's name, emblem, kit and area, its place in the league, the runners' fictional names, age, attributes and personal bests, and which races they are entered in. Players in your area also see the coach's name you chose, on the page of the clubs in the area. Your club buddies see the same wherever they live, and the results of the races your runners run. Your runners appear in the start fields and results of the races they run. When a time is among the best, the runner appears in the rankings for every player, with name, club and time; the coach's name only if you share the club. Nobody else ever sees your sessions, your e-mail or your settings. You turn sharing off in Settings.
Strava
You connect Strava yourself. Spurt fetches your sessions from there (type, date, time and title) and turns them into points. Heart rate is only compared with your own heart rate zones to see whether an easy session was easy, on the server when it fetches your sessions: only the answer is kept, never heart rate, zones or pace. You disconnect in the diary. Strava has its own terms for what you keep with it.
Money on the street, if you turn it on in the office: Spurt reads the GPS track of your new runs and checks whether it passes through the week's tiles in your town. This happens on the server when it fetches them; the phone then sends the week's tiles along, never your town. The track is thrown away at once. Only which tiles are taken is kept, never the track, where the tiles lie or where you ran.
How long
- If you delete the club and the account, everything goes at once.
- A club not saved with Google or Apple is deleted whole when the app has not been opened against the server for 12 months.
- A club saved with Google or Apple is deleted after 24 months without the app being opened.
- The club's snapshot is removed after 30 days without an update, and races 30 days after their week.
- The Strava keys are removed when you disconnect Strava. Keys the app never collected after you signed in at Strava are removed within an hour.
- Only the last ten versions of the save are kept, and they are deleted with the account.
- The league's points and divisions are removed after two seasons; the final places stay.
- The rankings cover this season and the last; the records and the ones just before them stay.
- The job log is removed after 14 days.
- Error reports are removed after 90 days, and with the account.
- The push token is removed when you turn the notices off, sign out or delete the account, and after 90 days without a word from the phone.
- A club buddy stays until either of you ends the friendship or deletes the account. A code is valid for a day, and the tries are kept a day.
- The days opened are removed after 90 days and feedback after 12 months, both also with the account.
- Supabase's own backups of the database and the sign-in's log may keep data for a while after a deletion, until they are replaced.
Your rights
At any time you can download everything stored about you and delete the club and the account for good, both under Office → Settings. You change names and town in the Office. Races you have already run stay in the other clubs' results, like in a newspaper, but without any link to you. If you think something is wrong, you can complain to the Swedish Authority for Privacy Protection (IMY).
Nothing is sold
No data is sold or handed over, nothing is used for advertising, and the app has no tracking or analytics from other companies.
Changes
If the policy changes, it says so here, with the date.