What we collect
Collected
Section titled “Collected”| Data | Notes |
|---|---|
| Page address and title | Cleaned in the browser and again on the collector |
| Referrer and UTM parameters | Of the visit’s first page |
| Browser, operating system, device type, language | From the user agent and language headers |
| Country, region, city | Looked up from the IP address, which is then dropped |
| Time on page, active time, scroll depth | One engagement event per page |
| Your events and conversions | Names and properties you choose |
| Heatmap clicks | Only if you turn heatmaps on; details |
| A daily visitor hash | See how counting works |
A user hash, only if you call identify |
A keyed hash of the id you pass, specific to your site; it links that signed-in user’s visits across days |
| Stripe payments, only if you connect Stripe | Amount, currency, fees, refunds, the visit it is credited to; never card details |
Never collected or stored
Section titled “Never collected or stored”- Cookies, local identifiers or fingerprints.
- Raw IP addresses: used in memory by the collector, never queued or stored.
- The text of what was clicked or the value of any field.
- Anything that links a visitor across your sites, or across days unless you call
identifyfor a signed-in user.
Location
Section titled “Location”Location and network come from a local copy of the free DB-IP Lite databases, updated monthly; the lookup happens on our servers and no address is sent anywhere. IP geolocation by DB-IP, CC BY 4.0. The network is what the datacenter bot signal uses: when it is missing, the trust report says the datacenter check did not run.
Where and how long
Section titled “Where and how long”Processed and stored in the EU. Kept while the site exists; deleting a site deletes its events, clicks, crawler reads and payments.