Documentation
Data Collection
Exactly what we collect, what we don't, and why.
Measure is designed so that tracking individual visitors is technically impossible. We only store aggregated counters — never individual data points, events, or sessions.
Here's exactly what happens when the Measure script fires on a page load.
What We Collect
- Page path — normalized, no query strings
- Referrer domain — just the domain
- UTM parameters — if present
- Country — IP discarded after lookup
- Device, browser, OS — then discarded
What We Don't Collect
- IP addresses
- Cookies or local storage
- Browser fingerprints
- Individual sessions or identifiers
- Personal data of any kind
How data flows
When the script fires, a single request is sent containing the page path, referrer domain, user agent string, and the visitor's IP address.
On our servers, the IP is used for a country lookup and then immediately discarded. The user agent is parsed into device type, browser, and OS, then also discarded. What remains is a set of anonymous, aggregated counters — nothing that could ever be tied back to an individual.
This architecture means you're automatically compliant with GDPR, CCPA, and PECR. No consent banner required.
Next steps
Continue exploring the documentation.
- AI Agent Analytics — detect and count traffic from AI agents
- All Documentation — back to the docs index