Cookieless analytics counts visits without setting a cookie or storing any personal data on the visitor's device. It identifies visits with a rotating, anonymous signal that resets daily instead of a persistent cookie, so no profile follows anyone. Because nothing personal is stored or read, a site using it needs no cookie-consent banner, including in the EU.
Traditional analytics gives each visitor a cookie — a small identifier stored in the browser — so it can recognise them across pages and days. That identifier is personal data, which is why cookie-based tools trigger a consent banner. Cookieless analytics answers the same questions (how many visitors, from where, to which pages) without ever storing that identifier.
How it works without a cookie
Instead of a persistent cookie, a cookieless tool derives an anonymous signal from information the browser already sends — and rotates it, typically once a day. Two page loads from the same person on the same day count as one visitor; the next day, the signal has changed and no link is kept. The result is an accurate count of visitors and sessions with nothing that identifies a person and nothing stored on their device.
What it can and cannot see
| Cookieless analytics sees | It does not see |
|---|---|
| Visitors, sessions and pageviews | A named or persistent individual |
| Referrer, country, device, browser | A profile that follows you between days |
| On-site journeys within a day | Cross-site browsing history |
| Conversions and revenue you tag | Anything to sell to an ad network |
Why it means no consent banner
The EU's ePrivacy rules require consent to store or read information on a device, and GDPR governs personal data. A tool that stores no cookie and processes no personal data triggers neither obligation, so no banner is required. That is the practical payoff: you keep measuring the visitors who would otherwise decline the banner and vanish from your numbers.
A cookieless tool that honours Global Privacy Control and Do Not Track will show slightly lower numbers than a cookie-based one — those are opt-outs being respected, not data going missing.
Open Analytics is cookieless by default: no banner, no personal data, and numbers you can trust.
See how it worksFrequently asked questions
- Is cookieless analytics GDPR compliant?
- Cookieless analytics that stores no cookie and collects no personal data falls outside the consent requirement of the EU's ePrivacy rules and GDPR, which is why it needs no banner. Compliance still depends on the specific tool's data handling, so check that it does not fingerprint or store identifiers.
- Is cookieless analytics accurate?
- For the questions most sites ask — visitors, sources, pages, conversions — it is accurate. It counts a daily-rotating anonymous visitor rather than a persistent one, so very-long-window return-visitor metrics are less precise by design. In exchange it captures the privacy-conscious visitors who decline a cookie banner and disappear from cookie-based tools.
- Does cookieless mean no tracking at all?
- No. It still measures traffic; it just does so without a persistent identifier or personal data. The distinction is between counting anonymous visits (cookieless) and building a profile of an identifiable person across sites and time (what cookies enable and what the banner exists to gate).
- Which analytics tools are cookieless?
- Plausible, Fathom, Umami, Simple Analytics and Open Analytics are all cookieless by default. Google Analytics is not: GA4 sets cookies and generally requires a consent banner. See our full comparison of privacy-first Google Analytics alternatives.