Privacy Policy

The short version

• Your runs are private until you share them.
• We never sell your data, and we show no ads.
• We never use your data to train an AI model.
• An AI model reads your data only when you ask: a watch photo you scan, or an app you connect.
• You can export everything, or delete your account, at any time.

What we hold

• Your account. Your email, and a name if you add one.
• Your runs. What you import (a Garmin or Strava export, or GPX, FIT and TCX files), read from Apple Health, or log. Your browser shows you what a file holds first; what you deselect never reaches us.
• Apple Health. In the iOS app, only if you connect it: your running workouts, with their routes, heart rate, distance and steps. We store them as your runs, on our servers. We never use them for ads, never sell them and never use them to train an AI model. An app or an AI assistant reads them only when you connect it. The app reads each new run as Apple Health saves it, also while the app is closed. We only read; we never write to Apple Health. To change what it shares, open Settings, Privacy & Security, Health on your iPhone.
• Where you ran. The GPS route of each run. It can show where you live, so it stays private until you share that run.
• Body measurements. Heart rate, power, VO2 max and training load, where your watch recorded them. Some laws treat these as health data.
• Photos. Stored privately and served through links that expire. A photo shows on your map only after you place it.
• A watch photo you scan. Sent to Google Gemini, or to Anthropic, to read the figures. We do not store it.
• What you write. Records, goals, plans, logged runs and group memberships.
• Notifications. One subscription for each device you turn them on for, with its timezone. On an iPhone, this is the app's device token. Turn notifications off, or sign out, and we delete it.
• Apps and agents you connect. An app such as Claude, or a token you make, reads your runs, races, Builds and plans. It adds to your plan only if you allow that. We store a digest of each token, never the token, and when it was last used. Runs from the Strava sync never reach an app. Disconnect in Settings and access stops at once.
• Membership. Stripe takes the payment. We store your membership state, never your card.
• Garmin. Only if you connect it: the tokens Garmin gives us, encrypted, the permissions you granted, and the runs Garmin sends. See Garmin below.
• Strava. Existing connections only: a read-only copy of the activities you authorized, with the tokens encrypted.

What other people can see

Nothing is public until you make it public.

• Your profile: private until you publish it. A public profile shows in ourpr. search and web search. AI training crawlers are kept out.
• A club page: your name and figures only if your profile is public.
• A run or a Build: only what you share, at a link you create.
• A pod: your week, to the people in that pod.
• A route you publish: its line and figures, found in ourpr. routes and web search.
• A route in print, such as a business card: only after ourpr. sends you a request for that route with the card, and you confirm it. You choose if your handle is on it. Withdraw at any time, and no new cards print. Cards already printed stay printed.
• Your routes for route discovery: only if you allow it in Settings. ourpr. reads your runs to find a route and keeps it in your Routes, private. Each route prints only after you confirm its request. Rescind the permission at any time.
• Your history and map: never.

A public page never shows activities from the Strava API.

How we use it

To show you your running, match runs to courses and places, show what you share, send the notifications and email you asked for and occasional news about ourpr., which you can stop from any email, and find and fix faults.

What we measure

• Signed in, we record a short list of acts with your account, such as opening Home. They appear in your export.
• When you open ourpr. from one of our emails, we note which email and which link. Our emails carry no tracking pixel, so we never know if you only read one.
• Vercel Web Analytics counts page views, with no cookie and no identifier that lasts past a day.
• Visits to public course pages are counted with no account, so we can tell a race organizer how many people their link brought.
• Our public MCP server records which tool an agent called and the name it gives, with no address and no account.

Who else handles your data

These services run parts of ourpr. for us. Each name links to its own policy.

• Supabase: accounts, database, photos.
• Vercel: the website.
• Render: the API.
• Cloudflare: map tiles.
• Mapbox: map tiles on a shared run page; it gets the map area, not your account.
• OpenStreetMap Nominatim: place names; it gets coordinates from your runs and photos, and no name or account.
• Sentry: fault reports; it gets your account ID, and no IP address or request content.
• Resend: email.
• Stripe: membership payments; it gets your email and account ID.
• Google: sign-in with Google, and Gemini reads a watch photo you scan.
• Anthropic: reads a watch photo you scan, when we use it in place of Gemini.
• Strava: existing connections only.
• Your browser's push service carries the notifications you turned on.

We also disclose data when the law requires it, or to protect someone's safety.

Garmin

When you connect Garmin Connect in Settings, Garmin asks you what to share with ourpr. We use only what you allow, and only for you:

• Courses and routes: we send the race courses and routes you choose to your Garmin Connect account and watch.
• Build plan: if you turn it on, we send the next two weeks of your Build plan to your Garmin Connect account as workouts. Turn it off and the ones ahead go.
• Runs: Garmin sends each run you complete, with its route, heart rate and splits. It joins your history, matches the run your plan called for, and shows on your public page only if you make that page public.
• VO2 max: if you allow health data, Garmin sends your watch's daily VO2 max estimate. We keep that one figure for the VO2 Max line on your Trends, which only you see, and nothing else of your health data.

We send data from Garmin only to Supabase, Render and Vercel, which store and serve it. No other service on the list above receives it.

An app or an AI assistant you connect, such as Claude, reads your runs from Garmin as it reads your other runs, and only while you keep it connected. We never use data from Garmin to train, evaluate or improve an AI model. We never sell it.

Disconnect in Settings, or in your Garmin Connect account, and we receive nothing more and delete the link. Your runs from Garmin stay in your history until you delete them or your account, and they are part of your export.

Export and delete

• Export. Open your history and export everything: runs, records and photos, in one file.
• Delete. Open Settings, choose Delete account, and type your email to confirm. It works the same on the website and in the app. It is immediate and permanent, and it ends a membership at once.
• Ask us. If you cannot sign in, email privacy@cordonate.io from your account's address, and we delete it for you.

After a delete, some things stay: fault reports in Sentry until they age out, place names with no link to you, a cheer you signed on a club page, copies other runners kept of a route you published, and the payment records Stripe must keep.

How long we keep it

Until you delete it. Notifications expire after 60 days. If you stop using ourpr., your history waits for you.

Security

The database lets each request reach only its own rows. Photo links expire. Tokens are encrypted or stored as digests. If something happens to your data, we will tell you.

Your rights

You can see, correct, export or delete your data, disconnect Garmin or Strava, and turn off notifications and non-essential email, all without asking. If your country or state gives you more rights, write to us and we will honor them.

Children

ourpr. is not for children under 13. If a child gave us data, tell us and we will delete it.

Changes

We post changes here and update the date. We tell you about a material change.

Contact

privacy@cordonate.io. Cordonate Labs LLC, Fort Worth, Texas. See also the Terms.