Analytics without cookie consent is legal in Europe only in specific, narrow situations. In France, the CNIL accepts audience measurement without consent if the tool meets strict conditions. In the UK, since 5 February 2026, PECR allows cookies used solely for statistics to improve your site, with a simple opt-out. And analytics that never touches the visitor's device, such as server log analysis, falls outside the cookie rules altogether. What doesn't work is assuming a tool labelled "cookieless" is automatically exempt: fingerprinting, local storage and many pixel techniques are caught by the same rules as cookies.
This guide sets out the three legal routes, what each requires and how to choose a setup that gives you usable data on visitors who never click "Accept".
General information, not legal advice. Exemptions differ by country, so check the regulator's guidance where your audience is.
Why analytics normally needs consent
The ePrivacy Directive (and PECR in the UK) requires consent to store or read information on a user's device unless it is strictly necessary for a service the user requested. Measuring your audience helps you, not the visitor, so it isn't strictly necessary. That rule applies to cookies, local storage, pixels and device fingerprinting alike, as the EDPB's Guidelines 2/2023 make clear.
The GDPR applies on top whenever the data relates to an identifiable person, and IP addresses and unique identifiers usually do. So there are two questions for any analytics tool: does it need ePrivacy consent, and what is its GDPR lawful basis?
Route 1: CNIL exempt analytics (France)
The CNIL accepts that some audience measurement is so closely tied to running a website that it can be exempt from consent, provided users are informed and can object. Its conditions, set out in its guidance on analytics on websites and applications, include:
- Purpose limited strictly to audience measurement (and A/B testing) for the publisher.
- Only anonymous statistical outputs; no cross-referencing with other data such as customer files.
- Trackers limited to a single site or app, not following users across sites.
- The last byte of IP addresses truncated.
- Tracker lifetime capped at 13 months, and collected data kept no longer than 25 months.
- Users informed and able to object.
- Where a provider serves many publishers, each publisher's data kept separate.
The CNIL itself warns that most large audience measurement offerings don't fall within the exemption by default, and points to configurable tools such as Matomo. Several analytics vendors publish CNIL-exemption configuration guides; if you rely on one, keep a record of the settings you applied.
Note that this is a French position under French law. Other EU regulators may take a different view, and Germany, for example, has no general analytics exemption.
Route 2: the UK statistical exemption
The Data (Use and Access) Act 2025 added a statistical-purposes exception to PECR. You can use cookies without consent if their sole purpose is collecting statistics on how your site is used to improve it, the data isn't shared except with someone helping you make those improvements, users get clear information and users have a simple, free means of objecting.
The ICO interprets the sharing condition as allowing a third-party analytics provider only where it acts as your processor and uses data solely to help you. Its guidance also stresses single purpose: a tag doing analytics and advertising doesn't qualify. We cover the conditions and how to build the opt-out in the Data (Use and Access) Act cookie exemptions.
| CNIL exemption (France) | UK statistical exemption | |
|---|---|---|
| Legal source | Regulator interpretation of the strictly necessary exemption | Written into PECR (Schedule A1) |
| Opt-out needed | Yes | Yes, simple and free |
| Third-party tools | Yes, if configured and data kept separate per publisher | Yes, if acting as your processor only |
| Specific technical limits | IP truncation, 13-month trackers, 25-month retention | No fixed numbers; sole statistical purpose |
| Covers advertising | No | No |
Route 3: cookieless analytics and the GDPR
"Cookieless" is a marketing term. Legally, what matters is whether the tool stores or accesses anything on the device. There are broadly three types:
Server-side log analysis
Analysing your own web server or CDN logs reads nothing from the device beyond what the browser sends to load the page. This generally falls outside the ePrivacy consent rule. The GDPR still applies to IP addresses in logs, so you need a lawful basis (often legitimate interests), short retention and a mention in your privacy notice.
Script-based tools without storage
Some privacy-focused tools run a script but store nothing on the device, counting visits through daily rotating hashes or aggregate counters. Whether these need consent depends on exactly what the script reads. A script that collects detailed device characteristics to build a recognisable fingerprint is accessing information on the device and is likely within scope.
Fingerprinting
Combining screen size, fonts, browser settings and similar signals to recognise a returning device is treated by regulators as equivalent to cookies, and it's harder for users to control. It needs consent, and the ICO has been openly critical of fingerprinting for tracking.
Server-side tagging is different. Moving your tag manager to a server doesn't remove the consent requirement if the browser still sets cookies or sends identifiers for analytics or ads. See is server-side tracking GDPR compliant?
Choosing privacy friendly analytics
For an affiliate or adult site, the right tool depends on what decisions you make with the data. Most publishers need sessions, sources, landing pages and out-clicks; revenue and conversions come from affiliate dashboards and postbacks anyway.
| Option | Consent position | Trade-off |
|---|---|---|
| Self-hosted Matomo configured to CNIL criteria | Can meet the French exemption and fit the UK one; consent elsewhere in the EU unless locally exempt | You run the server and updates |
| Hosted privacy-focused analytics with no device storage | Often outside consent rules if nothing is stored or read for tracking; check per tool | Fewer features; verify vendor claims |
| Server log analytics | Outside ePrivacy; GDPR applies | Bot noise, limited behavioural data |
| GA4 behind consent | Consent needed in the EU, usually in the UK too | Rich data, but only from those who accept |
A common hybrid is a consent-free statistics tool for everyone plus GA4 or ad measurement only for visitors who accept. It works, but don't merge the two datasets per user, or the exempt tool stops being exempt. For tool comparisons, see Google Analytics alternatives for affiliate and adult sites and our tracking platforms directory. And if you're wondering where GA4 fits, read is Google Analytics GDPR compliant?
Matomo without consent: a configuration checklist
- Host it yourself, or with a provider acting only as your processor.
- Anonymise IPs to at least two bytes, which exceeds the CNIL's one-byte requirement.
- Disable cross-site tracking, User-ID and ecommerce features that link to customer data.
- Set cookie lifetime to 13 months or less, or disable cookies entirely.
- Set data retention to 25 months or less.
- Add an opt-out mechanism on your cookie or privacy page, and mention the tool in your notices.
- Keep screenshots of the settings with the date.
Frequently asked questions
Can I use analytics without a cookie banner?
Only if your analytics, and everything else on the site, is either exempt or doesn't touch the device, and you still provide information and an opt-out where required. Most commercial sites have ad or affiliate tags that need consent, so a banner remains necessary.
Is cookieless analytics GDPR compliant?
Not automatically. Cookieless tools can still process personal data, such as IP addresses, which requires a lawful basis, and some read device information in ways that need ePrivacy consent. Check how the tool works rather than relying on the label.
Does the CNIL exemption apply across the EU?
No. It is the French regulator's interpretation. Other authorities may be stricter, so for multi-country EU traffic many sites either rely on consent or choose tools that store nothing on the device.
Next steps
Decide which route fits your traffic mix, configure the tool to match and document it. Then update your banner and privacy notice. More guides on consent and tracking are in our GDPR and cookies section.