Privacy
Your track file is never uploaded. This page lists every request that leaves your browser, and everything the studio keeps on your device.
What leaves your browser
- This site. Opening a page or the studio asks the site host for the page, its scripts, its fonts, and the sample track. The host sees an ordinary web request.
- Elevation tiles. To build the terrain, the studio asks AWS Terrain Tiles (s3.amazonaws.com) for the map squares that cover your route. If that fails, it asks Mapterhorn (tiles.mapterhorn.com).
- Imagery tiles. Only if you choose an imagery source. EOX 2016 uses tiles.maps.eox.at, and OpenTopoMap uses a.tile.opentopomap.org. With No imagery, no imagery request is made.
- Map features (opt-in). Off by default. Only if you turn on Map features, the studio sends the map area, not your route, to the Overpass API (overpass-api.de) to get OpenStreetMap peaks and lakes. With the switch off, no request goes to that service. Any future feature that contacts another service will also be opt-in, and this page will list it.
A tile request names a square of the map. The server that answers can see which squares you asked for, so it can tell roughly which area you looked at. It does not receive your track file, your route line, or your statistics.
What never happens
- Your GPX, FIT, TCX, GeoJSON, or KML file is not uploaded, copied, or sent to any server.
- There is no analytics and no tracking.
- There are no cookies.
- There is no account and no sign-in.
What stays on your device
The studio keeps your settings and the looks you save in your browser's local storage, under
the keys gpxtopo.settings.v2, gpxtopo.looks.v1, and
gpxtopo.mapFeatures.v1 (the Map features switch). A saved look holds
appearance settings only, never coordinates. Nothing in local storage is sent anywhere.
Clear your site data in the browser to remove it.
Posters, 3D-print files, and videos are built in your browser and saved straight to your device.
Fonts
The fonts are served from this site. No request goes to a font host.
For a practical walk-through, read how GPXTopo keeps your track private.