The rule
Article 5(3) of the ePrivacy Directive requires consent before storing or reading anything on a user's device that is not strictly necessary for the service they asked for: analytics, advertising and most third-party trackers. The consent has to meet the GDPR standard (Art 4(11) and 7): freely given, specific, informed and unambiguous, and you must be able to prove it.
What regulators check
- Cookies set before consent: the most common and most serious issue.
- No reject option on the first layer: refusing should be as easy as accepting.
- Pre-ticked boxes: silence or pre-selection is not consent.
- Cookie walls: making access depend on accepting cookies; the EDPB's consent guidelines say this is generally not freely given consent.
- Undisclosed trackers: third-party tags that are not named in the banner or policy.
- No granular choice, and no records of consent.
Fines regulators have issued
France's CNIL has been the most active enforcer: EUR 35 million against Amazon Europe Core (December 2020) and EUR 60 million against Facebook Ireland, among others, for cookie practices. Cookie rules are enforced under each country's national ePrivacy law, so who enforces them and the maximum fine depend on the country.
The calculator above weights the issues you tick, scales by supervisory risk and EU audience, and lists the fixes heaviest first. The ranges are our estimates, not a prediction of any regulator's decision.
See which privacy laws reach your business with the privacy law checker, and read about GDPR security requirements.
Sources
- ePrivacy Directive 2002/58/EC, Art 5(3) (EUR-Lex); GDPR (EUR-Lex)
- EDPB Guidelines 05/2020 on consent
- CNIL SAN-2020-013, Amazon Europe Core; CNIL SAN-2021-024, Facebook Ireland
Facts checked against the sources above on 22 October 2026. General information, not legal advice.
