GPX Viewer
GitHub Download

Privacy

This website and GPX Viewer Web Lite

  • Your GPX files stay on your device. Web Lite reads a file you choose or drop with your browser's File API and analyses it in your browser. The file, its coordinates and any heart rate, cadence, power or temperature values are never uploaded, stored on a server or sent to any analytics service.
  • Map images. To show a map, your browser requests the map images for the visible area from OpenStreetMap or OpenTopoMap. Those servers therefore receive your IP address, the area you are looking at and the address of this website (the HTTP Referer), as with any online map. They do not receive your file. Choose "No basemap" in Web Lite to make no map requests at all.
  • No analytics, no advertising, no tracking, no cookies. The website loads no third-party scripts or fonts; everything it needs is served from the website itself.
  • Browser storage. Your choice of appearance and the Web Lite settings (map, units, clock, gain threshold, graph options) are kept in your browser's local storage on your device only. Clear the website data in your browser to remove them.
  • Hosting. The hosting service records technical access logs (such as IP addresses and requested pages) under its own privacy terms. Downloads are served by SourceForge under its terms.
  • Offline use. Web Lite needs an internet connection for map images. Without them, the graphs and statistics still work.

The desktop applications

Author: A097MPRUS.

  • Your files stay on your Mac. Opening, analysing, editing and exporting GPX files happens locally. Opening a file never changes it; edits are written only when you save.
  • No account, no analytics, no tracking. The apps contain no analytics or advertising code and send no usage data.
  • What goes online, and when:
    • Map tiles: when a map is shown, the apps request the tiles for the visible area from the selected map service. The service sees which area you are looking at, as with any online map.
    • Search and addresses: when you search for a place or ask for an address, that text or point goes to Geoportail Luxembourg or Apple Maps.
    • Terrain: when you load official terrain, the route’s coordinates go to Geoportail Luxembourg (Luxembourg), IGN (France) or the AWS terrain tiles (elsewhere).
    • Route analysis: only when you choose “Analyze surface and route context”, the route’s coordinates go to Geoportail Luxembourg and to the OpenStreetMap Overpass service.
    • Route planning: when you draw a route with routing, the points go to BRouter.
    • Historical weather (version 0.3.0 and later): only when you press Retrieve historical weather (Weather inspector or Track menu), the apps send Open-Meteo (archive-api.open-meteo.com) a few places along the route, rounded to 0.01 degree (about 1 km), and the calendar days of the recording in UTC. The GPX file itself, exact times, elevations, names, waypoints and sensor values are not sent. Opening the Weather inspector only looks in the local cache and sends nothing. Open-Meteo receives the request under its own privacy terms (open-meteo.com/en/terms), including your IP address as with any web request.
    • Weather cache: answers are stored on your Mac (modern app: its sandbox Caches folder; Intel app: ~/Library/Caches/com.a097mprus.gpxviewer.macos.intel/Weather), at most 20 MB, oldest removed first. Answers for recordings older than eight days are kept until removed; newer ones are asked again after six hours. Clear weather cache in the Weather inspector deletes all of them.
    • Commercial maps (both Mac apps, only with your own key): when you show a Microsoft Azure Maps, TomTom, HERE or Mapbox map or layer (including live traffic and weather), the tiles for the visible area are requested from that company with your key, and for Azure Maps and HERE the visible area is also sent to get the credit line. Each company receives that under its own privacy terms and counts the requests against your account.
  • Keys and sign-in: API keys you enter are stored in the macOS Keychain. Geoportail sign-in happens on Geoportail’s own page; the app keeps only the session cookie and sends it only to Geoportail.
  • Location: the apps never ask for or use your current location.