PRIVACY POLICY

I collect nothing. Not “almost nothing” — nothing. There is no account to create, no server to send anything to, and no analytics in the app. Your GPS, your drives and your photos are written to storage on your phone and stay there.

This is not a promise about how carefully I handle your data. It is a consequence of how the app is built: the code that used to talk to a server has been deleted, so there is no longer a path by which your data could leave the device, even by accident.

Earlier versions had sign-up, login and a guest mode backed by a server. All of that is gone. The app creates a local profile on first launch — a name you can set and a country you pick — and that profile exists only in your phone's storage. Nothing is registered anywhere.

While you drive, the app reads your location in the background and matches it against a road database stored on your device. Matching is arithmetic done locally — points are compared to road geometry downloaded ahead of time.

Your coordinates are not transmitted, because there is nowhere to transmit them to. They are used to work out which roads you covered, then deleted from the queue on your phone.

Your drives, the roads you have explored, your exploration history and your memories (photos pinned to roads) are stored in a database inside the app's own storage on your device.

That keeps them private, but it also makes them yours to look after: if you uninstall the app or lose your phone, they are gone, and I cannot recover them because I never had them. Back them up whenever you like with Export my data in Settings, which writes a zip file wherever you choose, and wipe them with Clear local data.

The app downloads region packs — the road databases it matches against — from data.exploreeveryroad.com, which is Cloudflare R2 storage. These are static files. The request says nothing about you: it asks for a file by name, the same file every other user of that region downloads.

To be straightforward about it, Cloudflare sits in front of that storage and, like any web host, can see the IP address making a request as part of serving and protecting it. I do not receive, store or look at those logs, and nothing in the request identifies you or your drives — but I would rather say so than claim a purity I do not control.

The map background is served by CARTO's public basemap tiles, which is a normal map-tile request from your device to them.

• —Location, including background — to record which roads you drive while the screen is off. Background access is what makes the app work at all: tracking that stops when you put your phone down would miss most of a drive. Processed entirely on the device.
• —Camera and photo library — only when you add a memory. The photo is copied into the app's local storage and never uploaded.
• —Internet — to download region packs and map tiles. Nothing is uploaded.

No contacts, no microphone, no advertising identifiers.

• —Your name, email address or phone number
• —A password — there is no account to have one
• —Your GPS coordinates, location history or trails
• —The roads you have explored
• —Your photos
• —Advertising identifiers
• —Usage analytics or behavioural data
• —Anything at all that could be sold to anyone

The app contains no analytics SDK, no crash reporter and no advertising library. Not “disabled by default” — not present. You can check: the source is on GitHub.

Road data comes from OpenStreetMap contributors (their privacy policy), region boundaries from national mapping agencies — all credited on the coverage page — Cloudflare for file hosting, and CARTO for map tiles. That is the entire list. No Google Analytics, no advertising networks, no session recording.

There is nothing on my side to delete, because there is nothing on my side. To remove everything, use Clear local data in Settings or uninstall the app. Both are immediate and final.

The app is intended for adults. It is not directed at children, and since it collects nothing, there is nothing it could collect from a child either.

If the app ever gains a feature that genuinely needs a server — syncing between devices, say — this page changes first, the change is described plainly, and it will be something you opt into rather than something that happens to you.

Want to check my work? The code is on GitHub, or get in touch and I'll answer directly.