runair.app

Legal

Privacy policy

Polityka prywatności jest dostępna tylko po angielsku.

Last updated 17 November 2026

This policy explains how runair processes personal data in its iPhone and Android apps and on runair.app. runair records and imports runs, calculates scores and maintains leaderboards and special races.

At a glance. Accounts are for people aged 18 and over. Your individual tracks and sensor readings are not available for other runners to open in runair, but profile information, a public profile's Runs tab (each run's numbers, start time, nearest city and route outline, with no map), leaderboard values and race results can be visible. Even a private profile's username and race time appear in public special-race results, except results from runs imported from Garmin, which are shown only in the app. Connected health sources are optional; some need your explicit health-data consent in the app, and connecting Garmin always does. We do not sell personal data. We do not use workout or health data for advertising or to train AI models, and runair has no AI features that analyse them. You can turn off connections, delete your account and contact us about your data.

1. Who is responsible

The controller is Katarzyna Kołodziejczyk, Poland. Correspondence address: skr. poczt. Nr 1420, Wrocław 16, 54-137 Wrocław, Poland. Contact for privacy, support and safety: support@runair.app. Our separate Consumer Health Data Privacy Policy describes health-data categories, disclosures and rights under applicable US consumer-health laws.

2. Information we collect and its purposes

3. Location

Profile location is separate from a run's route. If you share profile location, the app rounds coordinates to two decimal places, roughly a kilometre, before sending them, and the server rounds again. We store them and their update time to select city boards and to suggest nearby runners in People you may know; search results do not use them. Board membership can reveal a broad area, so rounding is not anonymisation. Country comes from a location lookup or the phone's region and can be changed in Edit profile.

Recording a run uses precise GPS, including with the screen off, from its start until it ends. The app sends progress and a timestamped track, with accuracy and altitude where available, to measure, check and show the run. Connected workouts can also supply precise tracks. Other runners cannot open these tracks through runair.

Turning off Share location in Settings erases stored profile coordinates and removes you from city boards and location-based suggestions. It does not stop GPS for a run you choose to record, stop routes from a connected workout source or erase existing tracks. Revoking device permission alone does not erase data already stored.

Maps and place lookups use Apple MapKit on iPhone; OpenFreeMap tiles through MapLibre and the Android geocoder on Android. Map requests or lookups can disclose the requested area or coordinate and technical connection information to the provider. Tracks are drawn over maps in the app.

4. Apple Health, Health Connect and Garmin

Connections are optional and require the permissions for the selected feature and, where the app asks for it, your explicit health-data consent (section 8). Garmin always requires that consent first.

Imported runs support the same scoring, records, race matching and summaries as recorded runs. We do not request sleep, reproductive information, diagnoses or medical records from these integrations. Workout and health data are not sold or used for advertising; we do not use them to train AI models, and runair has no AI features that analyse them. Their original samples are not exposed to other runners; derived leaderboard values and race times can be visible as described below.

Switching off an import or revoking health-store permission stops future reading. Disconnecting Garmin in the app, or deleting your account, deletes your Garmin user identifier and tokens and asks Garmin to stop sending your activities. Removing runair's access in Garmin Connect deletes them when Garmin tells us; turning off only activity sharing there pauses deliveries until you allow it again. Disconnecting does not erase existing runs; runs imported from Garmin stay unless the law or Garmin's conditions require us to remove them. Source copies in Apple Health, Health Connect or Garmin remain independently controlled there.

5. Visibility and sharing

6. Service providers and other disclosures

Railway Corporation, a US company, hosts the server/database in Amsterdam, Netherlands; backups use Railway object storage backed by Tigris and configured volume backups. Backups and support access can be outside the Netherlands (section 10). The operator and these service providers can process stored data to operate, secure and recover runair; Railway, including its Tigris-backed storage, acts as our hosting provider.

Apple APNs and Google Firebase Cloud Messaging deliver requested notifications, which can contain names, distances, times or scores. Apple WeatherKit receives the centre of a 0.1° grid square around a run's start (several kilometres across) and the hour of the run, so we can show its weather; it receives no route, sensor data or account identity. Sign-in providers and the connected health/map services described above process their respective requests. Garmin receives only the requests we make with your connection tokens, such as asking Garmin to stop deliveries when you disconnect or delete your account. Support email uses Porkbun forwarding and a Google mailbox. We give each of these providers only the data its task needs, and each handles it under its own data-protection terms. We may disclose relevant data where required by law or as necessary and lawful for legal claims. We do not sell personal data or share it for targeted advertising.

7. Website

With your consent, Google Analytics measures site visits and app-download clicks. Google receives connection information, including IP address and device/browser information. Events use generalised page addresses without query strings/fragments, referrer origin, language, page type and button position; race paths are grouped, and profile pages are excluded. We do not send account identifiers, names, invitation parameters, tracks or health data. Advertising features are disabled, and Analytics is not loaded without consent.

Your choice and analytics cookies last up to 180 days. Use Analytics settings in the footer to withdraw; this stops future measurement and clears site analytics cookies, not data already received by Google. A language preference is stored locally. Hosting/API services also receive IP addresses and requests for operation and security.

8. Legal bases and choices

Under GDPR, we rely on contract (Article 6(1)(b)) for requested account, running and competition features; consent (Article 6(1)(a)) for optional profile location, used for city boards and nearby suggestions, and for website analytics; legitimate interests (Article 6(1)(f)) in security, fair results, abuse prevention, support, recovery and legal claims, and in suggesting runners whose routes overlap or who share your country in People you may know, which you can object to by emailing us; and legal obligations (Article 6(1)(c)).

Health data, such as heart rate, cadence, power and energy, require explicit consent under Articles 6(1)(a) and 9(2)(a), unless another lawful exception applies. Terms acceptance or general device access does not by itself provide that consent, and Garmin cannot be connected without it. To withdraw it, turn off health-data consent in Settings → Privacy choices on Android, or email us from any device. Withdrawing stops imports from health sources, deletes the heart rate, cadence, power and energy values we hold, including totals, averages and series, from the live service, and disconnects Garmin; backup copies expire as section 9 describes. Your runs, with their routes, distances and results, stay under our contract with you (Article 6(1)(b)) until you delete them or your account. Withdrawal does not affect earlier lawful processing.

Optional profile details and connections can be declined. Precise location is needed for app GPS recording; notifications are optional. Removing a permission does not automatically erase stored data. Scores and run checks are automated; you can challenge a result through Help and feedback. We do not use automated decisions producing legal or similarly significant effects.

9. Retention and deletion

Account and activity records are generally kept while you have an account, subject to deletion requests and the purposes above. Delete account under Profile removes profile/sign-in data, sessions, tokens, runs, tracks, sensor data, imports, competition records and blocks from the live service, and removes you from results. A minimal Deleted runner record remains for references. Notification text to/about you is blanked; operational delivery metadata can remain.

Deleting one run removes its ranking contribution and erases its detailed track, sensor series, recordings and health values, such as heart rate, cadence, power and energy; a summary/import record without health values can remain. Contact us for complete health-data erasure without account closure, or withdraw consent (section 8). Garmin user identifiers and tokens are deleted from the live service when the connection ends; backup copies expire as described below. Signing out, uninstalling or disconnecting a source does not delete the account.

Reports, reported-content snapshots, necessary moderation/ban identifiers, correspondence and security records may remain as needed to address abuse, unresolved complaints, legal duties or claims. They can contain personal data; they are not all automatically erased with an account. Removed accounts can leave hashed device/provider identifiers to prevent ban evasion. Contact us about retention or erasure of a particular record.

Backup copies expire: continuous database backups after seven days, volume backups after at most 27 days. A restore must not bring back data that was already deleted. Copies held by health stores or recipients you shared with remain separately controlled.

10. International processing, security and rights

Some providers, including US companies such as Railway, Apple and Google, can process data outside the EEA, for example for notifications, sign-in, weather, backups or support access. Where GDPR applies, transfers require an applicable adequacy decision or appropriate safeguards, such as European Commission Standard Contractual Clauses and necessary supplementary measures. Contact us for applicable safeguards and a copy. App/server traffic uses HTTPS and operator access is restricted; no system guarantees absolute security.

Email support@runair.app with your username to request access, correction, deletion, restriction, objection, portability or consent withdrawal, as applicable. We verify identity proportionately. GDPR requests normally receive a response within one month; a permitted extension of up to two further months is explained within the first month. To appeal a refusal, use the same address with the subject Privacy appeal. Additional consumer-health rights and request procedures are in the health-data policy. Authorised agents may act where permitted; exercising rights does not result in discrimination, though features needing withdrawn data may stop working.

You can complain to Poland's UODO or your relevant regulator: an EU data protection authority, the Canadian federal/provincial privacy regulator, Australia's OAIC, or a US state Attorney General/privacy regulator, as applicable. This does not limit other legal remedies.

11. Minimum age and policy changes

runair is for people aged 18 and over who meet the eligibility requirements in our Terms. People under 18 may not create or use an account, even with parental permission. If you believe someone under 18 has an account, contact support@runair.app so we can investigate and remove ineligible accounts and their personal data, subject to lawful safety-record retention.

We publish updates here with their date and give appropriate notice of material changes. A policy update does not itself authorise new processing or replace required consent.