Privacy Policy
The short version
Your GPS files are processed entirely on your device. They are never uploaded, never transmitted to a server and never stored anywhere. This is not a policy promise — it is how the site is built: the converters, mergers, splitters and viewers run as JavaScript in your browser, and no file-upload endpoint exists.
What stays on your device
Every file you drop into a tool is read into your browser's memory, parsed by a background worker on your machine, and the result is offered back to you as a direct download. Close the tab and everything is gone. You can verify this yourself: open your browser's developer tools, watch the network tab and convert a file — no file bytes appear in any outbound request.
What does leave the browser
Three things, none of which involve your files:
- Map tiles. Map previews load OpenStreetMap tiles from
tile.openstreetmap.org. When a map is displayed, that server sees your IP address and which tiles you requested. Your track data is never sent to the tile server; only the map underneath it is fetched. - Anonymous analytics. This site uses Umami (self-hosted at
umami.selenium39.me, run by the same operator as this site) to count page views in aggregate. It sets no cookies and collects no personal data — just the page URL, referrer, country and device type. It cannot and does not see the contents of any file you process. - Support chat. A Crisp
crisp.chatchat widget loads on every page. If you open the chat and send a message, that conversation is handled by Crisp. If you never open it, no conversation exists.
Cookies, accounts and analytics
There are no accounts and no advertising scripts. The analytics above (Umami) are cookieless. The Crisp chat widget sets a session cookie only when you interact with it; blocking third-party cookies in your browser disables that without affecting any tool.
Contact
Questions about this policy: [email protected].