Key Facts
Overview
The ePrivacy Directive is the EU's cookie-specific law, providing the direct legal basis for requiring consent before placing cookies and similar tracking technologies on users' devices. While the GDPR defines what valid consent looks like, Article 5(3) of the ePrivacy Directive is what actually requires that consent for cookies.
What This Means for Your Website
- You need prior consent before storing or accessing any information on a visitor's device — this includes cookies, local storage, tracking pixels, and device fingerprinting
- Only two narrow exceptions exist: cookies strictly necessary for network transmission, and cookies strictly necessary for a service the user explicitly requested
- Analytics cookies are NOT exempt — they require consent under the ePrivacy Directive
- Each EU member state has transposed the Directive differently, so specific rules vary by country
- Consent must meet GDPR standards: freely given, specific, informed, and unambiguous
Key Requirements
The Directive covers all forms of information storage and access on terminal equipment, not just HTTP cookies. The EDPB has confirmed that tracking pixels, URL tracking parameters, JavaScript processing, and device fingerprinting all fall under Article 5(3). Each member state enforces penalties independently — there is no harmonized penalty structure. The proposed ePrivacy Regulation that would have replaced this Directive was formally withdrawn in July 2025.
How ConsentStack Handles This
ConsentStack blocks all non-essential cookies and tracking technologies by default for EU/EEA visitors, satisfying Article 5(3) requirements. The platform handles the varying national implementations automatically, applying the strictest applicable standard for each visitor's location.
Penalties
Not harmonized; each member state sets own penalties (must be effective, proportionate, and dissuasive)
Key Requirements
- Prior informed consent before placing any non-essential cookie or tracking technology
- Only two exceptions: transmission necessity and explicitly requested service
- Clear and comprehensive information required before consent
- Consent must meet GDPR standards since May 2018
- Covers all terminal equipment including browsers, mobile devices, IoT, and smart TVs
Notable Provisions
- Proposed ePrivacy Regulation was formally withdrawn July 2025
- EDPB confirmed tracking pixels, URL tracking, and device fingerprinting fall under Art. 5(3)
- Must be transposed into national law, creating implementation differences across member states
Related Regulations (30)
Other Europe Regulations
Frequently Asked Questions
What is the ePrivacy Directive?
The ePrivacy Directive (Directive 2002/58/EC) is the EU law that specifically requires consent before placing cookies and tracking technologies on users' devices. It works alongside the GDPR, which defines the consent standard.
Does the ePrivacy Directive only cover cookies?
No. Article 5(3) covers any storage or access of information on terminal equipment, including local storage, tracking pixels, device fingerprinting, and URL tracking parameters.
Is the ePrivacy Directive being replaced?
The proposed ePrivacy Regulation was formally withdrawn in July 2025. The existing Directive remains in force, with limited amendments expected through the Digital Omnibus package.
Are analytics cookies exempt under the ePrivacy Directive?
No. Analytics cookies require consent under Article 5(3). Some national implementations like France offer narrow exemptions for privacy-friendly analytics, but the Directive itself does not exempt analytics.
Stay compliant with ePrivacy Directive
ConsentStack helps you implement Opt-in consent for European Union + EEA automatically.