08 / 08

The privacy model

No cookies, no fingerprinting, no personal data at rest, and how the counting works.

No cookies, no fingerprinting

No cookies. No localStorage. No fingerprinting. No personal data at rest. Each pageview is attributed to a visitor hash computed from the request with a salt that rotates at midnight UTC, so a visitor cannot be recognised from one day to the next and an IP address is never stored. That is what lets you run analytics without a consent banner.

The hash is derived from the IP address and browser only for the moment it takes to count the view, then thrown away: the raw IP is never written down, the hash cannot be reversed, and a new daily salt makes it unlinkable across days, sites and devices. Geography is country-level only, derived at the edge, with no city or region. The performance beacon carries timings, not identifiers. Because the tracker reads and writes nothing on the device, it falls outside the ePrivacy cookie-consent rules, and the limited processing rests on legitimate interest under the GDPR.

Accuracy and the live demo

Counts are exact at typical traffic levels and become statistical estimates at very high volume, where per-site sampling keeps queries fast. See it all working on the live demo, which is this product pointed at motion.dev's real traffic. The full privacy policy sets out every field we collect, where it is processed and how long it is kept, and our data-processing agreement and sub-processor list cover the contractual side.