RunsicKPrivacy policy
Last updated: 20 November 2026
This policy explains which personal data the RunsicK app, the web app at runsick.app and their server process, for what purpose and on which legal basis. In short: we process your data so you can record and analyse runs and other activities, train with them and share them with others. We show no ads, use no advertising or tracking services and never sell data. Visits to our website are only counted without cookies, with software we run ourselves (section 2.17).
1. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) is:
For any privacy question, contact us at the email address above.
2. Data we process
2.1 Account
When you sign up we process your name (how others see you; it doesn't have to be unique), a unique username made from it for links to your profile, your email address, password (stored only as a secure hash) and language; by creating the account you confirm that you are at least 16. Optionally you can add a profile picture, your age (it helps us estimate your maximum heart rate and calorie needs more precisely; we also store when you gave it, so it counts on over the years), your body weight, your threshold pace, your FTP, your maximum heart rate and the limits of your heart rate zones. To keep you logged in we store sessions (only as a hash of the token), and one-time links to confirm your email or reset your password.
In the app you can also sign in with Apple or Google. We then receive from Apple or Google an identifier of your account there, your email address (with Apple, if you like, a forwarding address from Apple) and whether it is confirmed, with Google also your first name, with Apple the first time your first name if you share it. We only use the first name to suggest it as your name. If there already is an account with the same email address, confirmed by Apple or Google, we link it with the sign-in. You then need no password. For signing in with Apple we also store a key from Apple with which we revoke the sign-in at Apple when you delete your account. We store nothing else from your Apple or Google account, and Apple or Google don't learn what you do in RunsicK.
Purpose: providing your account. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
2.2 Activities
When you record or import an activity – a run, a ride, a hike or another sport – we process: the sport, the GPS route with timestamps, distance, duration, pace or speed, pauses (including automatic ones), altitude, cadence (from your phone's step counter), heart rate (from a connected sensor), laps, the weather at the time and place, the songs played (title and artist), for a structured workout its steps with targets and results, and everything you add yourself: name, description, photos, gear (shoes, bike), perceived exertion and goals. From this we calculate statistics such as best efforts, predictions and records.
So that no recording gets lost, the app first stores runs on your device and uploads them as soon as there is a connection.
Purpose: recording, analysing and – according to your settings – sharing your runs. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
2.3 Location
The app uses your device's precise location to record runs – during a run also in the background, so recording continues with the screen locked. During a recording the app also uses your position to ask our server for nearby segments you starred and – if you leave a route – for the way back. Outside of a recording, the location is only used when you need it: on the home screen the app shows the weather where you are; for this, approximate coordinates are sent directly from your device to Open-Meteo (weather) and BigDataCloud (place name). When you look for routes near you, route suggestions or round trips (section 2.18), the app sends your position to our server to find or calculate suitable routes; we do not store it. You can revoke the location permission at any time in your device settings; without it, recording is not possible.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR) and the permission in your operating system.
2.4 Social features
When you follow others, give high fives, comment, mention someone or join challenges, we store this content and these connections and notify the people concerned in the app.
Segments are parts of routes that users create from their activities. When one of your activities goes through a segment, we store your time on it (with the date and, if recorded, average heart rate and power) and show it on the segment's leaderboard. If someone takes your segment record, we notify you. Segments you create show your username.
If you block someone, we store that. You then no longer see each other's profiles, activities, comments and high fives, can't follow each other and get no notifications from each other; existing follows are removed. The blocked person is not notified.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
If you ask for it ("Search contacts"), the app shows who of your contacts uses RunsicK. For this it reads only the email addresses of your contacts, turns them into irreversible checksums (SHA-256) on your device and sends only these to our server. The server compares them with the checksums of our users' email addresses and does not store them. Names, phone numbers and other contact details don't leave your device. Others can find you this way unless you change Settings → Privacy → Findable by email. Once you have searched your contacts and allowed the app to access them, it repeats the comparison in the same way at most once a day and tells you with a notification when someone from your contacts has joined; which matches there were before is only kept on your device.
Legal basis: your consent by searching (Art. 6(1)(a) GDPR); for being findable our legitimate interest in people who know each other finding each other (Art. 6(1)(f) GDPR), which you can object to at any time.
2.5 Reports
If you report a comment, an activity or a profile, we store the report with its reason and your optional note and pass it on to us for review. The reported person does not learn who reported them.
In addition, we automatically check new comments, activities and usernames for prohibited terms, spam links from new accounts and unrealistic speeds. Content flagged this way may be hidden provisionally – it stays visible to you – and is then reviewed by a human. In case of serious violations we may remove content or suspend an account.
If content or an account breaks our rules, we may warn you. For this we store with your account the reason, a short note and which content it was about, so we can recognise repeat cases, and may let you know about it by email.
Legal basis: legitimate interest in a safe community (Art. 6(1)(f) GDPR).
2.6 Beacon (live tracking)
If you turn on Beacon for a run, we create a secret link. Anyone with this link sees, without logging in, your first name, profile picture, current position, the route so far, distance and time – only during the run. You decide whom you share the link with. Besides the link for a single run there is a personal link that always shows your current run; you can create a new one at any time, then the old one stops working. We delete the live data 24 hours after the run ends.
If you add emergency contacts, we store their email addresses and, when a run with Beacon starts, send them an email with your live link (at most one per half hour). Please only add people who agree to this. You can change or remove the contacts at any time in the settings. If an emergency contact has a RunsicK account, they get a notification in the app instead of the email. If you choose friends for Beacon (at most five, only people who follow you), we notify them in the app at the start as well. While you type an email address, the app suggests matching people you follow or who follow you.
Legal basis: performance of a contract at your request (Art. 6(1)(b) GDPR).
2.7 Music
If you connect them, RunsicK controls Spotify or Apple Music through their official interfaces on your device; their privacy policies apply in addition. When you search Spotify for songs or playlists in the app, the app sends your search term to our server, which asks Spotify with it – using RunsicK’s own access, without any link to you – and returns the results to the app. The server keeps search results in memory for at most a day so that repeated searches are faster, and doesn’t store them permanently. Likewise, for the cover and song identifier (ISRC) of a Spotify song our server asks Spotify only with the song’s Spotify ID. To show covers and details of the songs played, our server asks Deezer only for title and artist or the song identifier (ISRC) – without any link to you. Your power songs and local playlists are stored in your account or on your device. For music that fits the workout (Premium), the app picks songs on your device from your power songs and the songs played in earlier activities by their tempo; our server determines the tempo likewise only from title, artist or the song code (ISRC). Playlists you choose for it stay on your device.
Individual testers whom we have enabled at Spotify are also offered a sign-in with Spotify in the app, to show their own playlists and liked songs. The access keys of this sign-in stay encrypted on the device; the app gets the playlists directly from Spotify. For this, our server stores which email addresses are enabled.
If you turn on “Add songs from Spotify history” (Settings → Music; only with this sign-in with Spotify), the app reads the songs you heard lately through Spotify’s interface (title, artist, song code and when they played). It keeps this history only on your device, for at most 14 days. When an activity has no songs – because it comes from your watch or another app, or Spotify wasn’t connected while recording – the app matches the songs that played during it and sends only those to our server – as with a recording in RunsicK. Turning it off deletes the history on the device.
While recording, the app notes which song played when and stores this with the activity. For this it connects to the Spotify app on your device by itself at the start; on an iPhone it may open Spotify for a moment to do so when music is playing.
2.8 Connected services
When you connect an account at Polar, Wahoo or Garmin, we store the access keys needed and import your workouts from there. If you connect Strava, we upload the activities you record with RunsicK there; we import nothing from Strava. You can disconnect at any time in the app under “Equipment” or in the web app under “Settings → Connections”.
Garmin. If you connect your Garmin account, Garmin sends us your activities after each sync (sport, time, distance, route, heart rate, cadence, power and the other values your device records). We use them only to show them to you in RunsicK as your activities, with the same visibility settings as activities recorded in the app (section 4), and for your statistics, records and training plan. If you send workouts, planned sessions of your training plan or routes to your watch, we transfer them to Garmin Connect. We do not sell Garmin data or share it with anyone for their own purposes. It is stored on our own server; Cloudflare only forwards it encrypted, and our encrypted backups are kept with a storage provider in the EU (section 5). No AI system processes Garmin data, and it is not used to train AI models. You can view, correct, delete and export your activities at any time (section 8). Disconnecting stops any further transfer; you can also revoke access in Garmin Connect. Activities imported until then stay in your account until you delete them or your account.
Legal basis: your consent by connecting (Art. 6(1)(a) GDPR, for health data Art. 9(2)(a) GDPR).
2.9 Notifications
For push notifications (e.g. new high fives or comments) we store a device token and send the notifications through Google's Firebase Cloud Messaging on Android and through the Apple Push Notification service on iOS. These services receive the token and the notification's title and text (e.g. the username of the person who gave you a high five) and deliver it to your device. Without a token the app asks our server for new notifications itself. While the app is open, it keeps a connection to our server to hear about new things right away; for this we only store that, and since when, the connection exists. Some notifications come with the address of a picture, such as the profile picture of the person who gave you a high five or a small map of your imported activity; your device loads the picture straight from our server, and the map's address is signed and runs out after 14 days. So that planned notifications (e.g. your monthly review) arrive at a sensible time, we store your device's time zone. Under Settings → Notifications you can turn off single kinds; we store which, and note which planned notifications we sent so that none comes twice. Some notifications are about your own use, such as your monthly review, a challenge that fits what you usually do, or a friendly reminder when you haven't recorded anything for a while; for these our server looks at your stored activities. The training reminders for your training plan and weekly goal are planned by the app itself on your device, and no further data is sent to us for them. You can turn notifications off at any time in your device settings.
If you add RunsicK widgets to your home or lock screen, the app keeps a small summary for them on your device (e.g. your distance this week, your weekly goal and the next days of your training plan). It does not leave your device and is deleted when you log out. Anyone who can see your screen can see what a widget shows.
2.10 Emails
We only send emails your account or a feature you started needs: confirming your sign-up, changing your email address (with a notice to the previous address), resetting and changing your password, the link to your data export (section 8) and confirmations when you delete your account and when it has been deleted for good. Your emergency contacts receive the Beacon emails described in section 2.6. We send no newsletters or advertising. The emails are sent on our behalf by Brevo (Sendinblue SAS, France).
So we can react quickly, our server notifies us by email about new accounts (username, how you signed up, language), support requests, feedback, tester sign-ups and reports (each with its content), about errors on the server and about training plans that do not keep one of our rules (only sport, goal and start date). These emails only go to our team and are also sent through Brevo.
Legal basis for these notifications: legitimate interest in reliable operation and quick help (Art. 6(1)(f) GDPR).
2.11 Maps
The app loads map tiles directly from OpenFreeMap and satellite images (Premium, also in the hybrid map) from Esri. For technical reasons these providers receive your IP address and the map area shown. The relief of the outdoor map (Premium, elevation data from Mapterhorn) comes from our own server; no other provider receives your IP address for it. If you save maps for offline use (a map area or a route's surroundings), the app loads the tiles of that area from OpenFreeMap and the relief from our server the same way and stores them only on your device; we do not keep track of which area you save. You can delete them in the app under "Offline maps".
2.12 RunsicK Premium
For the Premium subscription we store its status, plan and term. Payment is handled exclusively by Apple's App Store or Google Play; we receive no payment details. A service provider for in-app purchases may be used to process and verify purchases; it receives an anonymous identifier and the purchase receipts.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
2.13 Server logs and security
When you access our server, your IP address, the time and the requested address are processed for technical reasons. We use this data only briefly to protect against abuse (e.g. limiting login attempts) and to fix errors.
With your account we also store which app version you last used, on which platform, your device model (e.g. "iPhone 16 Pro") and operating system version, and when that was. This lets us help with support requests and send notices only to users of certain versions (e.g. about a bug that only occurs there).
For usage statistics we store on which days you used the app or the web app – only the date, without time, place or content. From this we find out e.g. how many users are active and come back. We also store on which days you used which Premium feature (e.g. training plan, heatmap, satellite map, routes) – only the feature and the date, not what you did with it. This shows us which features are really used. Likewise, the app reports once a day which outside services are set up on the device (e.g. Spotify linked, Apple Health on, a heart rate strap paired) – only the service and the date, not what you listen to or measure with it. Before you have an account, the app reports once which steps of the sign-up were reached (e.g. “sign-up opened”, “account created”) – only the step; we count it per day, without any identifier of your device or you. This shows us where signing up gets stuck. We delete these records after 13 months.
Legal basis: legitimate interest in secure operation (Art. 6(1)(f) GDPR).
2.14 Sensors
When you pair a chest strap, a watch, a power meter or a speed and cadence sensor, the app searches via Bluetooth for matching devices and connects directly to the chosen device during a recording. It only reads that sensor’s values (heart rate, power, cadence, wheel revolutions); we save power and cadence with your activity and calculate your best efforts and your FTP from them. The sensor's name and identifier are stored on your device only. The heart rate is saved with your activity (see section 3). From the recorded values we estimate your maximum heart rate for the heart rate zones unless you enter it yourself. You can revoke the Bluetooth permission at any time in your device settings.
2.15 Workouts and training plans
We store your own structured workouts (name, sport and steps with duration or distance and targets) with your account so you can use them in the app and in the web app; a copy is also kept on your device. When you create a training plan (Premium), we process your goal, the start and race or goal day, a target time or pace, the days you can train and how much time you have on them, the days for long sessions and your device's time zone. Added to this is your starting point: time per week and longest session of the last 30 days (from your activities or your answers), how long you have been running, whether you can run 30 minutes in one go, a recent best time or threshold pace, and whether the plan should build up more carefully; if you entered your age in your profile, we take it into account. Our server calculates the plan by fixed rules of training science, without AI, from this and your previous activities; in doing so it places you on one of six levels. For a cycling plan we also process your event's distance, your FTP, whether you have a power meter or smart trainer, whether the targets are power or heart rate and the days you ride on a smart trainer; an FTP you enter becomes your profile's. For a triathlon plan we also process your time per week and longest session per sport, how confident you feel in the water, optionally your 400 m and 200 m swim times (or the CSS calculated from them), the days you can swim and ride indoors, the days for the long ride and the long run, and triathlons done before with distance, year, time and splits; we store the CSS and the triathlons done before in your profile, so they are prefilled for the next plan. There is only one active plan at a time. With the plan we store your level, your starting point, the performance value calculated from it (VDOT) and where you stand in your hard sessions, so paces and sessions can adapt along the way; how long you have been running is stored in your profile, so we only ask once.
The plan is stored with your account. We match your activities to the days of the plan automatically. We use missed days and the perceived exertion of hard sessions to adapt the plan, for example to make a week easier or to move sessions within a week. Every week our server plans the coming weeks again from your actual activities; we store every change with its date and reason, so you can follow it and undo it. If you answer the morning question how you feel (fit, tired, a cold, ill or injured), we store the answer for that day, to adapt the day's sessions or start a break. To judge your form, we also compare the pace or power reached in hard sessions with their targets and your heart rate on easy runs with the weeks before; from this we suggest, for example, swapping a hard session, or adjust the paces. From the duration, pace, power or heart rate of your activities we also calculate their load and from it fitness, fatigue and form; we store the load with the activity. If you enter a break, we store its kind (ill with fever, a mild cold, injured, away or no time) and dates, to pause the workouts and come back gently afterwards. These are general training suggestions, not a medical assessment.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
2.16 Settings on your device
Some settings are stored on your device only and not sent to us, e.g. the values shown and voice announcements, auto pause per sport, your favorite temperature for the best time to train and the music per workout intensity. If you turn on "Record diagnostics" in the activity settings, the app also stores the raw data of GPS, step counter, motion sensor and air pressure as well as battery level and app state of recordings on your device (the last three recordings). They only leave your device if you share them yourself.
2.17 Web app
At runsick.app you can also use RunsicK in your browser. The web app accesses the same account and data as the app; the sections of this policy apply accordingly. You cannot record there, but you can upload activity files (GPX, FIT, TCX) from your computer and enter activities by hand.
When you log in, our server sets a session cookie ("runsick_session"). It only contains a random session identifier, cannot be read by scripts on the page and is only sent encrypted to our server. It expires after 180 days and is deleted when you log out. Your browser also keeps a few settings of the page in its local storage: the language last shown, the map type chosen, which notices you closed and on which days you already reported which Premium feature (so we learn it only once a day for the usage statistics in section 2.13). These do not leave your browser. We use no other cookies. As all of this is strictly necessary for the use you request, no consent is required for it (Section 25(2) no. 2 TDDDG).
When you open the segment map, the route planner or the routes near you, your browser asks whether the page may use your location. On the segment map and in the route planner it only centres the map on your location in your browser; the location itself is not sent to us, and for the segment map we only receive the map area shown, to find the segments in it. For the routes near you, your browser sends your approximate position to our server to find public routes around you; we do not store it.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
Visitor statistics. On the pages for visitors – the start page, "About RunsicK", help, legal notice, privacy policy and terms of use as well as login and registration – we count page views with the open-source software Umami, which runs on our own server. While you are logged in we count nothing, and pages inside the web app are never recorded. Umami sets no cookies and stores nothing in your browser. It records the page viewed, the page you came from (including campaign details in the link, e.g. "utm_source=instagram"), the browser, operating system and device type as your browser sends them with every page request, your approximate country with region and city, and clicks on the links to the App Store and Google Play. Umami derives country, region and city from your IP address; the IP address itself is not stored. To group page views into a visit, Umami forms a hash of the IP address and browser identifier with a key that changes daily, so we cannot recognise you on different days. Apart from the page viewed and the previous one, the page reads nothing from your browser for this, not even the screen size or language. If "Do Not Track" is switched on in your browser, we do not count you. The data stays on our server and is not passed on to anyone.
Legal basis for the visitor statistics: legitimate interest (Art. 6(1)(f) GDPR) in learning how visitors find RunsicK and which pages they view. You can object at any time, most simply with "Do Not Track" in your browser.
2.18 Routes
In the web app you can plan routes, in the app have round trips calculated from your location (both Premium). To do so, the browser or the app sends the points (for round trips your starting point and the length you want) you set on the map and the chosen profile (e.g. running or road bike) to our server. The way between the points is calculated by a routing service (BRouter) based on OpenStreetMap data, which we run ourselves on our server; the points are not passed to any third party. When you save a route, we store with your account its name, a description, the profile, the points you set, the calculated line with elevations, distance, elevation gain and surface, and who may see it. When you copy someone else's route, we remember which route the copy came from. You can download a route as a GPX file for watches and other apps.
Before you make a route public, our server checks whether its start or finish lies where your activities often begin (probably your home) and warns you if so; it only compares the end points sent with the starting points of your recent activities and stores nothing. When you look for routes near you or suggestions for a workout, the app or browser sends your approximate position to our server; it uses it to find your own routes, those friends share and public ones around you and does not store the position. If you report someone else's route, we store the report as described in section 2.5.
When you search for a place or an address in the route planner, your browser sends the search term and the approximate middle of the map section to our server. Our server uses it to ask the place search service Photon by komoot GmbH (Germany), based on OpenStreetMap data; komoot only receives the search term and the rounded middle of the map, not your IP address or your account. We keep searches in memory for at most a day to answer the same search faster, and not with your account.
When you follow a route in the app, the app stores it on your device so that this also works without a connection. Whether you are on the route and how much is left is worked out by the app on your device from your position; nothing extra is sent to us for it. If you leave the route, the app asks our server for the way back, using your position. With the activity we store which route you followed and whether you finished it. How often a route has been followed this way is shown with the route as a number without names; that you followed it is only visible to you.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
2.19 Error reports
If the app crashes or an error occurs, the app and the server send an error report: the error message and where in the code it happened, device model, operating system and app version, the last steps in the app (e.g. screens opened and addresses of server requests, without search terms) and a random identifier of the installation. Name, username, email address, location and content such as activities are not included, and the IP address is not stored. The reports are processed on our behalf by Functional Software, Inc. (Sentry, USA) in a data center in the EU. We delete them after 90 days at the latest. You can turn them off at any time under Settings → Privacy → Send crash reports.
Legal basis: legitimate interest in an app without errors (Art. 6(1)(f) GDPR).
2.20 Clubs
When you found or join a club, we store the club (name, short name, description, picture, sport, place and whether it is open or private) and your membership with its role (owner, admin, member), status (member, requested, invited), who invited you, and your settings for the club (show activities in the club, notifications). Announcements, photos and comments in the club are stored with your account. The admins of a private club see join requests with your username and profile picture.
When admins plan an event, we store its title, description, time, meeting point, route, pace groups and cancelled dates. When you answer, we store your answer and pace group for that date; the other members see who is coming. Before the date we remind you with a notification. After the date, the event shows who was there: for this we look for activities of members who show their activities in the club that began around the event’s time (and, with a meeting point, near it), and show them with their photos – only to members and only as they may see the activity anyway. For your calendar we create a link through which your calendar fetches the date without signing in.
Club challenges are stored like other challenges (section 2.4), with the club in addition. For the club’s power songs we evaluate the songs played by members who show their activities in the club; only added-up results of songs at least three members are faster with are shown, never who they are. The weekly leaderboard and the club’s segment leaderboards likewise only show members who show their activities in the club.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
2.21 Live groups
In a live group you record together with others. When you start a group or invite friends, we store the group, who is invited and who takes part, and notify those invited. While you record in the group, the app sends your current position, distance, time, speed and whether you are paused to our server – every 2 seconds while the app is open, otherwise every 5 seconds. It only keeps the latest values and passes them on to the group’s other members. When your activity is done or you leave the group, we delete the position. In a virtual run the app sends no position at all.
For comparing by time, the app also sends your time at every 100 metres, and for segments you go through in the group, their name and your time. We store both with the group and show them to its members in the summary, together with the members’ activities of that time – each only as the viewer may see them anyway. If you answered yes for a club event, you are invited to that date’s live group around its time and join it when you start recording; you can leave it at any time.
Legal basis: performance of a contract at your request (Art. 6(1)(b) GDPR).
When you start together on site, the app tells the group once your GPS is ready; the members see who is ready, and whoever started the group starts a shared countdown for everyone. In a race we store your result (the time over the distance, or the distance in the set time) and show the members the ranking. When you start a new group, the app suggests the friends you were last in a group with; for this we look at your previous groups.
Legal basis: performance of a contract at your request (Art. 6(1)(b) GDPR).
2.22 Invites
When you share your invite link, the page runsick.app/i/<username> shows your name and profile picture to anyone who opens it.
When someone opens an invite page, we store for 24 hours whom the invite was from, an encrypted fingerprint of their IP address (a hash made with a secret key, not the address itself), whether they use an iPhone, an Android device or something else, and their browser’s language. If an account signs up from the same network with the same platform and language in that time, we note the invite as likely; if several invites fit, none. It only counts once the new person confirms it in the app; they can also dismiss it there. We then delete the fingerprint.
An invite is matched for certain when the new person taps “Open in RunsicK” on the invite page in their account’s first week, or installs the app on Android through the page’s Google Play link. Google Play then passes the note “invite=<username>” to the app at its first start; the app reads it once and sends it to our server.
For a certain or confirmed invite we store who invited, you follow each other, and the inviter is notified. For the rewards (Premium months, app icons) we count how many invited friends have recorded at least three activities with RunsicK; the inviter sees the names and profile pictures of the friends they invited and how many of their first three activities there are.
Legal basis: legitimate interest (Art. 6(1)(f) GDPR) in matching an invite someone opened on purpose; performance of a contract (Art. 6(1)(b) GDPR) for following and the rewards.
2.23 Support, feedback and contact form
When you write to us via "Send feedback" in the app, we store your message, a screenshot if you add one, the app version, the operating system and the device model with your account. You can also write to us without an account using the contact form on runsick.app/support; then we store the subject, the kind of request, your message and – if you want a reply – your email address. Emails to our support address are read from our mailbox into the same system. Every request becomes a case that only our team sees; we store its history with our replies and who handles it. We reply by email (section 5).
Legal basis: performance of a contract (Art. 6(1)(b) GDPR) or our legitimate interest in answering your request (Art. 6(1)(f) GDPR).
2.24 Tester programme
When you sign up as a tester on runsick.app/testers, we store with your account the platform (iPhone or Android), which test version you use, when you signed up and whether the test version has reached us yet (the app version last reported). For Google Play's test we need your Google account's email address to add you to the test group; on the iPhone the test runs through Apple's TestFlight, where you give your details to Apple yourself. Once you complete the steps, we credit the promised Premium months. You can leave at any time; we then delete these details.
Legal basis: performance of a contract at your request (Art. 6(1)(b) GDPR).
2.25 Promotions
While a promotion runs (e.g. Premium months for the next new accounts), we check with your first recorded activity whether your account qualifies and store with your account which promotion it was, how many months you get and when they were credited.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
2.26 Notices during maintenance
When our server can't be reached (e.g. during announced maintenance), the app reads current notices from a small file at GitHub (GitHub, Inc., USA). For technical reasons GitHub receives your IP address and the usual connection data; no data from your account goes to GitHub.
Legal basis: legitimate interest in reliable operation (Art. 6(1)(f) GDPR).
3. Health data
Heart rate (also from a paired sensor), your maximum heart rate and heart rate zones, calories burned, body weight, breaks in a training plan because of illness or injury, your answer “a cold”, “ill” or “injured” to the morning question in the training plan and workouts from Apple Health, Health Connect or your watch are health data and specially protected (Art. 9 GDPR). We only process them with your explicit consent (Art. 9(2)(a) GDPR). Before the app or the web app processes health data for the first time – when you enable the import from Apple Health or Health Connect, connect a watch or a service, pair a heart rate sensor, enter your weight or heart rate values or enter a break because of illness or injury or say in the training plan that you are ill or injured (only you see it; it is deleted with the plan) – it asks you in a window of its own (in the web app likewise before uploading files, connecting a service or entering such values). That window says which data we process and for what. Only "I consent" lets you go on; without consent these features cannot be used. So that we can prove the consent, we store when you gave it and for which version of this policy. The access permission in the system dialog (e.g. of Apple Health) is separate and does not replace the consent.
- From Apple Health or Health Connect we only read workouts and their values (route, heart rate, calories, altitude) and write no data there.
- We use data from Apple HealthKit solely for the app's features, never for advertising, and do not share it with third parties.
- You can withdraw your consent at any time under Settings → Privacy → Health data. We then switch off the import from Apple Health or Health Connect, the connected services and the heart rate sensor; if you wish we also delete your stored body weight, maximum heart rate and zones, calories and the heart rate values in your activities as well as your breaks in the training plan. You can also revoke the permission in the system settings or delete your account. The lawfulness of the processing until the withdrawal remains unaffected.
4. Who sees your data
Your username, profile picture and the number of your followers and activities are visible to other users so they can find you. What else others see is up to you:
- Public account: your activities are visible to all logged-in users.
- Public pages: with a public account, people without an account can also open your profile (runsick.app/u/<username>) and your activities (runsick.app/a/<id>), for example when you or others share a link. There we show your username, profile picture, number of followers and activities, total distance and time, and your activities with the values you have not hidden. Start and finish are always hidden from visitors without an account, and they see no comments or badges. We ask search engines not to index these pages (noindex). When a link is shared in a messenger or social network, it fetches the activity's name, distance and duration and a photo or your profile picture for the preview. With a private account there are no public profile and activity pages; only routes you expressly make public have one (see “Routes”).
- Private account: only followers whose request you accepted see your activities, followers and badges.
- Hiding: for each activity – with a default in the settings – you can hide start and finish on the map, the whole map, heart rate, cadence and calories from others. Hidden data never leaves our server towards other users.
- Segments: your segment times are seen by the same people who may see the activity. Activities with a hidden map and times inside the hidden start and finish area appear on no leaderboard. Private segments are only visible to you.
- Clubs: the other members see that you are a member of a club; open clubs are also shown on your profile. Your activities only appear in a club if you show them there, and only to members who may see them anyway. What you write in a club is seen by its members; for open clubs, name, description, picture and events are visible to non-members too.
- Live groups: only the group’s members see your position, and only while you record in it; in virtual runs nobody does.
- Routes: new routes are private. If you share a route with your followers, people who follow you (with a private account: whose request you accepted) see the whole route including start and finish (which are often near your home) and can download it as GPX and copy it into their own routes. If you make a route public, every signed-in user can find it (e.g. under "Routes near you"), view, download and copy it, and it has a public page (runsick.app/r/<id>) that people without an account can open too – with its name, description, the whole line including start and finish, your username and profile picture. A copy then belongs to the person who made it and stays when you change or delete your route. Private routes and routes for followers only have no public page.
You always see all of your own data.
5. Services and recipients
We only share your data as far as needed for the features described:
- Hosting: we run our server and the web app ourselves. Connections pass through Cloudflare, Inc. (USA), which forwards the traffic encrypted and protects against attacks. Backups are kept on our server and, encrypted, with a storage provider in the EU.
- Google Firebase Cloud Messaging (Google Ireland Ltd./Google LLC) for push notifications on Android, the Apple Push Notification service (Apple Distribution International Ltd./Apple Inc.) on iOS.
- Apple or Google for signing in with Apple or Google, if you use it (section 2.1).
- OpenFreeMap for map tiles, Esri (Environmental Systems Research Institute, Inc., USA) for satellite images, komoot GmbH (Photon) for the place search in the route planner.
- Open-Meteo (Switzerland) for weather data: from the device for the home screen, from the server with place and time of a run.
- BigDataCloud (Australia) for the place name on the home screen.
- Deezer for song details (title, artist or song identifier only).
- Spotify, Apple Music, Polar, Wahoo, Garmin and Strava if you connect them.
- GitHub (GitHub, Inc., USA) for notices while our server can't be reached (section 2.26).
- Google (Google Groups, Google Play) or Apple (TestFlight) if you join the tester programme (section 2.24).
- Brevo (Sendinblue SAS, France) for sending emails; receives your email address and the content of the email.
- Sentry (Functional Software, Inc., USA; stored in the EU) for error reports (section 2.19).
- Apple or Google for purchasing and billing the Premium subscription.
Where required, we have concluded data processing agreements with providers that process data on our behalf.
6. Transfers outside the EU
Some of these providers are based outside the EU, in particular in the USA. Data is only transferred where an adequate level of protection exists – for example through an adequacy decision of the European Commission (such as the EU-US Data Privacy Framework or for Switzerland) or the EU standard contractual clauses.
7. Retention and deletion
- We keep your account and activity data as long as your account exists.
- You can delete individual activities, photos, comments and connections yourself at any time.
- Ended training plans stay stored with your account until you delete it.
- We keep routes until you delete them or your account.
- We delete your position in a live group as soon as your activity is done or you leave the group. The group with its times and segment times stays stored for the summary until you delete your account.
- We keep clubs, memberships, posts, comments and answers until you delete them, leave the club or the club is deleted, at the latest until you delete your account.
- We delete the fingerprint stored when an invite page is opened after 24 hours, or sooner once it is matched to a new account. Who invited you stays stored until you delete your account.
- We keep support cases and messages from the contact form until the request is settled and then for at most three years; warnings as long as your account exists.
- We delete your tester sign-up once you leave or delete your account; credited Premium months and promotions stay stored with your account.
- Under Settings → Delete your account you can delete your account with all its data. From then on the account is hidden from everyone, we log you out everywhere and delete it for good after 30 days, including your comments and high fives on others' activities. If you log in again during this time, the account is kept.
- Data on your device can be removed under Settings → Delete all local data; it is also deleted when you uninstall the app. In the web app we store only the session cookie, which is deleted when you log out, and the settings from section 2.17 in your browser; you can delete them via your browser's site data.
- We keep database backups for 14 days and photo backups for 7 days; deleted data disappears from them after that at the latest. Statutory retention obligations remain unaffected.
8. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). You can withdraw any consent at any time with effect for the future (Art. 7(3)). Just write to us at the address above. You can download a copy of all your data (account, activities as JSON, GPX and TCX, photos, routes, plans, who you follow and who follows you) yourself at any time as a ZIP file: in the app under Settings → App data, in the web app under Settings → Account. We put the file together in the background and send you a link by email; it stays on our server for up to 7 days and is deleted afterwards, as well as when you ask for a new export or delete your account.
You can also lodge a complaint with a data protection supervisory authority, in particular in the member state where you live.
9. Other
- Providing your data is necessary to use the app as far as the respective feature needs it. Optional information is marked as such.
- There is no automated decision-making, including profiling, within the meaning of Art. 22 GDPR. The automatic check of content (section 2.5) at most hides content provisionally; a human decides on removals and suspensions. The automatic adaptation of a training plan (section 2.15) only concerns your training suggestions.
- RunsicK is intended for people aged 16 and over.
- We update this policy when the app or the law changes. You always find the current version in the app, in the web app and at https://api.runsick.app/privacy.