Comparison GuideEU

EU ePrivacy Directive vs UK PECR

The EU Directive and UK PECR share the same legislative ancestry, but they are separate legal regimes. Check the destination jurisdiction before approving cookies, similar technologies, or direct marketing.

The comparison uses the EU Directive and EDPB guidance alongside the latest revised PECR text and ICO guidance on cookies and direct marketing.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 25, 2026
Sections
3

Structured answer sets in this page tree.

Primary sources
11

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 25, 2026
Overview

For an EU user, start with the Member State law that transposes the ePrivacy Directive. For a UK user, apply the Privacy and Electronic Communications (EC Directive) Regulations 2003 () in their latest revised form. Both regulate storage or access on terminal equipment and electronic marketing, but UK amendments now include PECR-specific statutory exceptions and a charitable-purpose soft opt-in that do not appear in the Directive's text. Do not copy an EU conclusion into a UK file, or a UK exception into an EU launch.

Side-by-side comparison

EU ePrivacy Directive vs UK PECR

Compare the EU framework with current UK statutory rules, then record the jurisdiction-specific source and conclusion for each operation.

Review all sources
First framework
EU ePrivacy Directive

Based on the supplied EU ePrivacy sources for Article 5(3), direct marketing, consent, soft opt-in logic, and GDPR/ePrivacy interplay.

Second framework
UK PECR

UK statutory rules for terminal-equipment storage or access, electronic communications and marketing, read with UK data-protection law and ICO guidance.

Comparison row 1

Scope boundary

EU ePrivacy Directive

Article 5(3) covers storing information or gaining access to information already stored in a subscriber's or user's terminal equipment; EDPB guidance frames the test around information, terminal equipment, storage, and access, and it is not limited to ordinary cookies.

UK PECR

regulation 6 and Schedule A1 govern storing information in, or gaining access to information stored in, a subscriber's or user's terminal equipment. The rule covers browser cookies and other technologies that perform the same storage or access operations.

Operational implication

Use one technical inventory, then make separate EU and UK decisions. The same storage or access can be in both regimes' scope, but the available exceptions are not identical.

Comparison row 2

Storage and access exceptions

EU ePrivacy Directive

EU cookie consent exemptions are narrow: the cookie must be solely for transmitting a communication, or strictly necessary for a specific information-society service explicitly requested by the user.

UK PECR

Schedule A1 includes consent, transmission, and strictly necessary routes, plus conditional exceptions for statistical collection, website appearance or functionality purposes, and emergency assistance.

Operational implication

For each UK exception, test every Schedule A1 condition. Do not treat a exception as an EU Article 5(3) exception or rely on a broad label such as analytics or preferences.

Comparison row 3

Trigger

EU ePrivacy Directive

Article 13 requires prior consent for electronic mail direct marketing, subject to the customer-contact rule for the sender's own similar products or services with a clear, easy, free opportunity to object at collection and in every later message.

UK PECR

regulation 22 generally requires consent for electronic-mail marketing to individual subscribers unless a statutory soft opt-in applies. Corporate subscribers follow a different PECR route, although UK GDPR still applies when the address or other campaign data is personal data.

Operational implication

Classify the subscriber before choosing the route. Keep the contact source, consent or soft-opt-in facts, sender identity, unsubscribe path, and suppression result.

Comparison row 4

Core obligations

EU ePrivacy Directive

EU consent evidence should show real choice, clear information, an affirmative action, ability to demonstrate consent, and withdrawal without detriment; scrolling or similar passive activity is not enough for unambiguous consent.

UK PECR

Where requires consent, use the UK data-protection definition and standards for consent. For electronic-mail marketing, the ICO requires consent to be specific to the type of message and sender; a soft opt-in is a conditional exception, not consent.

Operational implication

Consent logs should capture the notice version, purposes, sender, channel, positive action, timestamp, and withdrawal. Soft-opt-in records should capture every condition instead of recording consent that was never given.

Comparison row 5

Evidence record

EU ePrivacy Directive

EU evidence can be reused across cookie, analytics, consent, and marketing reviews only when each record says which Article 5(3), Article 13, consent, or GDPR/ePrivacy interplay point it supports.

UK PECR

evidence should identify regulation 6 or 22, the Schedule A1 or soft-opt-in branch used, subscriber type where relevant, information shown, consent or objection state, and any linked UK GDPR processing.

Operational implication

A shared evidence pack is useful only if each conclusion names the jurisdiction, rule, exception, owner, and unresolved facts.

Comparison row 6

Timing and deadlines

EU ePrivacy Directive

EDPB Opinion 5/2019 explains that Articles 5(3) and 13 can apply to website operators and other businesses, and that ePrivacy-specific rules can coexist with GDPR where personal data is involved.

UK PECR

Apply before non-essential storage or access begins and before sending consent-dependent electronic mail. Give the product-and-services or charitable soft-opt-in opt-out at collection and in every later message.

Operational implication

A DPIA, lawful-basis record, or privacy notice does not replace the pre-use decision, the collection-stage opt-out, or the message-level unsubscribe.

Comparison row 7

Enforcement

EU ePrivacy Directive

The Directive requires Member States to establish sanctions and designate authorities through national law, so the competent authority and penalty route depend on the transposition.

UK PECR

regulation 31 applies the Information Commissioner's enforcement powers through the UK statutory scheme. Use the current PECR text and ICO material for a concrete UK enforcement question.

Operational implication

Do not quote an EU-wide ePrivacy penalty or assume the same authority handles both jurisdictions. Record the national EU source and the UK source separately.

Comparison row 8

Overlap and reuse

EU ePrivacy Directive

The EU and UK analyses can reuse technical and campaign facts, but the EU conclusion must cite the relevant Member State transposition when a country-specific answer is needed.

UK PECR

The conclusion can reuse the same inventory, banner, consent log, sale record, and suppression list, but it must identify the UK rule, subscriber type, and any Schedule A1 or soft-opt-in conditions.

Operational implication

Reuse evidence, not legal conclusions. A UK statistical or charitable exception does not establish an EU exemption.

Comparison row 9

Practical decision rule

EU ePrivacy Directive

For an EU operation, identify the exact storage, access, or marketing act, then apply the relevant Member State law that transposes Article 5(3) or Article 13.

UK PECR

For a UK operation, apply regulation 6 and Schedule A1 to storage or access, or the relevant marketing regulation and subscriber category to the campaign. Apply UK GDPR separately where personal data is processed.

Operational implication

Approve each jurisdiction only after its own rule and exception conditions are documented. A single global banner or campaign setting may need different legal configurations.

Practical decision rule

How should teams make the EU and UK decisions?

  • Identify the user and campaign jurisdictions before choosing a rule.
  • For the EU, apply the relevant Member State transposition to the specific Article 5(3) or Article 13 operation.
  • For the UK, apply regulation 6 and Schedule A1 to storage or access, and classify the marketing channel and subscriber before using consent or a soft opt-in.
  • Do not import the statistical, website appearance or functionality, emergency-assistance, or charitable-purpose branches into an EU conclusion.
  • Apply GDPR or UK GDPR separately whenever the operation processes personal data.
Section 1

Choose the governing jurisdiction first

The ePrivacy Directive requires Member States to transpose its rules, so the operative EU requirement comes from the relevant national law. is the UK's own statutory instrument and is read with UK data-protection law and ICO guidance.

A service can need both workstreams when it serves people in the EU and UK. Keep separate legal conclusions even when the same tracker inventory, consent interface, customer record, or suppression list supplies the underlying facts.

  • Record the user's location, the service and sender entities, the applicable EU Member State transposition, and whether applies to the UK activity.
  • Inventory cookies and similar technologies by purpose, party, duration, information stored or read, and the service function the user requested.
  • Inventory marketing by channel, subscriber type, source of contact details, sale or support context, product similarity, consent, objection, and suppression status.
  • Keep EU and UK authority, enforcement, and penalty conclusions separate.
Section 2

Compare the device-storage rules carefully

EU Article 5(3) requires clear information and consent for storage or access on terminal equipment unless the operation is solely for transmitting a communication or strictly necessary for an information-society service explicitly requested by the user. EDPB guidance applies the technical test beyond browser cookies to pixels, local processing, identifiers, and connected devices.

Current regulation 6 and Schedule A1 retain consent, transmission, and strictly necessary routes, and also contain UK statutory exceptions for qualifying statistical collection, certain website appearance or functionality purposes, and emergency assistance. Each exception has conditions in Schedule A1; its title alone is not enough.

  • Do not import a Schedule A1 exception into an EU Article 5(3) decision. Check the relevant Member State law for any national rule or regulator position.
  • For statistical collection, verify the statutory safeguards, purpose limits, information duties, and opt-out requirements in the current Schedule A1 text.
  • For a website appearance or functionality purpose, record whether the storage or access adapts the service to the user's preferences or enhances its appearance or functionality, and verify the information and opt-out conditions.
  • Where personal data is involved, complete a separate GDPR or UK GDPR analysis after the ePrivacy or storage-access decision.
Section 3

Direct marketing has shared concepts and UK-specific branches

EU Article 13 requires prior consent for automated calls, fax, and electronic mail direct marketing, subject to the customer-contact exception for the sender's own similar products or services and a free, easy objection at collection and in each message. Member States retain choices for some other communications and must protect legal persons' legitimate interests.

regulation 22 distinguishes individual subscribers from corporate subscribers for electronic-mail marketing. The ICO explains the product-and-services soft opt-in as a five-condition exception for contact details obtained directly during a sale or sale negotiation, the sender's similar products or services, and opt-out opportunities at collection and in every message. Current UK law and ICO guidance also include a separate charitable-purposes soft opt-in with its own eligibility and six conditions. That exception commenced on 5 February 2026 and can apply only when the charity obtained the recipient's contact details on or after that date.

  • Identify the recipient as an individual or corporate subscriber for ; a named business email can still be personal data even where PECR's corporate-subscriber rule differs.
  • For the product-and-services soft opt-in, keep evidence for all five conditions. A purchased list, a contact obtained from another group company, or unrelated third-party marketing does not satisfy the ICO's stated route.
  • Only a qualifying charity can use the charitable-purposes soft opt-in, and only for its own charitable purposes when every statutory condition is met.
  • For EU campaigns, check the recipient country's Article 13 transposition rather than copying 's subscriber categories or charitable exception.
Primary sources

References and citations

digital-strategy.ec.europa.eu
Referenced sections
  • Grounds the Commission explanation that ePrivacy protects communications and device confidentiality alongside GDPR.
"electronic communications and the device"
Related guides

Explore more topics

Are cookie walls allowed under the EU ePrivacy Directive?
FAQ answer on cookie walls under the EU ePrivacy Directive, covering freely given consent, refusal and withdrawal paths, banner evidence, and national-law caveats.
Do Analytics Cookies Require Consent under the EU ePrivacy Directive?
FAQ answer on analytics cookies under Article 5(3) ePrivacy, limited analytics exemptions, configuration evidence, consent logs, and national-law caveats.
ePrivacy cookie consent vs DSA advertising rules
Compare ePrivacy rules for device storage and access with DSA ad labels, advertiser disclosures, targeting information, profiling limits, and VLOP/VLOSE ad repositories.
ePrivacy Directive vs GDPR: cookies, communications, consent, and evidence
Compare the EU ePrivacy Directive and GDPR across subject matter, lex specialis overlap, terminal equipment, communications confidentiality, marketing, consent, enforcement, and evidence.
EU cookie banner requirements under the ePrivacy Directive
EU ePrivacy cookie banner requirements for non-exempt cookies and trackers: prior consent, reject choices, no pre-ticked boxes, withdrawal, analytics limits, cookie walls, and evidence logs.
EU ePrivacy analytics cookies: consent, exemption, and evidence guide
Source-backed guide to analytics cookies under EU ePrivacy: Article 5(3) scope, when consent is usually needed, limited analytics exemptions, consent records, and evidence gaps.
EU ePrivacy Applicability Test for Cookies, SDKs, Pixels, Communications, and Marketing
A concrete EU ePrivacy Directive applicability test for electronic communications services, terminal-equipment storage or access, cookies, SDKs, pixels, local storage, direct marketing, GDPR overlap, and evidence.
EU ePrivacy Article 5(3) terminal equipment test
A cited Article 5(3) test for cookies, pixels, local identifiers, device APIs, strictly necessary exceptions, and consent evidence.
EU ePrivacy Confidentiality of Communications: Article 5 controls
Article 5 confidentiality guide for EU ePrivacy communications, traffic data, metadata, terminal-equipment access, consent limits, and GDPR interplay.
EU ePrivacy consent-log evidence workflow for cookies and trackers
Build evidence that links each cookie or tracker decision to the banner shown, the user's signal, the live technical behavior, withdrawal, and later changes.
EU ePrivacy cookie banner UX test cases
Source-backed cookie banner UX tests for Article 5(3) ePrivacy consent: reject all, pre-ticked boxes, withdrawal, cookie walls, analytics toggles, and consent evidence.
EU ePrivacy Cookie Scope Classifier Workflow
Decide whether cookies, pixels, SDKs, local storage, identifiers, and analytics fall within Article 5(3), then document consent, an exemption, or escalation.
EU ePrivacy direct-marketing consent checklist
Checklist for ePrivacy Directive direct-marketing messages: consent, soft opt-in, sender identity, opt-out handling, proof records, suppression, and national-law caveats.
EU ePrivacy Directive compliance calendar for cookies, consent, and marketing
Source-backed ePrivacy calendar covering Directive milestones, Article 5(3) cookie reviews, consent evidence, direct marketing checks, and national-law follow-up.
EU ePrivacy Directive Compliance Checklist
A concrete ePrivacy checklist for terminal equipment access, cookie consent, exemptions, banner UX, direct marketing, confidentiality, GDPR interplay, and evidence records.
EU ePrivacy Directive Compliance Guide for Cookies, Marketing, and Communications
Practical ePrivacy Directive compliance checks for terminal equipment, communications confidentiality, cookie consent, exemptions, direct marketing, evidence, and national-law caveats.
EU ePrivacy Directive Cookies and Consent: Article 5(3), exemptions, and banner evidence
Cookie consent guide for the EU ePrivacy Directive: Article 5(3) scope, strictly necessary and transmission exemptions, consent UX, withdrawal, logs, analytics caveats, and GDPR interplay.
EU ePrivacy Directive direct marketing rules for electronic mail
Source-backed guide to Article 13 ePrivacy Directive rules for electronic mail marketing, prior consent, customer soft opt-in, opt-out handling, sender identity, and Member State caveats.
EU ePrivacy Directive Enforcement and Fines
Source-backed guide to ePrivacy Directive enforcement, national penalties, competent authorities, GDPR interplay, cookie-banner risk, and evidence limits.
EU ePrivacy Directive FAQ: cookies, consent, marketing, GDPR interplay
Answers to recurring EU ePrivacy Directive questions on Article 5(3), terminal-equipment access, cookie consent, exemptions, analytics, direct marketing, GDPR interplay, national enforcement, and evidence.
EU ePrivacy Directive Member State Cookie Rules
How to evidence EU ePrivacy cookie compliance when Article 5(3) is implemented through Member State law and national authority practice.
EU ePrivacy Directive Metadata and Location Data Guide
Source-backed guide to EU ePrivacy Directive rules for traffic data, location data, anonymisation, consent, value-added services, Article 5(3) overlap, and national-law limits.
EU ePrivacy Directive penalties and fines: national enforcement caveats
Source-backed guide to ePrivacy Directive penalty exposure, national transposition caveats, cookie enforcement evidence, consent defects, and GDPR overlap limits.
EU ePrivacy Directive Requirements: cookies, communications and marketing
Source-backed map of EU ePrivacy Directive requirements for communications confidentiality, terminal-equipment access, consent, traffic and location data, and direct marketing.
EU ePrivacy Directive vs GDPR: cookies, communications, marketing, and evidence
Compare the EU ePrivacy Directive and GDPR by trigger, consent standard, lex specialis overlap, enforcement caveats, and evidence outputs for cookies, device access, communications, and marketing.
EU ePrivacy soft opt-in FAQ for email marketing
When Article 13(2) soft opt-in can support EU customer email marketing, including existing-customer, similar-offer, opt-out, sender-identity, suppression-list, and national-law checks.
EU ePrivacy soft opt-in marketing checklist
Source-backed checklist for using the EU ePrivacy Directive soft opt-in exception for customer email marketing, opt-outs, sender identity, suppression records, and national-law caveats.
EU ePrivacy soft opt-in marketing review workflow
Decide whether an electronic-mail marketing audience meets every Article 13 soft opt-in condition, or must be suppressed or supported by valid prior consent.
EU ePrivacy Strictly Necessary Cookie Exemptions
Source-backed guide to the Article 5(3) ePrivacy exemptions for transmission cookies, requested-service cookies, analytics caveats, evidence, and national-law checks.
Is a reject-all button required for EU ePrivacy cookie consent?
Standalone FAQ answer on EU ePrivacy reject-all and refuse options for cookie banners, including equal prominence, deceptive UX, consent evidence, withdrawal, and national-law caveats.
Strictly Necessary Cookies under the EU ePrivacy Directive
FAQ answer on when EU ePrivacy Article 5(3) allows cookies without consent, with cited examples, analytics caveats, evidence records, and national-law cautions.
What should CMP consent logs retain under the EU ePrivacy Directive?
FAQ answer on CMP consent logs for EU ePrivacy cookie consent: retained fields, consent validity signals, banner versioning, refusal and withdrawal events, proof limits, and national-law caveats.