Skip to content
  • Activity
  • Coach
  • Analysis
  • Pricing
  • Our Story
Download
Download
  • Activity
  • Coach
  • Analysis
  • Pricing

Privacy Policy

Effective date: 9 May 2026

Last updated: 17 November 2026

This Privacy Policy explains how Runmo Labs s.r.o. ("Runmo", "we", "us", or "our") collects, uses, and protects your personal data when you use the Runmo mobile application (the "App") and the website at runmo.app (the "Site"), together the "Service".

We have written this policy to be as clear as we can. Where we use defined terms from the EU General Data Protection Regulation (Regulation (EU) 2016/679, "GDPR") or Czech Act No. 110/2019 Coll. on Personal Data Processing, we have tried to explain them in plain language as well.

The App is available in English and Czech. This policy is published in English only.

Health data

Health and fitness data is special-category data under Article 9 GDPR. We process it only with your explicit consent: Apple Health’s permission sheet lets the App read it on your iPhone, and the AI Coach screen during setup lets the App send summaries of it to the AI coach. You can withdraw consent to AI processing at any time in Settings > Data > AI Features. Withdrawal stops all AI processing immediately and does not affect the training plan you already have. We never sell health data or use it for advertising.

1. Who we are

The data controller is Runmo Labs s.r.o. You can send privacy requests to support@runmo.app. This contact address is monitored by the people responsible for privacy at Runmo.

2. Privacy at a glance

We have built Runmo with a local-first approach. Most of your data (your runs, your routes, your heart rate, your training plans, your notes) lives on your device and in your personal Apple iCloud. We do not run a database that stores your runs or your health data on our servers.

In practice this means:

  • Your runs and health data stay on your device. We sync your profile, plans and logs between your devices using your own iCloud account. We cannot read them.
  • The AI coach is the one exception. When you ask the AI coach for a briefing, a plan, or a post-run analysis, we send a small, carefully limited summary of your training data to Anthropic, our AI provider, so it can generate a response. We never send your name, your email, your GPS coordinates, your routes, place names, or the raw second-by-second readings from your watch.
  • Analytics are pseudonymous, and you can switch them off. We use TelemetryDeck, which does not use cookies or advertising identifiers. Analytics cover which features you use, your trial and subscription purchases, and which Apple Ads ad brought you to Runmo, if one did.
  • We do not sell your data, ever. There are no ads in the App, we do not share your data with ad networks or data brokers, and we do not track you across other companies’ apps or websites.

The rest of this policy goes through each of these in detail.

3. The data we process

3.1 Account information

When you create a Runmo account we use Sign in with Apple. This means:

  • Apple gives us a stable pseudonymous user identifier.
  • Runmo asks Apple only for your name, and you can change it before you share it or later in Settings. We do not ask for your email address.

We store the identifier and your name on your device and in your own private iCloud database. We do not collect a password, Apple handles authentication.

So that you can revoke Sign in with Apple when you delete your account, our server swaps a single-use code from Apple for a revocation token. The token is stored only on your device; our server does not keep it.

3.2 Profile and preferences

During onboarding and inside the App you may tell us:

  • Your name and, if you add one, a profile photo
  • Your training goal (for example a race distance, race date and target time)
  • How many runs you want per week and on which days
  • Your preferred units (km or miles), the App’s language, and how your heart-rate zones are set
  • Your running shoes and the distance on them
  • Injuries and illnesses you log: what and where, how severe, and whether it is getting better. There is no free-text field.
  • The answers you pick to the coach’s questions

This information is stored on your device and synced to your personal iCloud. It is not stored on a Runmo database. Your health log is encrypted on your device before it is uploaded to iCloud.

3.3 Health and activity data

Runmo does not record runs itself. It reads the runs that your Apple Watch, or another app, saves to Apple Health. With your explicit permission, Runmo reads the following data from Apple HealthKit:

  • Workouts, including running workouts and their routes
  • Heart rate, resting heart rate, and heart rate variability (HRV)
  • Cardio Recovery (how much your heart rate drops in the minute after a workout)
  • Distance, active energy, and step count
  • Running stride length, ground contact time, and running power
  • VO₂ max
  • Height and date of birth (your age sets your default heart-rate zones)
  • Sleep analysis
  • Workout effort scores, both the ones you rate and Apple’s estimates
  • On iOS 27 and later, the heart-rate zones you have set in Apple Health

Runmo writes one thing back to HealthKit, and only if you allow it: a workout effort score, when you rate one of your runs.

HealthKit data is treated as a special category of personal data ("data concerning health") under Article 9 GDPR, which means we only process it when you have given us your explicit consent through the iOS HealthKit permission prompts. You can withdraw this consent at any time in iOS Settings → Health → Data Access & Devices → Runmo.

HealthKit data is read on your device and never leaves your device or your iCloud, except in the summarised form described in section 3.5 below, when you use the AI coach.

3.4 Location, routes and weather

Routes. When a run saved to Apple Health has a route, Runmo reads it to show it to you on a map. Maps are drawn by Apple’s MapKit.

Place names. To label a run with the town it started in, Runmo sends the run’s starting point to Apple’s geocoding service, which is part of iOS. Runmo keeps only the town’s name, which syncs to your iCloud.

Weather. If you allow location access, Runmo asks iOS for your location at kilometre-level accuracy when it needs the weather, and sends it to Apple WeatherKit. You can change this in iOS Settings → Runmo → Location.

We never send GPS coordinates, route polylines, or place names to our servers, to Anthropic, or to TelemetryDeck. The AI coach receives the weather without the place it was measured.

3.5 Data sent to the AI coach

If you have Runmo Plus or a trial, and AI features are on, the App sends requests to our coach API (hosted on Vercel at api.runmo.app), which relays them to Anthropic for AI inference. We have designed the request format to send the minimum data necessary for the coach to be useful.

The exact contents are documented in our source code as a privacy invariant. A request to the AI coach never contains:

  • GPS coordinates, exact or bucketed
  • Route paths, polylines, or place names
  • Run names, titles, or any text you have typed
  • Your name, email, Apple ID, or any device identifier
  • Raw heart-rate time series
  • Raw sleep numbers
  • Raw HRV or resting heart rate values
  • Your sex, which Runmo does not collect

A request to the AI coach does contain the following, in aggregated form:

  • Your fitness baseline: your age, your heart-rate zone limits, and a 5 km pace estimated from your recent runs
  • Your goal, how many runs you want per week and on which days, your average weekly distance, and an experience level worked out from your recent training
  • For recent runs: the date, distance, duration, average pace, average heart rate, elevation gain, and pace and heart rate per split; weekly totals for up to the last eight weeks
  • For a run you just finished, also its maximum heart rate, the time spent in each heart-rate zone, the time of day as a word (for example, “morning”), and how it compared with the planned session
  • Your readiness score and its trend, and short labels (for example, “improving”)
  • The injuries and illnesses you have logged: what and where, how severe, how they have changed, and how recently
  • Your training plan (dates, sessions, the AI’s own descriptions of them) and, when you start a new plan, a summary of the last one
  • Calendar dates only, never times of day, except the time-of-day word above
  • AI-authored memory summaries of past coach interactions, capped at 140 characters each
  • The coach’s questions and the answers you picked
  • Today’s weather where you are, without the location: temperature, humidity, wind, conditions, chance of rain, UV index, and a forecast for the next few hours
  • Your App’s language (English or Czech), so the coach replies in it, your units, and whether you are on a trial or a paid subscription

Our server also receives technical details it needs to handle the request: the App version, a key that stops the same request being processed twice (for a post-run analysis, a one-way code made from the workout; App versions before 1.0.7 sent Apple Health’s random identifier for that workout instead), and, for plan updates, a random identifier for your plan that is not derived from your account. These are not passed to Anthropic.

Each request to our coach API is signed using Apple App Attest, which proves the request comes from a genuine, unmodified Runmo install on a real Apple device. We do not link App Attest device identifiers back to your account.

Runmo’s coaching features are generated by Claude, an AI model from Anthropic. AI-generated content is labelled as such wherever it appears in the app, and can make mistakes. Your data is never used to train AI models.

3.6 Subscription information

Runmo Plus is an auto-renewing subscription, billed through Apple.

When you subscribe:

  • Apple processes the payment. We do not see, store, or have access to your payment card details.
  • Apple tells our App, via StoreKit, that you have an active entitlement to Runmo Plus.
  • We store this entitlement status locally on your device so the App knows what features to unlock.
  • If analytics is on (section 3.7), the App attaches its random install code to the purchase. Apple then sends our server a signed notification for each trial start, charge, renewal and refund, carrying that code, the product, the price you paid and its currency. Our server keeps these records only for installs that have reported where they came from (section 3.8), for about 400 days.
  • If analytics is off, the purchase carries no code, and our server only counts it, without linking it to anything.

For information about how Apple handles your payment information, please see Apple's Privacy Policy.

3.7 Analytics

We use TelemetryDeck for product analytics. TelemetryDeck is a German analytics service designed specifically to be GDPR-compliant. It does not use cookies or advertising identifiers.

Each analytics event we send is a short name (for example, app.session_start, coach.plan_generation_succeeded) with a few short labels and counts. Events cover:

  • which features and screens you use
  • your trial and subscription purchases, with the plan, the price you paid and its currency
  • which Apple Ads ad brought you to Runmo, if one did (section 3.8)
  • summaries of crashes and performance problems (section 3.9)

TelemetryDeck also adds standard technical details to each event, such as the App version, iOS version, device model, language, region and time zone settings, and accessibility settings.

We never send your name, your email, free-text input, run names, locations, or any value from Apple Health, not even rounded or bucketed. Each install is identified by a random code that resets if you delete Runmo.

You can switch analytics off in Settings > Data > Analytics. While it is off, the App sends nothing to TelemetryDeck, does not ask Apple about ads, and does not attach a code to your purchases. The setting stays off if you delete your Runmo account. If you delete the App and install it again, analytics is on again, under a new code. You can read TelemetryDeck's privacy practices at telemetrydeck.com/privacy.

3.8 Apple Ads attribution

We advertise Runmo on Apple Ads, Apple’s advertising in the App Store. To learn which of our ads work, the App asks Apple, once per install and only while analytics is on, whether an Apple Ads ad led to the install.

If one did, Apple answers with the ids of the campaign, ad group, keyword and ad, your App Store country or region, whether it was a download or a redownload, whether you tapped or only saw the ad, and where in the App Store it appeared. Apple does not tell us who you are.

The App adds the ad ids to its analytics events, and sends Apple’s answer to our server together with the install’s random code, when you first opened the App, the App version, and whether it is an App Store or TestFlight build. Our server keeps this record for about 400 days.

If you switch analytics off later, the App asks our server to delete this record, and it does. Purchase events already recorded stay until they expire. We never share this information with ad networks or data brokers, and we never combine it with data from other companies.

3.9 Crash and diagnostic data

If you have agreed to share diagnostics with Apple in iOS Settings, Apple will send diagnostic crash reports from Runmo to us through App Store Connect. We use these reports only to find and fix bugs.

The App also reads the diagnostic reports iOS keeps on your device (MetricKit). While analytics is on, it sends a short summary of crashes, hangs and performance problems to TelemetryDeck: the kind of problem, the name of the function where it happened, and the App and iOS versions. No stack traces and nothing you entered.

3.10 In-app feedback

When you use Suggest a Feature or Report an Issue in Settings, we receive the title and text you write, the App version, your device model, your iOS version, and the time you sent it. Before sending, the App removes anything that looks like an email address, a web address or a phone number. Our server forwards the message to a private Google Sheet that we own. It carries no account or install identifier, so we cannot reply to it. If you would like an answer, email us.

After a free trial ends, the App offers a short question about why you did not continue. If you answer it, we receive the reason you picked and anything you typed, with the same technical details and through the same route as the feedback above, again without any account or install identifier. While analytics is on (section 3.7), the reason you picked is also counted there. What you typed is never sent to analytics.

3.11 Communications with us

If you email us at support@runmo.app, we will receive your email address and the contents of your message. We use this to respond to your enquiry and keep a record of the support conversation.

4. Why we process your data; on what legal basis

Under the GDPR, we must have a legal basis for every type of processing. Here is ours.

What We Do

Why we do it

Legal basis

Run your account, sync your data, show you the App

To perform our contract with you (these Terms)

Article 6(1)(b) GDPR — performance of a contract

Read HealthKit data on your device

To compute your training metrics, plan, and coach output

Article 6(1)(b) and Article 9(2)(a) GDPR — your explicit consent (granted via the HealthKit prompt)

Send aggregated training data to the AI coach (Anthropic)

To generate your coach output

Article 6(1)(b) GDPR — performance of a contract; Article 9(2)(a) — your explicit consent, given by enabling the coach

Use your location for weather and place names

To show the forecast and label where your runs started

Article 6(1)(b) GDPR — performance of a contract, and only with your iOS location permission for weather

Process your subscription

To bill you (via Apple) and unlock Runmo Plus

Article 6(1)(b) GDPR — performance of a contract; Article 6(1)(c) — legal obligation (tax, accounting)

Send pseudonymous product analytics via TelemetryDeck

To understand which features are working and where the App needs improvement

Article 6(1)(f) GDPR. Our legitimate interest is improving the Service. We have balanced this against your interests; the data is pseudonymous and carries no health data. You can object at any time in Settings > Data > Analytics.

Learn which Apple Ads ads bring installs, and how trials and subscriptions convert

To know which of our ads work and how Runmo is doing as a business

Article 6(1)(f) GDPR. Our legitimate interest is spending our advertising budget well. You can object at any time in Settings > Data > Analytics, which also deletes your install’s record from our server.

Receive crash reports from Apple and diagnostic summaries from the App

To find and fix bugs

Article 6(1)(f) GDPR — our legitimate interest in providing a working App

Receive in-app feedback

To learn what to fix and build next

Article 6(1)(f) GDPR — our legitimate interest in improving the Service

Reply to support email

To handle your enquiry

Article 6(1)(b) GDPR — performance of our contract; Article 6(1)(f) — legitimate interest in supporting users

Comply with legal obligations (tax, fraud prevention, lawful requests)

Because we have to

Article 6(1)(c) GDPR — legal obligation

Where we rely on consent (HealthKit, the AI coach), you can withdraw consent at any time. Withdrawal does not affect the lawfulness of processing carried out before withdrawal.

5. Who processes your data

We use the following processors to provide the Service.

5.1 Anthropic PBC, United States

Anthropic receives aggregated training summaries, heart-rate zone boundaries, your age, a 5 km pace estimate, injury and illness entries including type, severity, and changes over time, current weather at an unnamed location, short memory summaries, training-plan metadata, and the App’s language. It never receives names, email addresses, Apple IDs, GPS routes, place names, individual workout identifiers, or raw heart-rate recordings. Anthropic’s commercial terms state that API inputs and outputs are not used to train models. Anthropic retains API traffic for up to 30 days and then deletes it, unless its systems flag a request as breaking its usage policy, in which case Anthropic may keep it longer under its own policy.

5.2 Vercel Inc., United States

Vercel hosts our server: the API that relays requests to Anthropic, the Sign in with Apple code exchange, the in-app feedback relay, and the endpoints that receive attribution records and Apple’s purchase notifications. It processes request data, including your IP address, in transit and retains runtime logs for one day. Those logs can include a short excerpt of a coach reply when our quality checks flag one.

5.3 Upstash, Ireland, EU

Upstash is our server’s database. It stores App Attest device keys, replay-protection markers, per-device usage counters, and short-lived rate-limit counters, some of them keyed to your IP address. It also stores the attribution and purchase records described in sections 3.6 and 3.8, a short marker for each plan update, and a newly generated plan for 24 hours so a retried request is not generated twice. It holds no health data and no run data. This data does not leave the EU.

5.4 TelemetryDeck GmbH, Germany, EU

TelemetryDeck receives usage analytics only: which features are used, trial and subscription purchases with their price and currency, the Apple Ads ad that brought the install, if any, and summaries of crashes and performance problems. Events carry no name, run data, or health data. Each installation is identified by a random code that resets when the App is deleted. You can turn this off in Settings > Data > Analytics.

5.5 Google

Google hosts the private Google Sheet where in-app feedback lands (section 3.10). It receives the feedback message and the technical details sent with it, and nothing else.

5.6 Apple Inc.

Apple provides iCloud sync of your data into your own private database and processes subscription purchases. We cannot read the contents of the health log stored there because it is encrypted on your device before upload. Apple also provides the services described above: Sign in with Apple, App Attest, StoreKit and its purchase notifications, Apple Ads attribution, WeatherKit, geocoding and maps, and the App Store, which supplies the icons of the apps that save your workouts to Apple Health (the App sends only those apps’ identifiers and your App Store country). Sending your plan to your Apple Watch (WorkoutKit) and the home-screen widgets work on your devices.

5.7 Professional advisers and authorities

We may share your data with our accountants, lawyers, or auditors when we need professional advice; with public authorities when we are legally required to do so; and with a successor entity if we ever sell or restructure the company. In each case the recipient is bound to keep your data confidential.

6. International transfers

Anthropic and Vercel are located in the United States. Transfers to them rely on the European Commission’s Standard Contractual Clauses. Google may process feedback messages in the United States; Google LLC takes part in the EU-U.S. Data Privacy Framework, which the European Commission recognises as providing adequate protection. Data processing terms with all of our processors are incorporated into the agreements we have accepted with them. Upstash and TelemetryDeck process data within the EU, so no third-country transfer applies to them. You may request further information about these safeguards at the contact address below.

7. How long we keep your data

We keep each kind of data only as long as we need it.

Data

Retention

Data on your device and in your iCloud

For as long as you keep the App installed and the data in your iCloud. Deleting the App or your iCloud data deletes it.

Account records

We hold no account record on our servers. Your Apple Sign-In identifier is stored only on your device and in your own private iCloud database.

Your name after you delete your account

Kept in your own iCloud Keychain, which we cannot read, so Runmo can fill it in again if you sign in later. Apple shares your name with an app only the first time you sign in.

AI coach requests

We do not log the contents of AI coach requests on our servers. Anthropic's retention is described in section 5.1.

Server runtime logs (Vercel)

1 day

Replay-protection markers

2 minutes

Rate-limit counters

Up to 2 hours

Usage counters

48 hours and 14 days

Newly generated plans, cached against retries

24 hours

Plan update markers (a random plan identifier and its revision number)

About 400 days

App Attest device-attestation records

1 year

Attribution and purchase records on our server

About 400 days from the last update; each renewal extends a subscription’s records. Switching analytics off deletes your install’s attribution record straight away.

Analytics events on TelemetryDeck

TelemetryDeck's standard retention applies.

In-app feedback

Up to 3 years from when you sent it, then deleted.

Apple subscription records

Held by Apple under Apple's policies.

Tax and accounting records (invoices, etc.)

10 years from the end of the relevant accounting period, as required by Czech Act No. 563/1991 Coll. on Accounting.

Support emails

Up to 3 years from your last contact, then deleted.

8. Your rights

Under the GDPR, you have the following rights. Access and portability under Articles 15 and 20: Settings > Data > Export Data produces an archive on your device of your runs, gear, training plans, health log, coach notes, profile and preferences. Nothing is uploaded and no network request is made. GPS tracks and heart-rate series stay in Apple Health, where you can export them from the Health app. Erasure under Article 17: Settings > Account > Delete Account removes local data and the iCloud copy (apart from your name, as described in section 7), and revokes the Sign in with Apple grant. Objection to analytics and ad attribution under Article 21(2): use Settings > Data > Analytics. Withdrawal of consent under Article 7(3): use Settings > Data > AI Features. Rectification under Article 16: edit your profile details in Settings. You can lodge a complaint with the Czech Úřad pro ochranu osobních údajů, ÚOOÚ, as the lead authority, or with the supervisory authority in your country of residence.

Analytics and attribution records are tied to a random install code, not to your account, so deleting your account does not remove them. Switching analytics off deletes your install’s attribution record from our server, and deleting the App gives a reinstall a new code. Because we cannot link these records to you, we may be unable to find them from an email request alone.

9. Children

Runmo is not intended for users under the age of 16. We do not knowingly collect personal data from anyone under 16. If you become aware that a child under 16 has used Runmo, please contact us at support@runmo.app and we will delete the relevant data.

10. Security

We protect your data using a combination of measures appropriate to the risk:

  • End-user device security. Most of your data lives on your device and is protected by Apple's device-level security (passcode, Face ID/Touch ID, file-system encryption) and your iCloud account.
  • Transport security. All communication between the App and our servers uses TLS 1.2 or later.
  • Request integrity. Every coach API request is cryptographically signed with Apple App Attest, which prevents replay and tampering. Apple’s purchase notifications are signed by Apple, and our server checks the signature before reading them.
  • Data minimisation. We do not store the contents of AI coach requests on our servers, and we keep no database of your runs or health data. The records we do keep are listed in section 7.
  • Access controls. Only a limited number of people at Runmo have access to our infrastructure, with multi-factor authentication required.

No system is perfectly secure. If we ever discover a personal-data breach that is likely to result in a risk to your rights and freedoms, we will notify the ÚOOÚ within 72 hours and notify you without undue delay where required.

11. Cookies and tracking on runmo.app

Our website at runmo.app uses no advertising cookies, no analytics cookies, and no third-party tracking. The only cookies it can set are session cookies that remember a units or region choice made through a link, and they are deleted when you close your browser. The site reads your browser’s language to show distances and prices for your region; that happens in your browser. Like any website, the company that hosts it processes the technical data each request carries, such as your IP address, to deliver the page. If this changes in future, we will update this policy and ask for your consent before placing any non-essential cookies.

12. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes we will notify you through the App and update the "Last updated" date at the top of this policy. We will keep previous versions available on request.

13. Contact

If you have any questions about this Privacy Policy or how we handle your personal data, please email us at:

support@runmo.app

Runmo

For those who want to level up their running

Product

  • Download
  • Release Notes
  • Pricing

Compare

  • Strava
  • Runna
  • Nike Run Club
  • Garmin Connect

Company

  • About
  • Support
  • Privacy Policy
  • Terms of Use