Privacy: Technical Details
This page explains the technical details behind our privacy promises: where data goes, what we log, what we don't, and how server-side proxies work without exposing your exact coordinates.
This page is for the curious or privacy-conscious — it explains the technical details behind our privacy promises.
Geolocation API runs client-side
The browser's navigator.geolocation.getCurrentPosition() call resolves entirely on your device. We only receive the result if you explicitly grant permission via the browser prompt. We never request high-accuracy continuous tracking.
Server proxies and coordinate truncation
When we need to do something with your coordinates that requires a server (like reverse geocoding), the request goes through our /api/reverse-geocode endpoint. The endpoint truncates coordinates to 3 decimal places (~100m) before any logging. The upstream call to Nominatim uses your full coordinates so the address is accurate, but our logs never see them.
No coordinates in URLs (by default)
We never include coordinates in URL parameters during normal operation. Sharing is the exception — when you explicitly choose to share, the share link contains coordinates because that's the only way to share a location.
Open source data sources
We use OpenStreetMap Nominatim (reverse geocoding), Open-Meteo (elevation and weather), SunCalc (sunrise/sunset), and ipwho.is (IP fallback). None of these require API keys or user-identifying tokens.