Help / About
Privacy and stored data
What leaves the browser, what stays in it, and how to clear it.
Models are built in the browser. Settings and models are never sent to a server of mine. Neither are the areas picked on the map, apart from what the LiDAR proxy below sees.
What is sent where
- Map data, elevation, LiDAR, and map tiles are downloaded straight from their public sources.
- Some LiDAR files come through a small proxy I run, which sees the IP address each request comes from and which file it asks for, like any server. It doesn't keep a log of them.
- Searching for a town or city uses a list built into the site. Searching for streets, addresses, and landmarks sends the search text to Photon (photon.komoot.io), or to Nominatim (nominatim.openstreetmap.org) when a search is tried again after Photon failed.
- The site counts visits with Cloudflare Web Analytics, which doesn't use cookies or track anyone between sites.
- It also counts how many models are generated and downloaded and how many fail, with roughly why, how long each took, how far it got, whether the page was hidden or closed while it ran, the kind of model, the browser or the app the site was opened in, and the site's version, never the area or the IP address.
- When something goes wrong in the site itself, it sends me the error, where in the code it happened, the browser or the app the site was opened in, and the site's version, without where the area is or the IP address. If the browser closes the page while it's generating or preparing a download, the next visit also sends the size of the area and the print, the settings that use the most memory, and how far it got.
No account is needed. Signing in is only for redeeming a code. An account stores an email address, its sign-in method, and its tier, never models. Asking for an emailed code goes through Cloudflare Turnstile, which checks that a person is asking.
What stays in this browser
Settings, routes, and edits are kept here, and the results of street and address searches for a month.
See the privacy page for details.