Privacy and data processing

What the public site tracks

The public site can load Google Tag Manager and GA4 only after analytics consent is accepted and a GTM ID is configured. Events are coarse product and marketing events such as opening the map builder, changing language, opening a guide, or completing an export.

What analytics never contains

Analytics must not contain uploaded file contents, filenames, latitude or longitude, map centers, polygon coordinates, GeoJSON/KML/KMZ content, spreadsheet column names, layer names, territory names, category values, customer names, arbitrary IDs, raw exception messages, or user-entered text.

Uploaded project data

Code verification shows the current builder is client-side. Imported project data is processed in the browser and saved locally with IndexedDB unless you export files yourself. There is no account system or TerritoryKit cloud workspace in the current product.

Map tiles and third parties

The builder requests basemap styles and tiles from the configured map provider. Those requests can reveal normal request metadata such as IP address and requested tile resources to that provider, but uploaded records and zone geometry are not attached to basemap requests.

Local storage and project files

Projects are stored locally in the browser profile for the current origin. Exported project files can contain original coordinate data, so treat them as data-bearing files.

Cookies and consent

The consent preference is stored locally. Analytics does not load before acceptance. The owner must confirm the final legal configuration for launch markets.

Owner placeholders

Legal name: TODO: add legal entity name before launch. Privacy contact: TODO: add privacy contact before launch.