mapbench

Privacy Policy

Last updated: September 2026

The short version

  • No account is ever required.
  • Files you open (KML, GPX, GeoJSON, CSV) are parsed entirely in your browser and never uploaded to our servers.
  • Coordinates you enter stay in your browser, except where a tool needs an external answer (below) — and then only the coordinates themselves are sent.
  • We do not sell, share or profile. If ads are displayed, they are clearly marked slots and do not receive your tool inputs.

External services your browser talks to

Some tools need live data. When you use them, your browser contacts these public services directly:

  • Map tiles — OpenFreeMap (data © OpenStreetMap contributors).
  • Place search — Photon (komoot), based on OpenStreetMap.
  • Reverse geocoding — Nominatim (OpenStreetMap). Sent: one coordinate pair per request.
  • Routing & isochrones — FOSSGIS Valhalla (with OSRM fallback for driving). Sent: your stops' coordinates.
  • Elevation — Open-Meteo. Sent: sampled coordinates.
  • Nearby places — Overpass API (OpenStreetMap). Sent: centre point and radius.

These requests come from your browser, not from our servers, and are subject to each provider's own privacy policy and fair-use terms.

Geolocation

"Use my location" uses your browser's Geolocation API. Your position is shared by the browser with this page only; we do not store or forward it beyond the reverse-geocoding request needed to show an address. Denying permission never breaks a tool.

Local storage

We store one preference — your light/dark theme choice — in localStorage. Tool states (map position, radii, pins) live in the URL so they can be shared; nothing is written server-side.

Analytics & advertising

If aggregate analytics are enabled in the future, they will be privacy-preserving and documented here first. Reserved ad slots never overlay maps, results or download buttons, and ad providers never receive your coordinates or files.

If Google AdSense is enabled, Google and its advertising partners may use cookies, web beacons, IP addresses and similar identifiers to serve and measure ads. See How Google uses information from sites or apps that use its services for Google's current explanation of this processing.

Questions

If anything here is unclear, the source code of this site is the definitive answer — every behaviour described above is verifiable in the browser's network tab.