Legal
Privacy Policy
Last updated: 20 November 2026
1. Overview
OwnRun is built privacy-first: your runs, health metrics and training plans live on your device. Data you choose to import from a connected service (for example Garmin, COROS or Polar) is fetched through our backend proxy, processed in memory, and not stored on our servers — see §2 and the §6 connected-services section. This policy explains the limited data we do process, why, and the choices you have.
OwnRun is operated by Syspole Inc., a company incorporated under the federal laws of Canada. Syspole Inc. is the data controller for the limited data described here. You can reach us at [email protected].
2. Data stored on your device
Activity data (runs, distances, paces, heart rate, GPS tracks), health metrics you enter, settings, and generated training plans are kept in local storage on your device.
Except for the data sources you actively connect (such as Garmin, COROS or Polar), we do not send your raw activity or health data — routes, GPS tracks, heart rate or health readings — to our servers. When you connect a data source, the data is retrieved through our backend proxy, processed in memory only, and not stored on our servers; it is ultimately stored on your device. Two narrow exceptions: weather lookups send coordinates rounded to 4 decimal places (about 11 m) to our weather service, which forwards them to Apple Weather (iOS) or MET Norway (Android) (§7), and creating a custom plan sends the summary figures shown on the plan screen (weekly volume, longest recent run, experience level), which are not stored. Local data is removed when you delete it or uninstall the app; on iOS, sign-in tokens kept in the system Keychain may survive an uninstall until you sign out or delete the account.
3. Account and limited server data
OwnRun does not require a sign-up. On first launch the app creates a minimal anonymous account (a random identifier) so that a subscription and your device list can be tied to you.
The only data stored on our servers is: the account’s random identifier; if you choose to sign in with Google or Apple, the email address and sign-in identity attached to it; the list of devices you have used; your subscription and ad-free status; limited usage events (such as app open, plan created, and ad clicks or rewarded-video completions); if you send a support request, your message and the diagnostics it carries (user ID, device ID, app version, locale, and the app log you choose to upload); session security data (IP address, user agent, and the coarse country, city, and region derived from the IP address) used to protect accounts from abuse. That data is deleted when you delete your account.
Except for data sources you actively connect (such as Garmin, COROS or Polar), your runs, routes, GPS tracks, heart rate, and health readings are not sent to our servers.
Signing in is optional. You can delete your account at any time from Settings.
4. Advertising
The free version of OwnRun shows ads served by Google AdMob. Watching a rewarded video removes ads for 7 days, and a subscription removes them entirely.
The Google Mobile Ads SDK automatically collects and shares certain data for advertising, analytics, and fraud prevention: your IP address (which may be used to estimate the general location of your device), product interactions (such as app launches, taps, and video views), diagnostic information (such as app launch time and performance), and device and account identifiers (such as the Android advertising ID and app set ID). This data is encrypted in transit using TLS.
We never share your health or activity data with the advertising SDK, and it is never used for advertising. We do not pass your email address to it.
You can reset, limit, or delete your advertising ID in your device settings (Android: Settings → Google → Ads; iOS: Settings → Privacy & Security → Tracking). Users in the EEA and UK are shown a consent prompt. See how Google uses information from apps that use its services.
5. Health data
Any data read from Apple Health, Google Health Connect or Samsung Health is used only to display your own metrics. It is never uploaded to us, and it is never used for advertising or profiling.
6. Optional connections
Sign-in. Google and Apple sign-in is used only to identify you and to carry your subscription across devices. No activity or health data is uploaded.
Connected training services (Garmin, COROS, Polar). You can optionally connect a Garmin, COROS or Polar account to import your activities into OwnRun. Each is governed by the same rules below.
Connected training services — Garmin, COROS and Polar
If you choose to connect one of these accounts, OwnRun requests your explicit consent through the provider’s OAuth flow. We then receive only the activity data the provider exposes for the permissions you grant: activity summaries and activity files (FIT/TCX) with their route, time series, laps and heart-rate data. We do not receive daily health summaries (such as sleep or resting heart rate) from these connections.
How it is used. Only to provide the features you asked for: importing your activities into OwnRun, displaying them (route, splits, pace, heart rate, elevation), computing your own training metrics (training load, pace/HR zones, best efforts, race predictions), and adapting your plan.
Where it is processed. Requests are proxied through our backend hosted on Cloudflare Workers so that your provider credentials never live in the app. Activity payloads are processed in memory and returned to your device; we do not store your activities or health data on our servers. Your OAuth tokens are stored in Cloudflare KV, associated with your account, and deleted when you disconnect or delete your account.
Third parties. Cloudflare, Inc. (hosting: Workers, KV, D1, R2, Pages) processes this data solely on our behalf as our infrastructure provider. Garmin, COROS and Polar are the respective sources of the data. No other third party — no analytics provider, no advertising network, no data broker, and no AI or machine-learning service — receives or processes this data.
No sale, no sharing. We do not sell this data, do not share it with third parties for their own purposes, and do not use it for advertising or to train, evaluate or improve AI models.
AI. We do not use connected-service data, or anything derived from it, to train, evaluate or improve AI or machine-learning models.
Your controls. You can disconnect a service at any time in OwnRun → Settings → Connections, which deletes the stored tokens, or revoke access in the provider’s own account settings. You can correct or delete your imported activities on your device, and delete your account (which removes all server-side records). You may withdraw consent at any time; withdrawal does not affect processing that already took place.
7. Weather and maps
When you view the current weather or a forecast, the app sends coordinates rounded to 4 decimal places (about 11 m) to our weather service, which forwards them to Apple Weather (on iOS) or MET Norway (on Android). We never attach your account identifier to these requests. Apple Weather and MET Norway are governed by their own terms and privacy policies.
Map views request tiles from OpenFreeMap, which serves map data © OpenStreetMap contributors.
8. Third-party processors
We rely on a small number of service providers, each governed by its own terms and privacy policy: Cloudflare, Inc. (hosting: Workers, KV, D1, R2, Pages), Google (AdMob advertising, Google sign-in, and Google Play billing), Apple (Apple sign-in, App Store billing, and Apple Weather), MET Norway (weather on Android), OpenFreeMap (map tiles, with data from OpenStreetMap), and Garmin, COROS and Polar (data sources, when you connect them). Samsung Health data is read locally on your device and is not sent to us. We do not use AI or LLM services: plans and training numbers are produced by deterministic rules on your device.
9. Data retention
Data on your device stays until you delete it. On our servers: your account, device list, and subscription status are kept until you delete your account; support requests and ad-click/ad-watch usage events are kept for 12 months; ad-unlock records are kept until they are no longer needed for the purposes above and are reviewed periodically; the diagnostic logs you upload are kept for up to 7 days; internal provider-operation logs (which contain no tokens, credentials, email or health data — only a pseudonymous account hash for correlation) are kept for up to 30 days; session security data is kept for the life of the session (up to 30 days); and operational access logs (which do not contain your request contents, tokens, email, IP address, city, or health data) are kept for 3 days in hot storage, 3 months in analytics, and longer in cold archive.
10. Your rights
Depending on where you live, you may have rights over your personal data — including the right to access, correct, delete, or receive a copy of it, and to object to or restrict certain processing (for example under the EU/UK GDPR, or California’s CCPA/CPRA). We do not sell your personal data.
Because most of your data lives on your device, the main server-side data is your account. You can delete it from Settings, or contact us at [email protected] to exercise any of these rights.
11. International transfers
We use Cloudflare, a global infrastructure provider. The limited data described above may be stored and processed in countries other than your own, including the United States. Where required, we rely on appropriate safeguards, such as standard contractual clauses.
12. Security
Data is encrypted in transit using TLS. Account tokens are stored in your device’s secure storage (iOS Keychain / Android Keystore). We keep the data we hold to a minimum and do not store your runs or health data on our servers.
13. Children
OwnRun is not directed at children. We do not knowingly collect personal data from children, and the app is not intended for use by them.
14. This website
www.ownrun.app is a static website. It does not use cookies, analytics, or tracking, and it does not collect any personal data. Your light/dark theme choice is stored only in your own browser.
15. Changes
We may update this policy from time to time. Material changes will be posted here with a new effective date.
16. Contact
Questions about this policy? Contact us at [email protected].