Cookieless analytics
Cookieless analytics — no cookies, no consent banner
Every cookie banner costs you visitors — the ones who decline vanish from your numbers, and the banner itself annoys the rest. Cookieless analytics removes the banner entirely, because there's no personal data to ask permission for.
What “cookieless” actually means here
Satsu never sets a cookie or stores a persistent visitor ID. To count a returning visitor within a day, it derives a throwaway fingerprint that rotates every 24 hours and can never be reversed to a person. No profile follows anyone across days or sites.
- No cookies, no localStorage, no persistent IDs
- Raw IP and user-agent are never stored
- The daily secret rotates — yesterday's hash is unrecoverable
- Sessions are derived on the fly, never persisted
Why that removes the consent banner
Under GDPR and the ePrivacy Directive, you need consent to store or read information on someone's device and to process personal data. Satsu does neither — so there's nothing to consent to, and no banner required. It's compliant by design, not by disclaimer.
You stop losing visitors
With no banner, no one clicks “reject” and disappears from your analytics. You see all your traffic, your numbers are complete, and your visitors get a cleaner site.
Frequently asked questions
Do I really not need a cookie consent banner?
Correct. Because Satsu stores no personal data and sets no cookies, there is nothing under GDPR or ePrivacy to request consent for — so no banner is required.
How does Satsu count returning visitors without cookies?
It derives a daily-rotating fingerprint from non-identifying signals that can't be reversed to a person and is discarded every 24 hours. It's enough to de-duplicate visits within a day, without tracking anyone across days.
Is cookieless analytics accurate?
For the metrics most sites care about — visitors, pageviews, sources, goals — yes, and often more complete than cookie-based tools, because you don't lose everyone who declines a banner.