← RunnersDNA

Privacy Policy

RunnersDNA · Last updated: November 17, 2026

1. Who We Are

RunnersDNA is operated by Bob Creative Copy SRL, a company registered in Romania (CUI: RO39386811), with registered address at Strada Lungă nr. 139, 500051, Brașov, Romania.

Contact: privacy@runnersdna.app

2. What This Policy Covers

This Privacy Policy explains how RunnersDNA collects, uses, stores, and protects your personal data when you use our platform at runnersdna.app. It applies to all users of our web and mobile application.

By using RunnersDNA, you agree to the practices described in this policy.

3. Data We Collect

3.1 Data You Provide Directly

  • Name, email address, and password (during account registration)
  • Age, weight, and running experience (during onboarding)
  • Goal races and training preferences
  • Your weekly check-ins, if you fill them in (how training felt, pain, tiredness and an optional note), and the availability and notes you add to your training calendar
  • Your answers to your club's start questionnaire, if your club uses one: your running history, goals, training habits, sleep, nutrition and equipment. Its health step (past injuries and treatments, medical conditions, medical tests, recurring pain) is optional, and its answers are saved only if you agree that your coach may see them (see sections 4 and 6.1).

3.2 Data From Connected Platforms

Strava (via OAuth connection)
When you connect your Strava account, we access:

  • Running activity history (pace, heart rate, distance, elevation, moving time)
  • Activity routes and GPS data
  • Gear information
  • Personal records, and the runs you mark as races

We access only the data necessary to compute your performance profile and show it to you. We do not post to Strava on your behalf. Your official race results come from the race timers' published lists, not from Strava (see 3.3).

Intervals.icu (your watch)
Your watch reaches RunnersDNA through Intervals.icu: you link your Garmin, COROS, Suunto, Polar or Wahoo device to your own Intervals.icu account, and connect that account to RunnersDNA with your personal Intervals.icu API key (or, where offered, through Intervals.icu's own authorization screen). For a Garmin, Polar or COROS watch you can also connect the watch's own account directly (see below). When you connect Intervals.icu, we read:

  • Your activities as your watch recorded them: runs and other sports, with their time, distance, heart rate, cadence, altitude and power samples, their laps, whether you marked them as a race, and your rating of the effort. Activities that reached Intervals.icu from Strava are not read (Intervals.icu does not share them). When the same run is also on Strava, we keep your watch's copy instead of Strava's.
  • Recovery data your watch records: sleep duration, sleep score and heart rate during sleep, HRV, resting heart rate, SpO2, VO2 Max, respiration rate, daily steps and weight (only what your device and your Intervals.icu settings provide)
  • Your Intervals.icu athlete profile (name and identifier) and your running settings

And, only on your behalf, we write:

  • Planned workouts and race plans, made by your coach or by you, to your Intervals.icu calendar, from where Intervals.icu sends them to your watch; when a workout is deleted in RunnersDNA, we remove it from that calendar too
  • Your running threshold pace in your Intervals.icu running settings, estimated from your race results, so pace targets reach your watch correctly

We do not read or change anything else in your Intervals.icu account. Your API key is stored on our servers and used only for the calls described above. You can disconnect at any time (see section 9).

Activity files (FIT upload)
If you upload activity files from your watch (FIT files, for example from Garmin Connect → Export Data), we read from each the activity as your watch recorded it: sport, start time, distance, duration, heart rate, cadence, altitude, speed and power samples, and laps, plus the watch model. We keep the activity, not the file. When the same run is also on Strava, we keep your file's copy instead of Strava's.

Garmin Connect (direct connection)
If you connect Garmin Connect from Account → Connected services, you sign in on Garmin's own page and choose there what to share with RunnersDNA. Garmin then sends us, from the moment you connect (it does not send anything older), each time your watch syncs:

  • Your activities: runs and other sports, with their summary (time, distance, pace, heart rate, cadence, elevation and the watch model) and the file your watch recorded (heart rate, pace, cadence, altitude and power samples, laps, and your GPS route, which we keep to draw the map of the run)
  • Your daily health data: resting heart rate, steps, stress level, Body Battery, sleep (duration, stages, sleep score, when it began, and SpO2 and breathing during sleep), heart rate variability (HRV) and VO2 Max

And, if you allow workout import on Garmin's page, we write on your behalf:

  • Your coach's planned workouts, made in RunnersDNA's workout editor, to your Garmin Connect account, scheduled on their day, from where Garmin sends them to your watch; when a workout changes or is removed in RunnersDNA, we change or remove it there too. These workouts then no longer go through Intervals.icu, so they do not reach your watch twice

Your Garmin data is shown to you and, only if you linked a coach, to your coach (your health data only with the health consent, see section 4). We never sell it, we do not share it with anyone for their own use, and we show it with Garmin's attribution. When the same run also reaches us from Strava or Intervals.icu, we keep Garmin's copy. Garmin is an independent controller of the data in your Garmin Connect account; its privacy notice is at garmin.com/privacy/connect.

Polar (direct connection)
If you connect Polar from Account → Connected services, you sign in on Polar Flow's own page and agree there to share your data with RunnersDNA. Right after you connect, we read what Polar still keeps from the last 30 days (activities) and 28 nights (sleep); from then on Polar tells us each time your watch syncs, and we read:

  • Your activities: runs and other sports, as the file your watch recorded (time, distance, pace, heart rate, cadence, altitude and power samples, laps, the watch model, and your GPS route, which we keep to draw the map of the run)
  • Your sleep: duration, stages, sleep score and when it began
  • Your Nightly Recharge: heart rate variability (HRV), your average heart rate and your breathing rate during sleep

We do not write anything to your Polar account.

COROS (direct connection)
If you connect COROS from Account → Connected services, you sign in on COROS's own page and authorize RunnersDNA there. Right after you connect, we read your activities of the last 30 days; from then on we read what is new four times a day:

  • Your activities: runs and other sports, as the file your watch recorded (the same data as for Polar above, including your GPS route)
  • Your sleep (duration, sleep score and when it began), your heart rate variability (HRV) during sleep and your resting heart rate, for the last 7 days

When you connect COROS, we also write on your behalf, to your COROS account, the workouts your coach plans for you (name, description and steps), scheduled on their day in your COROS calendar, from where COROS sends them to your watch; when your coach changes one, we change it there too. These workouts then no longer go through Intervals.icu, so they do not reach your watch twice. We write nothing else to your COROS account. COROS does not let us move or delete a workout: one your coach moves or deletes stays on your watch until you delete it in the COROS app. Disconnecting COROS stops any further writing.

Your Polar and COROS data is shown to you and, only if you linked a coach, to your coach (your health data only with the health consent, see section 4). We never sell it and we do not share it with anyone for their own use, and we show it with the name of its brand (Polar or COROS) as its source. When the same run also reaches us from Strava or Intervals.icu, we keep the copy from Polar or COROS. Polar Electro Oy and COROS are independent controllers of the data in your Polar and COROS accounts; their privacy notices are at polar.com/en/legal/privacy-notice and coros.com/privacy.

Garmin Connect (file upload)
If you choose to export a health summary file from Garmin Connect and upload it, we extract recovery metrics from it (such as sleep, HRV and resting heart rate). The raw file is deleted after processing.

3.3 Third-Party Data

Weather data: We enrich your activity history with historical weather conditions (temperature, precipitation) using public weather APIs, to provide context for your performance data.

Official race results: For races you ran from 2025 on and within the last 18 months (your goal race, a race you signed up for in the app, or a run marked as a race on Strava), we look for your name on the public results lists that race timers and organisers publish (for example Time-iT, RaceResult or Sportic), to add your official time, places and category to your profile, or to suggest them for you to confirm. We read the whole published list and match your name to it ourselves: your name is not sent to these sites. We keep the spellings of your name as these lists print them, only to find you on later lists and on UTMB; they are not shown in the app.

UTMB Index: If you are a member of a club, we also search UTMB's public runner database (utmb.world) for your name and those spellings. We link a UTMB profile to you, and show its UTMB Index, only when that profile lists your own official results: the same races, on the same day, with the same time.

Our copies of results lists: To find these results, we keep a copy of each results list we read, as it was published: every finisher's name, bib number, gender, club, category, time and places. The copies are used only to find our users' results and are not shown in the app. Each copy is deleted 18 months after its race (or 18 months after we last read it, when we do not know the race date). When a copy holds a line that matches one of our users, on a day they recorded a run, and that result is not on their profile yet, we keep only those lines, for at most 6 more months, so the result can still be added; everyone else's lines are deleted on schedule. When you delete your account, we remove the lines that match your name from the copies (see section 7).

3.4 Automatically Collected Data

  • IP address and device type (for security and analytics)
  • Session data and usage logs
  • If you create your account from an event's link or QR code (for example at a running conference): the name of that event and which of its codes you used, saved once on your account. We use it to know which events bring runners to RunnersDNA and to honor what was offered there (for example free access). Nothing else about that visit is kept.
  • Error reports (via Sentry, anonymized)
  • In the mobile app, if you allow notifications: the push address of your phone (a token issued by Apple or Google through Expo), whether it is iOS or Android, and the app version. It is deleted when you sign out of the app, when the phone stops accepting our notifications, or when you delete your account.
  • The mobile app does not read Apple Health, Health Connect, your location, your contacts or your photos. Your runs and recovery data reach RunnersDNA only from the services you connect (Strava, Intervals.icu, Garmin Connect, Polar, COROS), as described in 3.2.

4. How We Use Your Data

We use your data exclusively to provide and improve the RunnersDNA service.

PurposeLegal Basis (GDPR)
Compute your Runner DNA performance profileContract performance
Generate personalized training insights and coaching signalsContract performance
Display your historical trends and progressionContract performance
Share your start questionnaire's health answers with your coachExplicit consent (GDPR Art. 9(2)(a)), which you can withdraw at any time
Share your health data with your coach in the club and your club's administrators (see below)Explicit consent (GDPR Art. 9(2)(a)), which you can withdraw at any time
Show the runs from your watch to the other members of your clubConsent, which you can withdraw at any time
Send product updates and feature announcementsLegitimate interest
Detect and prevent fraud or abuseLegitimate interest
Comply with legal obligationsLegal obligation

Your health data, in this policy, is your watch's recovery data (resting heart rate, HRV, sleep, SpO2, VO2 Max, steps, weight and the other data listed under Intervals.icu, Garmin Connect, Polar and COROS in 3.2), the daily metrics you enter in your training calendar (such as mood, stress, tiredness, muscle soreness, sickness and injury) and, in your weekly check-ins, your answers about pain and tiredness and your note. We ask for both consents above when you join a club, with nothing ticked for you, and you can give or withdraw them at any time in the club, under Club → What data you share. The health consent is for your coach in the club, whichever of the club's coaches that is (the consent names your current one), and for the club's administrators: a coach the club's administrator moves you to sees your health data under the same consent, and a coach from outside the club never sees it, even one you add yourself. Without the health consent, your coach and the club's administrators do not see your health data and your coach's planning assistant does not receive it. You always see your own, and our computation engine still uses it to compute your own profile.

We do not use your data for advertising. We do not sell your data to third parties. We do not use your raw activity data to train machine learning models.

Your activity data, from Strava and from your watch (through Intervals.icu or the files you upload), is processed by our computation engine to produce numerical performance scores. Some features then use AI text generation (Claude, by Anthropic) to put these into words or to help your coach plan, with the data listed below: your activities from Strava and from your watch, your watch's recovery data, your official race results, and what you or your coach enter in RunnersDNA (your plan, check-ins, notes, goals and chat). We never send your email address, your password or your GPS routes:

  • Texts about your running (such as insights on an activity, race plans and reviews, your evolution report, your story and the Brain chat): your name, your goals and races, your official results, the figures from your activities, from Strava and from your watch (such as distances, paces, heart rate, elevation and activity titles) and the scores we compute from them, your recovery data and your weight, the notes you or your coach add about periods such as an injury or a break, and what you write in the chat.
  • The planning assistant your coach may use to draft your training: your recent training as planned in RunnersDNA and as you recorded it (from Strava or your watch), your training zones, your goal and upcoming races, your last two weekly check-ins (how the sessions felt, the plan and any race; your answers about pain and tiredness and your note only with your health consent), the availability and notes in your calendar for the week being planned, and your coach's own notes and instructions. It is not sent your name. Nothing it drafts reaches your calendar until your coach accepts it.
  • Your club's weekly recap: figures from the members' activities they share with the club (from Strava and from their watches), the names of the members it mentions, the badges, kudos and challenges of the week, and any note given with a badge.
  • A result screenshot you upload: the image and your name, to find your line on it.
  • Finding a race's official page or results page on the web: only the race's name (from your goal, your sign-up, the race directory, a name you gave the run in RunnersDNA or your race activity's title on Strava), its date or year and, when we know it, its town. Your name is not sent; your official results are matched to you by our own code (see 3.3).

Garmin data and AI (AI transparency statement). Data from Garmin Connect (your activities, your health data and what we compute from them) is sent to AI text generation (Claude, by Anthropic) only if you allowed it, with a separate box, unticked by default, on the screen before you connect Garmin. You can change your choice at any time in Account → Connected services → Garmin Connect → "AI features may use my Garmin data". Without your consent, the AI features do not receive any of your Garmin data: they use your other data, or show a text written by our own code. With it, your Garmin data is used only to write the texts listed above, for you and your coach, one request at a time. Neither we nor Anthropic use it to train, evaluate or improve any AI model, and we do not keep it for that purpose. Withdrawing your consent stops new requests at once; texts already written stay visible to you.

Polar and COROS data and AI. The same rule holds for the data we receive from Polar and from COROS (your activities, your health data and what we compute from them): it is sent to AI text generation (Claude, by Anthropic) only if you allowed it, with a separate box, unticked by default, on the screen before you connect, and you can change your choice at any time in Account → Connected services → Polar or COROS → "AI features may use my Polar data" (or COROS data). Without your consent, the AI features receive none of it; with it, it is used only to write the texts listed above, one request at a time, and neither we nor Anthropic use it to train, evaluate or improve any AI model.

Your start questionnaire answers are never sent to AI.

Notifications. If you allow them, the mobile app tells you when your coach adds, moves, changes or removes a workout in the next days, and when your coach writes to you about a workout. A notification names the workout and the day; it never shows the text of a message or any health detail on your lock screen. We send none between 21:30 and 07:00 (Romanian time). You can turn them off in your phone's settings at any time.

5. Data Storage and Security

  • All data is stored on servers within the European Union.
  • Database: PostgreSQL, hosted on Railway (EU region).
  • Data in transit is encrypted using TLS 1.2 or higher.
  • Access to production data is restricted to authorized team members only.
  • Passwords are hashed using bcrypt and are never stored in plain text.
  • We perform regular security reviews and apply security patches promptly.

6. Data Sharing

6.1 Your Club and Your Coach

If you join a running club on RunnersDNA (for example at threshold.runnersdna.app), the club's members can see your name, your profile photo and your club activity, such as badges and the events you sign up for. Your runs, from Strava and from your watch (in the club feed, rankings, the weekly recap, challenges and teams, badges, your last 7 days in People, your journey and Did you know), are shown to them only if you agree (see section 4). A run you keep to Only You or Followers on Strava is not shown to the club, not even as your watch recorded it through Intervals.icu or a file you upload; a run that reaches us straight from Garmin Connect is Garmin's data, not Strava's, and is shown like your other runs. In the club's settings you choose whether your club card is shown to other members, and, separately, whether the club may name you or use photos of you outside the club (for example in a results poster on social media). Being named outside the club is off until you turn it on.

If you are linked to a coach, that coach can see your activities, your training calendar, your weekly check-ins, your race results (including your UTMB Index) and your evolution report, so they can plan your training; your health data (see section 4) only if you agreed to share it and they are one of the club's coaches, and then your coach's planning assistant may also read your check-in answers about pain and tiredness and your note. They can also see your answers to your club's start questionnaire, as you save them; the health answers only if you agreed to share them with your coach. You can withdraw that agreement at any time on the questionnaire's health step, and the health answers are then deleted. You are linked to a coach when you accept an invitation that names them (the invitation page tells you who your coach will be before you accept) or when you add your coach yourself under Account → My coach. The club's administrator can also link you to one of the club's coaches if you have never had a coach in the club, move you from your coach in the club to another of its coaches, or end that link; your health consent is for your coach in the club, so it then covers the coach you are moved to. A link that ended because you ended it or left the club is made again only by you, or by an invitation you accept. The club's administrators can see the same about every member of the club, with the same consent for health data, but never the health answers of the start questionnaire. Apart from these people, your health data is visible only to you.

You can end the link with your coach at any time from Account → My coach; the coach loses access immediately.

6.2 Service Providers

We share data only with the following categories of processors, strictly to operate the platform:

ProcessorPurposeLocation
RailwayBackend computation hostingEU
VercelWeb application hostingEU/US (SCCs apply)
AnthropicAI text generation and web search, with the data listed in section 4US (SCCs apply)
SentryError monitoring (anonymized)US (SCCs apply)
Lemon SqueezyPayment processingUS (SCCs apply)
Auth0Authentication (your account and signing in)US (SCCs apply)
PostmarkTransactional email (notifications)US (SCCs apply)
Expo (650 Industries)Delivering the mobile app's push notifications (your phone's push token and the notification's title and text)US (SCCs apply)
Google (Firebase Cloud Messaging)Delivering notifications to Android phonesUS/EU (SCCs apply)
Apple (Apple Push Notification service)Delivering notifications to iPhonesUS (SCCs apply)

For processors outside the EU, we rely on Standard Contractual Clauses (SCCs) as the legal transfer mechanism under GDPR Article 46.

To find your official results we also use public websites that are not our processors: we read the results lists that race timers and organisers publish, and we search UTMB's public runner database, which receives your name as the search (see 3.3).

7. Data Retention

Data TypeRetention Period
Account dataUntil account deletion
Your phone's push tokenUntil you sign out of the app, the phone stops accepting notifications, or account deletion
Activity data from StravaUntil you revoke Strava access (then deleted within 30 days), or until account deletion
Data from Garmin ConnectUntil you disconnect Garmin Connect (in RunnersDNA or in Garmin Connect), when we delete it, or until account deletion
Data from Polar or COROSUntil you disconnect Polar or COROS in RunnersDNA, when we delete it, or until account deletion
Activity data from your watch or uploads, and health dataUntil account deletion, or upon disconnecting that source
Computed performance profilesUntil account deletion
Weekly check-insUntil account deletion
Start questionnaire answersUntil account deletion, or until you delete them: clearing an answer deletes it, and withdrawing your consent deletes the health answers
Official race results, your UTMB link and the spellings of your name on results listsUntil account deletion
Our copies of public results lists18 months after the race (or after we last read the list, when we do not know the race date); a line that matches one of our users and is not on their profile yet, at most 6 months more
Payment records5 years (Romanian fiscal law requirement)
Error logs30 days

When you delete your account, your account and the personal data linked to it are permanently deleted within 30 days, except where retention is required by law. From our copies of public results lists we remove the lines that match your name or a spelling of it we had kept, and a line printed with a longer form of your name (with a middle name, for example) when it is one of the results we had added to your profile. When another RunnersDNA user has that same name, a line with it may be theirs: we then remove it only when it is one of the results we had added to your profile; of each removed line we keep only a one-way fingerprint, so that the line is not added back if the list is read again. The rest of each list stays until its 18 months are up; a line kept for another user's result that is not on their profile yet stays at most 6 months more. Club texts that name you, such as the weekly club recap, belong to the club and are not deleted with your account; you can ask us to remove your name from them (see section 8).

8. Your Rights Under GDPR

As a data subject under EU/Romanian law, you have the following rights:

  • Right of access: Request a copy of all personal data we hold about you.
  • Right to rectification: Request correction of inaccurate data.
  • Right to erasure: Request deletion of your personal data. You can delete your account from the website (Account → Delete account) or from inside the mobile app (Cont → Șterge contul).
  • Right to restriction: Request that we limit processing of your data.
  • Right to data portability: Receive your data in a structured, machine-readable format.
  • Right to object: Object to processing based on legitimate interest.
  • Right to withdraw consent: Where processing is based on consent, withdraw it at any time.

To exercise any of these rights, contact us at privacy@runnersdna.app. We will respond within 30 days.

You also have the right to lodge a complaint with the Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP) at anspdcp.ro.

9. Connected Platform Permissions

Strava: You can revoke RunnersDNA's access to your Strava data at any time from Strava Settings → My Apps, or from Account → Strava → Disconnect in RunnersDNA. Either way, new data stops syncing, and within 30 days we delete every activity, sample and detail we received from Strava and everything we computed from it; your profile is recomputed from your other sources, if you have any. Data from your watch, your uploads, your official results and what you entered in RunnersDNA stays until you delete your account. When you delete an activity on Strava, we delete it here within 48 hours.

Garmin Connect: You can disconnect at any time from Account → Connected services → Garmin Connect → Disconnect in RunnersDNA, or from the Garmin Connect app (Settings → Connected Apps). Either way, Garmin stops sending us data, we delete the activities and health data we received from Garmin, and we stop writing workouts to your Garmin Connect account.

Polar and COROS: You can disconnect at any time from Account → Connected services → Polar (or COROS) → Disconnect in RunnersDNA. We then end our access at Polar or COROS, delete the activities and health data we received from them and stop reading (and, for COROS, writing workouts). If you remove RunnersDNA from your Polar or COROS account instead, we can no longer read anything new; what we already received stays until you press Disconnect in RunnersDNA or delete your account.

Intervals.icu: You can disconnect at any time from Account → Watch sync → Disconnect in RunnersDNA. You can also cut access from Intervals.icu itself by clearing or regenerating your API key in Intervals.icu → Settings → Developer Settings. Either way, new data stops syncing and RunnersDNA can no longer write to your Intervals.icu calendar. Existing data in your profile will remain until you delete your account.

10. Children's Privacy

RunnersDNA is not intended for users under the age of 16. We do not knowingly collect personal data from children under 16. If you believe we have inadvertently collected such data, please contact us at privacy@runnersdna.app and we will delete it promptly.

11. Cookies and Tracking

RunnersDNA uses only essential cookies required for authentication and session management. We do not use third-party advertising cookies or tracking pixels. You can control cookie preferences through your browser settings.

12. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will notify you via email or through a banner in the application at least 14 days before the changes take effect.

Continued use of RunnersDNA after the effective date of changes constitutes acceptance of the updated policy.

13. Contact

Bob Creative Copy SRL
Email: privacy@runnersdna.app
Website: runnersdna.app

This policy is governed by Romanian law and applicable EU regulations, including the General Data Protection Regulation (GDPR — Regulation (EU) 2016/679).