FAQEU ePrivacy

Can EU email marketing use soft opt-in?

Article 13(2) can support customer email marketing only when the contact details came from a sale, the sender is the same legal or natural person, the offer is for that sender's own similar products or services, and the customer had a free, easy opt-out at collection and in every message.

Use this campaign gate for privacy, lifecycle marketing, CRM operations, and legal review before relying on soft opt-in instead of consent.

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

Structured answer sets in this page tree.

Primary sources
5

Cited legal and guidance references.

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

EU ePrivacy is not a general permission to email prospects. It is a narrow Article 13(2) route for reusing electronic mail contact details collected from a customer during a product or service sale, subject to same-sender, similar-offer, clear opt-out, sender-identity, and national transposition checks.

Search this module

Find a question or answer quickly

3 of 3 questions
Question 1

When does the ePrivacy soft opt-in apply?

Treat as available only when every Article 13(2) condition is documented before launch. The sender must have obtained the customer's electronic contact details in the context of selling a product or service. The same natural or legal person must send the campaign for its own similar products or services. Article 13(2) does not itself extend the route to prospects, bought or shared lists, affiliates, another group company, third-party offers, or unrelated products.

The customer also needs a clear and distinct chance to object, free of charge and in an easy manner, when the details are collected and in every later message if the customer did not initially refuse. Each message must disclose a valid address for stopping further communications and must not disguise or conceal the sender. If the sale record, collection screen, CRM record, similarity assessment, sender identity, or message template cannot prove those facts, do not rely on Article 13(2).

  • Confirm the contact is an existing customer from a sale, not a bought-in lead, scraped address, event badge scan, newsletter-only signup, trial with no documented sale context, or abandoned form.
  • Confirm the sending entity is the same legal or natural person that collected the electronic mail details.
  • Map the promoted offer to the product or service originally sold and explain why it is similar.
  • Show the opt-out text or control used at collection and the unsubscribe or objection route in each message.
  • Block the send where the customer has objected, unsubscribed, or appears on a suppression list.

Can EU email marketing rely on under the ePrivacy Directive?

Yes, but only for a narrow existing-customer use case. Article 13(2) allows the same sender that obtained a customer's electronic mail contact details during a sale to use those details for direct marketing of its own similar products or services, provided the customer was clearly and distinctly offered a free, easy objection at collection and in every message. If the list is prospect data, a different sender is involved, the offer is not similar, the opt-out is missing, or the customer already objected, do not rely on .

Citations
Question 2

What campaign evidence should teams keep?

Keep evidence that proves the exact path, not a generic marketing approval. The record should connect the customer record, sale context, sender identity, product-similarity assessment, opt-out presentation, message template, and suppression-list enforcement.

Suppression evidence matters because Article 13(2) depends on the customer not having initially refused and on the customer receiving a continuing objection opportunity. A working suppression list should record collection-stage refusals, later unsubscribe requests, bounced or invalid stop addresses, and downstream systems where the block must be honored before the next send.

  • Customer-source evidence: order, subscription, or service record showing the email address was obtained in the context of a sale.
  • Sender evidence: legal-entity name, brand presentation, reply domain, and sender authentication that match the entity relying on Article 13(2).
  • Similarity evidence: short mapping from the purchased product or service to the promoted offer.
  • Collection opt-out evidence: checkout, account, or order-flow copy showing the clear and distinct objection opportunity.
  • Each-message opt-out evidence: final email template with unsubscribe link, preference-center path, or valid reply address.
  • Suppression evidence: timestamped objection records and pre-send exclusion checks across CRM, ESP, CDP, and regional campaign tools.
Citations
EDPB Guidelines 05/2020 on consent

The consent guidance supports fallback analysis where a campaign does not fit the Article 13(2) soft opt-in route and needs valid opt-in consent.

Question 3

When should teams escalate instead of sending?

Escalate when any condition depends on interpretation: whether a free trial is a sale, whether a service renewal is similar enough to a new product, whether a group affiliate is the same sender, whether the collection notice was clear, or whether national law adds stricter rules for a channel, recipient type, or local implementation.

The ePrivacy Directive is implemented through national law. Article 13(3) leaves Member States a choice for other direct-marketing cases, and Article 13(5) requires protection for subscribers that are not natural persons under Union and applicable national law. The Commission's 2017 proposal for a directly applicable ePrivacy Regulation was withdrawn in 2025, so it does not replace those national variations. Do not add country-specific rules, penalties, or exemptions unless they are separately sourced for the relevant country.

  • Use consent review for prospects, purchased lists, partner lists, affiliate sends, group-company sends, or unrelated offers.
  • Escalate where the message disguises or conceals the sender identity, uses a misleading sender name, or lacks a valid address or route for stopping further messages.
  • Check local implementation before relying on for B2B recipients, legal-person subscribers, mixed channels, SMS, automated calls, or voice calls.
  • Recheck the GDPR layer for any personal-data processing that sits outside the ePrivacy special rule, such as profiling, segmentation, analytics, or enrichment.
Citations
Directive 2002/58/EC, Article 13

Article 13(3), 13(4), and 13(5) ground the escalation points for national-law choices, sender identity, valid stop addresses, and legal-person protections.

Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • Article 13(3), 13(4), and 13(5) ground the escalation points for national-law choices, sender identity, valid stop addresses, and legal-person protections.
"the choice between these options to be determined by national legislation"
edpb.europa.eu
Referenced sections
  • The consent guidance supports fallback analysis where a campaign does not fit the Article 13(2) soft opt-in route and needs valid opt-in consent.
"freely given, specific, informed and unambiguous"
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 Directive vs UK PECR: cookies and direct marketing
Compare the EU ePrivacy Directive with current UK PECR rules for device storage and access, statutory exceptions, consent, electronic-mail marketing, soft opt-ins, and enforcement.
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.