Privacy policy

Overlandi is a route planner (web studio at app.overlandi.com) and navigation app (iOS) for mixed-surface riding and driving. This policy explains what personal data we handle, why, and the choices you have. We have tried to write it plainly. The short version:

• We collect what we need to run your account and your plans: your sign-in email, the routes you create and the settings you choose.
• Ride-trace recording is off unless you turn it on. If you opt in, the GPS track of rides you navigate is used to improve OpenStreetMap trail data. Publishing traces publicly to OpenStreetMap is a separate, second choice.
• No ads, no ad tracking, no cookies, no analytics SDKs. We don't sell your data.
• You can delete your account, and everything linked to it, from inside the app.

1. Who we are

Overlandi is run by JG Media Limited (a company registered in England and Wales, company number 10882020), the controller of your personal data. For anything privacy-related, including the rights in section 4, email us atjgmedia@outlook.com. We have not appointed a Data Protection Officer; that address reaches the person responsible for data protection.

2. What we collect, why, and for how long

2.1 Your account

You sign in with Google or Apple. We receive and store youremail address and that provider's account identifier, plus the time you created your account and when you were last active. We do not receive or store your name or profile picture. If you sign in with both providers using the same verified email they are linked to one account. Apple's "Hide My Email" relay addresses work.

Signing in gives your device a session token (valid for 30 days), kept on your device — in the iOS Keychain or, on the web, in your browser's local storage. We don't use cookies.

Why: to provide the service you signed up for (contract). Kept: until you delete your account.

2.2 Your plans and content

Routes, waypoints, tracks, imported GPX/KML/TCX/FIT files, notes, markers, analyses and your preferences (e.g. units) are stored on our server so you can use them on any device. We keep the last 12 saved versions of each plan so you can undo mistakes, and back plans up daily. Plans you share with other people (share links, ride groups) are visible to them.

Why: contract. Kept: until you delete them or your account. Each daily backup is kept for 30 days and then deleted. When you delete your account we also erase your plans from the backups straight away; anything that can't be erased at once is gone within those 30 days.

2.3 Your location while you use the app

The iOS app uses your device's location to show you on the map and to navigate. This is processed on your device. When you ask for a route, search a place or look for nearby fuel/camps, the relevant coordinates are sent to our server to compute the answer; they are not stored unless you save them in a plan.

The app asks for "While Using" location, keeps location running in the backgroundonly while you are navigating (so guidance and crash detection keep working with the screen off), and asks for "Always" location only if you share your location with a ride group. Precise location can be granted temporarily.

2.4 GPS ride traces — only if you opt in

Recording is off by default. You can turn it on in Settings (or when the app asks you once, after your first navigation). When it's on:

• What: while you navigate a route, the app records your GPS positions — latitude, longitude, time, speed, heading, elevation and GPS accuracy — and the name of the plan you were following. Nothing is recorded when you are not navigating. If you import or sync recorded tracks (with timestamps, e.g. from a Garmin), those are used the same way; planned routes are never used.
• Privacy zone: before a ride is analysed, stored or shared, we cut off the part within 200 m (in a straight line) of where it starts and where it ends — usually your home. A short ride that never leaves that zone keeps no track at all.
• Why: we filter out GPS noise and compare your ride with OpenStreetMap to find trails drawn in the wrong place and paths that are missing, and to improve our road-surface estimates. The results are combined with other riders' into statistics about map features that do not identify you; suggested map fixes are reviewed by people — we never edit OpenStreetMap automatically from traces.
• Legal basis: your consent. We record when you gave it and which version of this explanation you saw.
• Kept: raw points are deleted as soon as the ride has been analysed (usually within minutes; if the app stops before the ride is finished, it is analysed after 48 hours without new points). A cleaned, simplified copy of each ride (with the privacy zone removed) is kept privately in our storage for up to 24 months, or until you delete it sooner (Settings › Delete my recorded rides) or delete your account. The combined, de-identified statistics are kept.
• Turning it off: any time, in Settings on iOS or the web. Rides not yet analysed are deleted immediately, and anything still waiting on your phone is discarded.

Publishing to OpenStreetMap (separate opt-in). If you link your OpenStreetMap account and separately turn on "Also publish to OpenStreetMap", each cleaned ride (with the privacy zone removed) is uploaded to OpenStreetMap's public GPS-trace store, by default as an anonymous "trackable" trace (shared without your username, as timestamped points, and not listed publicly). Once uploaded it is held by the OpenStreetMap Foundation under its own policy; you can delete it on openstreetmap.org.

2.5 Ride groups, safety and crash detection

If you join a ride group, the members can see your latest position, heading and speed, any help/SOS request you raise (including an automatic crash alert), hazards you report and group chat messages, along with your email address. We store only your latest position, not a history, and delete it 24 hours after your last update (an active help/SOS alert is kept for 72 hours after it was raised). Crash detection is off unless you turn it on (Settings › Safety). When on, it uses your phone's motion sensors on the device; nothing is sent unless an alert is raised.

Why: contract (you asked to ride with a group); the safety features are in your and the group's vital interests. Kept: your latest position as above; hazard reports and chat messages for 90 days. All of it goes sooner if the group/plan is deleted or you delete your account.

Reports and blocks: if you report a message or a member, we keep the report (who reported, who was reported, a copy of the reported message, the reason and any note) so we can review it. It is deleted 180 days after we close it. Your block list is kept until you unblock someone or delete your account. Group text is checked against a short list of offensive words, which are masked before the message is stored.

2.6 Map contributions (surface surveys and OpenStreetMap edits)

If you answer "what surface is this track?" prompts we store your answer, the location and the way. If you link your OpenStreetMap account (we store its access tokens encrypted, plus your OSM username), your confirmed answers are published as edits underyour OpenStreetMap username — public, by design. If you delete your Overlandi account, answers that already became OpenStreetMap edits are kept without your account attached (so we don't ask the same question again); the edits themselves remain on OpenStreetMap.

2.7 AI co-driver

The optional route co-driver sends your messages, the recent conversation, a short description of your plan (e.g. its name and number of tracks) and the results of the tools it uses (e.g. place searches, waypoints) to an AI provider — Google (Gemini) orAnthropic (Claude). If you add your own API key, it is stored encrypted (AWS KMS) and the request is made under your agreement with that provider. Otherwise (Pro on iOS) it is made with ours. We keep the conversation in memory only while you use it; we don't store chat history. We count AI usage per account to enforce fair-use limits.

2.8 Other connections you choose

• GitHub (plan version history): your access token is stored encrypted and plans are committed to the repository you choose.
• AI agents via MCP: if you connect an agent, we store the connection and its tokens until you revoke it.

2.9 Payments

Overlandi doesn't currently sell anything, so we collect no payment details. If we introduce a paid plan, payments will be handled by a payment provider (such as Stripe or Apple) that processes your payment details; we would never see your card. We will update this policy before that happens.

2.10 Usage statistics and logs

• Usage statistics: we record service events (e.g. "route computed", "navigation started") with a pseudonymous account code (a hash keyed with a secret, not your email or account id), a coarse location rounded to about 1 km, and your app/browser type. They never include your email address, plan names or anything you type (such as hazard notes or chat). Detailed events are deleted after 7 days; per-minute counts (which hold no account codes) after 90 days. Basis: legitimate interests (keeping the service running and sized).
• Ride stats (app, on by default — turn off in Settings → Privacy): while you navigate, the app sends a small update about every 10 seconds so we can see how rides go and fix problems. It carries a random ride ID that changes every ride (not your account ID); your rough area as a ~1 km grid square (never within about 1 km of where a ride starts or ends); your speed range, routing profile, route length and progress, whether you're on the route; counts of reroutes, off-route moments and routing problems; and app health (frame-rate band, device temperature state, Low Power Mode, memory warnings, app and map version). Our server also records the IP address each update comes from, so this information can be linked to you. We keep no route or track: the live view holds only the latest square, for at most 2 minutes. Stored ride events (which hold no location finer than a country or region and no ride ID, but do hold the IP address) are deleted after 30 days; per-minute counts (no IP) after 90 days. Turning the setting off sends nothing. Basis: legitimate interests (keeping navigation working well; security and abuse prevention).
• Marketing site: overlandi.com sends a random per-tab identifier and the page path so we can count visitors. No cookies and no third-party analytics; the request reaches our server, so its IP address is in our server logs (below).
• IP addresses — server and CDN logs: our server logs every request (time, your full IP address, and the URL with any sign-in token removed), and our CDN (Amazon CloudFront, which serves the website, map data and app files) keeps access logs with the IP address and the requested address. We use these for security and abuse prevention (e.g. spotting and blocking attacks, enforcing rate limits) and for service analytics (load, errors, performance). Server and CDN logs, like the IP addresses kept with ride stats above, are deleted after 30 days. Basis: legitimate interests (security, abuse prevention, running the service).

3. Who processes your data

We use the following providers. Those marked processor act only on our instructions.

Some of these providers are in the USA. Where personal data leaves the UK/EEA we rely on UK adequacy regulations (including the UK Extension to the EU-US Data Privacy Framework, for providers certified under it) or, otherwise, the UK International Data Transfer Agreement or the EU Standard Contractual Clauses with the UK Addendum. We don't sell or rent personal data, and we don't share it for advertising.

4. Your rights

Under UK and EU data-protection law you can:

• Access your data and get a copy. Plans export as GPX from the app; for everything else, email us.
• Correct it.
• Delete it. Settings › Delete account removes your account, plans, settings, saved keys, ride traces, group data and connections, and signs you out everywhere. Your plans are erased from our backups at the same time, and backups are never kept longer than 30 days in any case. Settings › Delete my recorded rides removes ride traces alone.
• Withdraw consent to ride-trace recording or OpenStreetMap publishing at any time in Settings. This doesn't affect what was done before.
• Object to or restrict processing based on legitimate interests, and port your data.
• Complain to a supervisory authority: in the UK, the Information Commissioner's Office (ico.org.uk); in the EU, your local data-protection authority. We'd appreciate the chance to help first.

5. Security

Connections are encrypted (HTTPS). API keys and OpenStreetMap/GitHub tokens are encrypted at rest with AWS KMS. Access to production systems is limited to the operator.

6. Children

Overlandi is not intended for anyone under 13. If you believe a child under 13 has given us personal data, email us and we will delete it.

7. Changes

We'll update this page when what we collect changes. If a change affects ride-trace recording, the app will ask for your consent again before recording.