Privacy notice

What oSplit stores about you, who helps us run it, and what you can do about it. Last updated: 20 October 2026.

What we store

Without an account, nothing about you: you can look at maps, replay races and use the Studio without signing in. Drafts, your GPS tracks and the edit keys of anything you published before accounts stay in your own browser.

If you sign in, we store:

• your name and, if you add it, your club;
• your email address and which sign-in methods are linked (email code, passkey, Google, Microsoft);
• your devices and sessions: the browser and system, and when each was last active;
• what you publish: map images, versions, courses, and who you share them with;
• GPS tracks you choose to share with a course: only the part of your run over the map (plus a margin of 300 m), as positions and times. Heart rate, elevation and device details are not kept. The runner name and club are the ones you type. Nothing is shared unless you switch sharing on, and the rest of your run never leaves your device;
• a security log of sign-ins, changes to your sign-in methods, sharing and deletions. It is kept for 180 days.

Internet addresses are not stored. We use a scrambled form of them (a keyed hash) only to slow down abuse, and it can't be turned back into an address.

We don't use advertising trackers. To count visits we use Cloudflare Web Analytics, which does not use cookies and does not follow you across sites. The one cookie we set is the session cookie that keeps you signed in; it is removed when you sign out.

The watch app

The oSplit app for Garmin watches needs no account and sends nothing about you. To get a course, the watch asks us for a four-character code. When you type that code on osplit.app (Send to watch), the course goes into a short-lived basket under that code, and the watch downloads it. The code, the course in it, and a scrambled form (a SHA-256 hash) of the key the watch reads it with are kept for 15 minutes and then deleted. This doesn't use your account, and nothing else is uploaded from the watch.

To slow down abuse we count requests per scrambled address, as above. Those counts are deleted after two days.

The courses stay on the watch until you remove them or uninstall the app. The activity the watch records is saved to your Garmin account like any other activity, under Garmin's own terms and privacy notice. Questions about the app: [email protected].

Who helps us

• Auth0 (Okta) runs the sign-in page and stores your sign-in details: your email address, any passkeys, and the link to your Google or Microsoft account. We never see or store a password, because there are none.
• Resend delivers the sign-in code emails that Auth0 sends.
• Cloudflare hosts the site, stores the data and images you publish, and provides the visit counts (page views, countries and browsers, without cookies).
• Google or Microsoft, only if you choose to sign in with them.
• Cloudflare Turnstile is a bot check shown only when you share a track without an account.
• OpenStreetMap data for Make from OpenStreetMap in the Studio comes first from our own copy, kept in our storage, so nothing leaves us. For an area our copy doesn't cover, or doesn't hold yet, our server asks the public Overpass service, sending only the rectangle you chose (its corner coordinates), so it doesn't see your address or account. Either way the result is kept for a day so a repeat of the same area is quicker.
• Terrain heights, for a course's climb estimate and for contours on a map made from OpenStreetMap, come from the open AWS Terrain Tiles (Amazon S3). Your browser fetches the tiles that cover the area, so Amazon sees your internet address and which tiles you ask for, not your account.
• Map tiles come from their providers (Esri, OpenStreetMap, OpenTopoMap), the Studio's satellite view from Google Maps, and some fonts and icons from Google Fonts, cdnjs and unpkg. Loading them shows your internet address and browser to those services, as any website that shows a map does.

How long

• Your account and what you published stay until you delete them.
• Sessions expire after 30 days without use (90 days at the most).
• The security log is deleted after 180 days.

Your choices

• Tracks: you choose who can see each track (everyone who can see the course, only the course organisers and you, or only you) and can hide your start time. You can remove a track at any time. The course owner can also remove tracks from their course. Where a course allows it you can share without an account; you then get a delete key (we keep only a scrambled form of it), and anyone with that key can remove the track.
• See your data: Account, then Download my data.
• Delete it: Account, then Delete account. This deletes your courses and the maps that only you used, and also deletes your sign-in records at Auth0, and the tracks you shared. A map that other people have courses on stays, without an owner, so their courses keep working.
• Control who sees what you publish: each map and course is public, unlisted (only people with the link) or private (only you and the people you invite). You can change it, or remove people, at any time in Settings.
• Sign out on any device, or on all of them, in Account.

Contact

Questions or requests about your data: [email protected].