Secure Privacy

Cookie Compliance Under GDPR and ePrivacy – Cookie Categories, Consent Requirements, and DPO Guidance

Cookie compliance requires satisfying both the ePrivacy Directive (when consent is needed) and GDPR (how consent must be obtained and recorded). This guide covers the four cookie categories, GDPR consent standards, common compliance pitfalls, and how your Secure Privacy DPO works alongside the Consent Management Platform to keep your cookie practices audit-ready.

SPT
Secure Privacy Team
6 min read ()

Cookie compliance sits at the intersection of the ePrivacy Directive and GDPR. While the ePrivacy Directive governs the requirement to obtain consent before placing non-essential cookies, GDPR sets the standard for what valid consent looks like — freely given, specific, informed, and unambiguous. Your Secure Privacy DPO ensures your organization's cookie practices satisfy both frameworks, working alongside the Secure Privacy Consent Management Platform (CMP) to keep your cookie banner, preference center, and consent records fully compliant.

Who Is This For?

  • Data Protection Officers and privacy managers responsible for cookie and consent compliance

  • Marketing and analytics teams using tracking technologies, advertising cookies, or third-party scripts

  • Web developers and IT teams implementing cookie banners, consent management platforms, and Google Consent Mode

  • Legal and compliance teams reviewing cookie policies and consent mechanisms for GDPR and ePrivacy compliance

How Cookies and GDPR Interact

The ePrivacy Directive requires prior informed consent before placing non-essential cookies on a user's device. GDPR Article 7 defines the standard that consent must meet to be legally valid — including requirements for freely given consent, granular choice per cookie category, equal prominence of accept and reject options, and the right to withdraw consent as easily as it was given. Organizations that fail to align their cookie consent practices with both frameworks face enforcement risk from supervisory authorities and, increasingly, from data subject complaints.

Cookies are classified into four categories based on their purpose. Consent requirements differ by category:

Category

Consent Required

Examples

Strictly Necessary

No

Session cookies, authentication, security cookies, load balancing

Functional

Yes

Language preferences, user settings, accessibility options

Analytics

Yes

Google Analytics, traffic measurement, A/B testing tools

Marketing

Yes

Advertising cookies, social media tracking pixels, retargeting scripts

Your DPO reviews regular cookie scan results to verify that all cookies deployed on your website are correctly identified, categorized, and declared — including third-party scripts loaded by analytics and marketing tools.

Your DPO advises on consent mechanisms to ensure they meet GDPR Article 7 requirements — including freely given consent, equal prominence of accept and reject options, granular category-level choice, and easy withdrawal.

Your DPO reviews cookie banner design and preference center configuration to ensure the implementation reflects best practice guidance from supervisory authorities and does not use dark patterns that nudge users toward acceptance.

Your DPO reviews your cookie policy to confirm it accurately reflects all cookies in use, provides clear descriptions of each cookie's purpose and retention period, and is updated whenever new cookies are added or existing ones change.

Your DPO advises on the correct implementation of Google Consent Mode V2 and IAB Transparency and Consent Framework (TCF) requirements — ensuring your CMP integration signals consent correctly to advertising and analytics partners.

Regulatory guidance monitoring

Your DPO tracks emerging cookie enforcement decisions, supervisory authority guidance, and ePrivacy Regulation developments — updating your consent framework proactively as the regulatory landscape evolves.

Your DPO works directly alongside the Secure Privacy Consent Management Platform to ensure end-to-end cookie compliance:

  1. Regular cookie scanning: Automated scans identify new and changed cookies before they create compliance gaps in your consent records.

  2. Consent record maintenance: All consent events are logged and stored in line with GDPR accountability requirements — providing an auditable record for regulatory inspection.

  3. Opt-out mechanism verification: Your DPO verifies that reject and withdraw consent functions operate correctly across all cookie categories and do not require additional steps beyond accepting.

  4. Cross-domain consent management: Where your organization operates multiple domains, your DPO ensures cross-domain consent is correctly implemented and recognized across all properties.

  5. Change management: When new cookies or tracking technologies are introduced, your DPO ensures consent requirements are reviewed and updated before deployment.

Pre-ticked checkboxes do not constitute valid consent under GDPR Article 7 or the ePrivacy Directive. Consent must be an active, affirmative action — silence or pre-selection is explicitly excluded.

Requiring users to accept all cookies as a condition of accessing content is problematic under most supervisory authority guidance, as it prevents consent from being freely given. Your DPO advises on compliant alternatives.

Classifying analytics or marketing cookies as "strictly necessary" to avoid requiring consent is a frequently cited enforcement finding. Your DPO reviews all cookie classifications to ensure they reflect the cookie's actual function.

Cookie policies must accurately reflect all cookies currently deployed. When new tools, scripts, or third-party integrations are added, cookie policies and consent banners must be updated before the new cookies are placed.

Cookie declarations must include the name, provider, purpose, and retention period for each cookie. Incomplete or generic descriptions — such as listing only cookie categories without naming individual cookies — do not satisfy transparency requirements under GDPR and the ePrivacy Directive.

Frequently Asked Questions

Does GDPR apply to cookies directly?

GDPR does not regulate cookies directly — that is the role of the ePrivacy Directive. However, GDPR sets the standard for what constitutes valid consent, which applies to cookie consent under the ePrivacy Directive. Organizations must satisfy both frameworks: ePrivacy for when consent is required, and GDPR for how that consent must be obtained and recorded.

Are analytics cookies strictly necessary?

No. Analytics cookies — including Google Analytics — are not strictly necessary for the website to function and require prior consent under the ePrivacy Directive. Supervisory authorities across the EU have consistently confirmed this position in enforcement decisions against organizations treating analytics cookies as exempt from consent requirements.

Google Consent Mode V2 is Google's framework for adjusting how Google tags behave based on users' consent choices. It is required for organizations using Google Ads, Google Analytics 4, or other Google services that rely on consent signals — particularly for retaining access to modeled conversion data and audience features. Your DPO advises on correct CMP integration to ensure consent signals are passed accurately to Google's services.

Cookie scans should be conducted regularly — at minimum quarterly — and triggered automatically whenever significant website changes are made, new third-party scripts are added, or CMS or tag manager configurations change. Your DPO reviews scan results and advises on any reclassification or policy updates required.

See Also

Need more help?

Our privacy experts are here to guide you through complex regulations and find the right solution.

Contact Support

Related Articles

View all