Usage records
The analytics database records visit time, page path, referrer domain, device class, browser family, interface language and a random tab-session identifier. Records may include country, region, city and approximate coordinates derived from the IP address using a local GeoIP database. Raw IP addresses are not stored in the analytics database.
Interaction events and metadata include place-search text, analysis and export actions, and an analyzed area's centre, size and simplified outline. The public map does not request names or contact details, but search text or share titles may contain information you choose to enter. Avoid entering sensitive information.
Sessions, cookies and Do-Not-Track
The measurement identifier is stored in the tab's sessionStorage, not a cross-site tracking cookie. Closing a tab does not delete records already received by the server. With DNT=1, the browser sends no usage beacons and the server discards them if received; necessary analysis requests and technical logs still operate. Known crawlers are filtered, but not every bot can be identified.
The public map needs no login. The admin dashboard uses an essential session cookie for operator authentication, form protection and dashboard language.
Your location and analyzed areas
Device geolocation requires browser permission. “Locate” moves the map; changing its view can request tiles and data for the displayed area. “Analyze around me” creates an area around your location and sends its boundary to the server for analysis. Drawing, searching, distance and elevation tools send the coordinates needed for your request.
Some results and source data are cached to avoid repeated requests. Durations vary: OSM analysis about one hour, street-network results about 30 minutes, and climate/population about 24 hours. Cache expiry stops reuse; it does not guarantee physical deletion at that instant. Analysis-event records are separate from these caches.
External providers
The server obtains data from providers including Overpass, Nominatim, Open-Meteo, PVGIS, WorldPop, Copernicus, USGS, OpenSky, CelesTrak, Sondehub and TeleGeography. Necessary request information, such as search text or area coordinates, reaches them through the server's connection.
Map and imagery tiles may load directly from your browser through OpenStreetMap, Esri, OpenTopoMap, NASA GIBS, RainViewer, OpenSeaMap, Global Forest Watch and Google Cloud Storage. Software libraries may load from CDNs such as jsDelivr and unpkg. Direct-request providers receive your IP address, connection information and requested resource path. Their own policies apply.
Saved areas and sharing
Your browser stores language, theme, basemap and saved areas/bookmarks locally, and may cache previously loaded resources and tiles. These can survive tab closure and can be cleared through browser site-data settings. Interface language is also sent in usage measurements when enabled.
Creating a share link stores the area's boundary, title, language, statistics snapshot and layers in the server's shares database. Anyone with the link can open it, and opens are counted. Shares currently have no automatic expiry. Clearing local bookmarks does not delete a share link or server records.
Logs, backups and retention
Web-server and security logs contain technical requests and may include IP addresses, User-Agent strings, timestamps and login errors. They are separate from analytics and rotated periodically. The daily maintenance task deletes pageviews and usage events older than 730 days when it runs successfully.
Analytics and shares databases are backed up with operational files, including offsite storage in Cloudflare R2. Full-backup settings retain the latest 14 local archives and offsite copies for 60 days. Deleting an active record does not immediately remove it from backups.
Controls and updates
You can deny geolocation permission, enable DNT and clear local browser data. These actions do not automatically erase existing server records. Closing a tab does not automatically fulfil a right of access or erasure; rights under applicable law remain in place. Material changes are recorded in the changelog.