Cookieless analytics and GDPR: what EU law allows in 2026
Hephaestus Technology7 min read

Cookieless analytics is website or product measurement that counts visits and usage without storing cookies or other identifiers on the user's device. Under EU law it can reduce or remove the need for a consent banner, but it is not automatically exempt: the ePrivacy rules cover any storage of or access to information on a device, and the GDPR still applies if the tool processes personal data such as IP addresses. Ireland's Data Protection Commission says analytics cookies require consent, while France's CNIL allows a narrow exemption for audience measurement that meets strict conditions.
Key takeaways
- Two laws apply to analytics: the ePrivacy rules (device access, implemented in Ireland by S.I. 336 of 2011) and the GDPR (personal data).
- Removing cookies does not remove ePrivacy obligations if the tool still reads or stores information on the device, for example through fingerprinting or local storage.
- The DPC's guidance says analytics cookies need consent, though first-party analytics are unlikely to be an enforcement priority.
- The CNIL exempts audience measurement from consent only under strict conditions, and says most large analytics offerings do not qualify.
- Cookieless tools that hash request data with a rotating salt and store nothing on the device are the strongest option for consent-free measurement, subject to legal review.
What is cookieless analytics?
Cookieless analytics is measurement that does not place a cookie or similar identifier in the user's browser or app to recognise them. Instead of tracking a person across visits, it typically counts page views and events, and estimates unique visitors over a short window. The trade-off is less detail: no long-term user journeys, limited attribution and no cross-site tracking.
Which EU rules apply to analytics?
Two separate sets of rules apply, and you need to satisfy both.
- ePrivacy (device access). In Ireland, Regulation 5 of S.I. No. 336 of 2011 implements Article 5(3) of the ePrivacy Directive. It requires consent before storing information, or gaining access to information already stored, on a user's device, unless it is strictly necessary to provide a service the user explicitly requested.
- GDPR (personal data). If the tool processes personal data, you need a lawful basis under Article 6 of the GDPR, such as legitimate interests. Recital 30 notes that people can be associated with online identifiers such as IP addresses and cookie identifiers.
The DPC's cookie FAQ states that consent is the only lawful basis for the storage of, or access to, information on a device. Legitimate interests can be relevant for the later GDPR processing, but not for the device access itself.
What does Ireland's DPC say about analytics?
The DPC's guidance note on cookies and other tracking technologies (last updated April 2020) says plainly that analytics cookies require consent. It distinguishes first-party analytics, run by the website or on its behalf, from third-party analytics, where the provider may use data for its own purposes, which it considers a greater privacy risk. It also says it is unlikely that first-party analytics cookies would be a priority for DPC enforcement action.
The same guidance notes that the ePrivacy rule applies to device fingerprinting, so replacing cookies with fingerprinting does not avoid the consent requirement. Our guide to cookie consent rules in Ireland covers banner design and the DPC's expectations in detail.
Does "cookieless" automatically mean no consent is needed?
No. The European Data Protection Board's Guidelines 2/2023 on the technical scope of Article 5(3), adopted in final form on 7 October 2024, explain that the rule is not limited to cookies. They analyse use cases including URL and pixel tracking, local processing, tracking based on IP addresses only, and unique identifiers. The EDPB notes that new tracking methods are emerging to replace cookies, which is precisely why it clarified the scope.
In practice, ask what the tool's script does on the device. If it writes to local storage, reads device characteristics to build a fingerprint, or sets any persistent identifier, the consent question remains.
What is the CNIL's audience measurement exemption?
The CNIL, France's data protection authority, allows analytics without consent when the tool is configured within narrow limits. Its developer guidance lists the conditions:
- Inform users and give them the ability to object
- Limit the purpose to audience measurement and A/B testing
- Do not combine the data with other processing, such as customer files or visits to other sites
- Limit the tracker's scope to a single site or app publisher
- Truncate the last byte of the IP address
- Limit tracker lifetime to 13 months
The CNIL adds that most large audience measurement offerings do not fall within the exemption regardless of configuration, and suggests open-source tools such as Matomo that you can configure yourself. It also notes that its guidance relates to the ePrivacy Directive and may vary nationally, so check your own regulator's position. The DPC's guidance does not set out an equivalent exemption.
How do cookieless analytics tools work?
They count visits from data that every web request already carries, without storing anything on the device. Plausible's data policy is a published example: it creates a daily identifier by hashing a daily salt, the website domain, the IP address and the user agent; the salt is rotated and deleted every 24 hours, and raw IP addresses and user agents are not stored. Its script sets no cookies and writes nothing to local storage or the browser cache.
Matomo, the open-source tool the CNIL mentions, offers a cookieless configuration that disables its tracking cookies for all sites or specific sites.
How do the main analytics approaches compare?
The table summarises the trade-offs under EU rules.
| Approach | Stores data on device? | Consent likely needed in Ireland? | Detail available |
|---|---|---|---|
| Third-party analytics with cookies | Yes | Yes | High, including journeys and attribution |
| First-party analytics with cookies | Yes | Yes, though DPC enforcement priority is low | High |
| Fingerprinting-based "cookieless" tracking | Reads device data | Yes | High, but legally risky |
| Cookieless, no device storage, short-lived hashed counts | No | Possibly not for device access; GDPR still applies | Aggregate only |
| Server-side logs, aggregated | No | Depends on processing; GDPR applies | Basic |
This is a general comparison, not legal advice. The answer for your product depends on exactly what the script does and what data you keep.
What does cookieless analytics cost?
Self-hosted open-source tools cost hosting and maintenance time; hosted privacy-focused services charge subscriptions, usually tiered by traffic. The larger cost is lost detail: you may give up long-term user journeys, campaign attribution and individual-level product analytics. Many B2B products combine cookieless website analytics with in-product analytics for logged-in users, covered by their terms and privacy notice.
What pitfalls should you avoid?
- Trusting the label. "Cookieless" in marketing copy does not tell you what the script reads from the device. Ask the vendor or test it.
- Forgetting the GDPR. Even without device storage, processing IP addresses is processing personal data. Document your lawful basis and list the tool as a processor in your records, with an Article 28 contract.
- Mixing purposes. Using analytics data for advertising or combining it with CRM data removes any exemption argument.
- Applying French rules in Ireland. The CNIL exemption is a French regulator's position; the DPC guidance still says analytics cookies need consent.
For the wider set of launch obligations, see our GDPR checklist for a new SaaS product and the product launch checklist for B2B software.
Frequently asked questions
Is cookieless analytics GDPR compliant?
It can be, but compliance depends on configuration, not the label. If the tool processes personal data such as IP addresses, you need a lawful basis, transparency and a processor contract. Separately, if it stores or reads information on the device, the ePrivacy consent rule applies.
Do I need a cookie banner for cookieless analytics in Ireland?
If the tool stores nothing on and reads nothing from the user's device beyond what is strictly necessary, the ePrivacy consent requirement may not be triggered, though you must still explain the processing in your privacy notice. If it uses cookies, local storage or fingerprinting, the DPC's guidance says analytics require consent. Get advice on your specific setup.
Does Google Analytics qualify for the CNIL exemption?
The CNIL says most large audience measurement offerings do not fall within the exemption, regardless of their configuration. It suggests contacting your provider or using configurable open-source software such as Matomo. Check the CNIL's current position before relying on any tool.
Are IP addresses personal data?
They can be. Recital 30 of the GDPR lists IP addresses among the online identifiers that can be associated with individuals. Tools that truncate or hash IP addresses and avoid storing them reduce, but do not necessarily remove, GDPR obligations.
What is the difference between ePrivacy and GDPR for analytics?
ePrivacy rules govern access to the user's device, such as setting cookies or reading stored information, and generally require consent unless strictly necessary. The GDPR governs any processing of personal data and allows several lawful bases, including legitimate interests. Analytics often engages both.
Choosing an analytics setup for your product? Book a free 30-minute call to talk through the options.
Cover photo by https://kaboompics.com/ on Pexels.