Skip to content

Privacy and data processing

Plain-language details about public-site analytics, browser-based project processing, map-tile requests, local storage, account data, and Google Sheets access.

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.

Address matching and US boundaries

When you explicitly choose address matching, the selected street, city, state and ZIP fields and temporary row IDs are sent through TerritoryKit to the US Census Bureau. Other spreadsheet columns are not sent to Census. Matching responses are not stored by the geocoding endpoint; imported matches become part of your local map and, if signed in, its private cloud save. ZIP, county and state boundary requests send geographic codes to Census TIGERweb. Hashed network identifiers temporarily enforce mapping request limits. Matching can be stopped; a request already received by Census may have been processed.

Uploaded project data

Map editing and analysis run in your browser. Local drafts use IndexedDB. When you sign in, we store your email and account identifier to identify your private workspace. Google sign-in also provides your Google identifier and name. Email sign-in sends your email address and a one-time code to Resend for delivery. Codes expire after 10 minutes, are stored as keyed hashes, and are deleted after use or expiry cleanup. Keyed identifiers derived from email and IP address temporarily enforce sign-in rate limits. Signed-in maps autosave geometry, records and presentation settings to private Cloudflare storage. Uploading a file to Workspace or leaving Save original files enabled during import stores an original copy in Cloudflare R2. Account and file metadata are stored in Cloudflare D1. Cloud saves remain until you delete them; local copies can remain in the browser after cloud deletion.

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.

Address search

Submitting an address or place search sends only that search text and normal request metadata to our configured geocoding provider, Photon by default. Searches run when you press Enter or select the search button. We do not send your datasets or territory geometry with these requests, and search text is excluded from analytics. A small results cache lasts only for the current browser tab session. Choosing a result moves the map and shows a temporary marker; the map viewport is saved with your project.

Local storage and project files

Projects are stored locally in the browser profile for the current origin. Demo includes one owned map, ten total exports and 200 MB cloud storage. Pro includes unlimited map and export counts with 2 GB storage. Maps and original files share the allowance. Shared maps do not count toward your owned-map limit. Local map saves and individual cloud transfers support up to 40 MB; browser and infrastructure capacity still apply. Local drafts are separated by signed-in account. Signing out removes the active server session but does not erase local drafts. Exported project files can contain original coordinate data, so treat them as data-bearing files.

Google Sheets

Connecting Sheets is optional. Google grants permission to view, edit, create and delete spreadsheets in your account; TerritoryKit uses it only to read selected source sheets and create or update its results worksheet. We use this access only for the spreadsheets you select. Refresh reads your source worksheet. Sync results writes records and territory assignments to a TerritoryKit results worksheet, replacing its previous values while preserving the source worksheet. Google refresh tokens are encrypted before storage and used only on the server. You can revoke access with Disconnect in Workspace or in your Google account permissions. Disconnecting does not delete previously imported records or saved maps.

TerritoryKit adheres to the Google API Services User Data Policy, including its Limited Use requirements, when using or transferring information received from Google APIs. Google user data is not sold or used for advertising or to train generalized AI models.

Payments and plan usage

Stripe processes subscriptions and stores payment details. We send your account name and email to Stripe when you start checkout; card details are entered on Stripe, never stored by TerritoryKit. We store Stripe customer and subscription identifiers, subscription status, paid-through dates and export operation counts to provide your plan. Export usage records do not contain map data or file contents. Checkout and billing management take place on Stripe.

Cookies and consent

Essential HttpOnly cookies maintain your sign-in, bind an email code to the requesting browser, and protect the Google authorization flow. Sessions expire after 30 days. These essential cookies are separate from optional analytics consent.

The consent preference is stored locally. Analytics does not load before acceptance.

Built-in boundary library

Boundaries picked in Territories → Add boundaries are static files served by TerritoryKit and downloaded one country at a time. Choosing areas does not send your map data anywhere.

Feature requests

When you submit the Request a feature form, we store the title, details, category, importance, the optional name and email you enter, whether you were signed in, and the page you came from. The request is emailed to the TerritoryKit team through Resend. We use your email only to reply about the request. Ask us to delete a request at any time.

Contact and data requests

Operator: Areeb Qamar. For privacy questions or requests to delete your account and stored data, contact areeb7676@gmail.com.

Build your first territory map

Bring your account list, draw the territories you need, and see the results as the map changes. Your first map is free.

Open Map Builder
Try one map free. Sign in for ten exports.