The General Data Protection Regulation is the anchor of European privacy law and the default legal framework for every marketing sender reaching an EU recipient. It requires a documented legal basis for every processing activity, extends to any organization worldwide that handles EU personal data, and lets supervisory authorities impose fines up to €20 million or 4% of global annual turnover, whichever is higher. This guide focuses on what GDPR and the ePrivacy rules mean for email marketing: which legal basis to use, when cold B2B email is allowed country by country, how to prove consent, and how unsubscribes must work.
General Data Protection Regulation (GDPR) · Regulation (EU) 2016/679 · In force since 25 May 2018 · Enforced by 30 national supervisory authorities across the EU/EEA (CNIL France, AEPD Spain, Garante Italy, BfDI Germany, DPC Ireland, DSB Austria, DPA Netherlands, plus 23 others), coordinated by the European Data Protection Board (EDPB) · Applies to any organization processing personal data of EU residents, regardless of the organization’s location · Max fine: €20M or 4% of global annual turnover, whichever is higher (Article 83).
Legal basis for email marketing
Under Article 6, every processing activity, including sending a commercial email, must rest on one of six legal bases. For email marketing to consumers, only two are practical:
Can you send cold B2B email under GDPR? Country rules
GDPR decides how you may process a contact’s data. Whether you may send them an unsolicited marketing email is decided by the national law implementing Article 13 of the ePrivacy Directive. That is why the same B2B campaign can be legal in Paris or London and unlawful in Berlin. The table below covers three of the largest markets, based on the regulators’ own guidance.
| Country | Cold email to consumers | Cold email to businesses (B2B) | Existing customers |
|---|---|---|---|
| France (CNIL) | Prior consent required (unticked box, positive action) | Allowed without prior consent if the offer relates to the recipient’s job, the person was informed and can object easily, and each message identifies the sender | Allowed for similar products or services; creating an account without any purchase does not qualify |
| Germany (UWG § 7) | Prior express consent required | Prior express consent required: the email rule does not distinguish consumers from businesses | Allowed only if all four § 7(3) conditions are met: address obtained in a sale, own similar products, no objection, opt-out notice at collection and in every email |
| United Kingdom (ICO, PECR) | Specific consent required | Allowed to corporate subscribers (companies, LLPs, public bodies); sole traders and some partnerships count as individuals and need consent | Soft opt-in for customers who bought or negotiated to buy, with an opt-out at collection and in every message |
Where B2B prospecting is allowed, GDPR still applies to the data. A named work address such as firstname.lastname@company.com is personal data. You still need a legitimate interest assessment, a privacy notice that reaches the person (Article 14 when the address did not come from them), and an opt-out that works on the first click.
Proof of consent and unsubscribe setup
- Log every opt-in: timestamp, IP or source, the form URL, and the exact wording shown. Article 7(1) puts the burden of proof on you.
- Use double opt-in where you can. GDPR does not mandate it, but a confirmation click is the simplest proof that the address owner really subscribed.
- Make withdrawal as easy as signup (Article 7(3)): one visible unsubscribe link plus a List-Unsubscribe header for one-click removal in Gmail and Yahoo.
- Set up the link correctly in your platform: see the Mailchimp, Brevo, HubSpot and Klaviyo guides, or the unsubscribe merge tag reference for other tools.
What to store as proof of consent
Article 7(1) puts the burden of proof on the sender. In practice, regulators ask for the record of one specific subscriber, so each consent must be traceable on its own, not just “we use a compliant form”. This is the minimum record we recommend keeping for every address:
| Field | Example | Why it matters |
|---|---|---|
| Email address | jane@example.com | The identifier the regulator or the complainant will give you |
| Date and time (UTC) | 2026-11-04 18:10:53 | Shows consent existed before the first marketing email |
| Source | Form ID and page URL | Lets you show the exact form the person saw |
| Wording shown | Versioned text of the checkbox and notice | Consent must be specific and informed: the words are the evidence |
| Lists or purposes | Newsletter, Deals | Consent to one list is not consent to another |
| Confirmation | Double opt-in click, date and time | Proves the mailbox owner, not a third party, subscribed |
| IP address | Signup and confirmation IP | Helps separate real signups from bot or list-bombing traffic |
| Withdrawal | Unsubscribe date and channel | Proves you stopped, and that you stopped on time |
Consent wording that holds up, and wording that does not
☐ “Send me the weekly Acme newsletter with product news and offers. I can unsubscribe at any time from any email.”
☐ “Yes, email me deals and discount codes from Acme. This is separate from my order confirmation emails.”
☑ Pre-ticked “Keep me updated” box: no positive action, ruled invalid in the CJEU Planet49 case.
☐ “I confirm I am over 18 and agree to receive marketing”: bundled with another statement. The ICO cited this kind of bundling in its HelloFresh fine (see below).
A double opt-in flow that actually confirms
Double opt-in only works as proof if the confirmation email arrives. On smtpedia.com we saw it fail in practice: confirmation emails went to spam because the sending service was not signing with our domain (DKIM) under a strict DMARC policy, so new subscribers stayed “unconfirmed” without ever seeing the email. The checklist we now use:
- Authenticate the sending domain with the provider that sends the confirmation (SPF, and above all DKIM aligned with your From domain), then check the Authentication-Results header of a real confirmation email shows
dkim=passanddmarc=pass. - Keep the confirmation email plain: one button, the same link in clear text, a line saying what to do if the person did not sign up. No images, no tracking on the confirmation link.
- Tell people where to look: the success message after the form should ask them to check their inbox and spam folder, not say “you are subscribed”.
- Store the confirmation click with its date and time next to the signup record.
- Do not mail unconfirmed addresses. Remove them after a fixed delay (for example 30 days) instead of sending them marketing.
Data subject rights that touch marketing
- Right of access (Article 15). A subject can request all personal data you hold on them within one month.
- Right to erasure (Article 17). Also known as the “right to be forgotten”, deletion within one month unless a legal ground overrides.
- Right to object to direct marketing (Article 21). Unconditional. As soon as a subject objects, sending must stop for direct marketing purposes.
- Right to data portability (Article 20). Structured, commonly-used, machine-readable format.
- Right to withdraw consent (Article 7(3)). Consent must be as easy to withdraw as it was to grant, a one-click unsubscribe link satisfies this for email marketing lists built on consent.
Who must comply
GDPR applies extraterritorially. Article 3 pulls in any organization outside the EU that offers goods or services to EU residents (paid or free) or monitors their behavior. A US SaaS with EU signups, a UK newsletter with continental subscribers post-Brexit, and an Asian retailer accepting EU shipping addresses all fall in scope. The location of your servers is irrelevant; the location of your data subjects controls.
Data controllers (who decide why and how personal data is processed) and data processors (who process on the controller’s behalf, like an ESP) share responsibility. Article 28 requires a written data processing agreement between them setting out the processor’s obligations, missing or inadequate DPAs are one of the most common triggers for supervisory-authority enforcement.
Penalties and enforcement
Two-tier ceiling. Article 83(4) violations (record-keeping, data-processor duties, notification failures) cap at €10M or 2% of global annual turnover. Article 83(5) violations (unlawful processing, consent failures, transfers, data subject rights) cap at €20M or 4%, whichever is higher. National regulators have grown steadily more aggressive: Meta €1.2B (transfers, May 2023), Amazon Luxembourg €746M (ad targeting without valid consent, July 2021), Meta €390M (consent-to-contract shift), TikTok €530M (2025). Beyond headline enterprise cases, France’s CNIL, Spain’s AEPD, and Italy’s Garante regularly issue mid-five to seven-figure fines against SMEs for cookie consent violations, missing DPAs, and improper email marketing lists.
Real enforcement cases involving email marketing
Headline GDPR fines are mostly about data transfers and ad tracking. The cases below are the ones that matter for email senders: each one was decided on how marketing emails were consented to, sent or stopped. Amounts and dates come from the regulators’ own decisions.
| Company and regulator | Decision | Fine | What went wrong |
|---|---|---|---|
| Google (CNIL, France) | 1 Sept 2025 | €325M | Ads displayed between emails in Gmail inboxes without users’ consent, treated as electronic direct marketing under French ePrivacy law (CPCE L.34-5), plus cookies set at account creation |
| Solocal Marketing Services (CNIL) | 15 May 2025 | €900,000 | Email and SMS prospecting without valid consent, and prospect data passed to partners without a valid legal basis. Also ordered to stop prospecting without valid consent |
| Caloga (CNIL) | 15 May 2025 | €80,000 | Consent forms designed to push the “yes” button, unsubscribing harder than subscribing, data shared on legitimate interest instead of consent, and retention extended every time a prospect opened an email |
| KASPR (CNIL, all EU authorities consulted) | 5 Dec 2024 | €240,000 | B2B contact data scraped from LinkedIn profiles whose owners had limited its visibility, then used by customers for prospecting. Data kept 5 years from each update, and people informed only by an email in English |
| HelloFresh (ICO, UK) | 12 Jan 2024 | £140,000 | About 79 million marketing emails and 1 million texts in seven months without valid consent. The opt-in was bundled into an age confirmation statement (PECR regulation 22) |
What these cases teach email senders. Regulators look at the form, not the policy: button design, bundled checkboxes and pre-ticked boxes are judged on what the person actually saw. Unsubscribing must be as easy as subscribing. Consent does not travel: buying or renting a list, or sharing it with partners, needs consent for that use. And “the prospect opened our email” is not a reason to keep their data longer. For B2B, a named work address is still personal data, even when you found it on a public profile.
Sources: CNIL, Google; CNIL, Solocal Marketing Services; CNIL, Caloga; CNIL, KASPR; ICO, HelloFresh. Last reviewed November 2026.
Compliance checklist for email senders
- Identify the Article 6 legal basis for every list. Document it in your Record of Processing Activities (Article 30).
- Collect consent with an unchecked checkbox, plain-language purpose statement, and a clear identification of the sender. Store timestamp, source URL, and the exact consent language shown.
- Publish a privacy notice at the point of collection covering Articles 13 or 14 disclosures (identity, purposes, legal basis, retention, subject rights).
- Include a working unsubscribe link honored immediately in every marketing message. Delete or suppress within a documented retention window.
- Sign a written data processing agreement with every ESP, CDP, and marketing automation vendor. Confirm sub-processor lists and international transfer safeguards.
- For UK subscribers post-Brexit, apply UK GDPR + PECR (near-identical to EU GDPR but enforced separately by the ICO).
- For US or other international transfers, rely on the EU-US Data Privacy Framework certification for recipient organizations, or use Standard Contractual Clauses with a transfer impact assessment.
Common misconceptions
“Legitimate interest covers all B2B email.” Not everywhere. The answer depends on the national ePrivacy rules of the recipient’s country. France and the UK allow cold B2B email without prior consent under conditions, while Germany requires prior express consent for email advertising whether the recipient is a consumer or a business. See the country table above.
“We are not in the EU so GDPR does not apply.” Article 3(2) explicitly reaches organizations outside the EU that offer goods or services to EU residents or monitor their behavior. A signup form in English available worldwide is not a defence.
“Our ESP handles GDPR for us.” ESPs are data processors. The controller (you, the sender) retains full responsibility for consent, legal basis, and data subject rights. The ESP is only responsible for what it does with the data you send it.
“GDPR only fines the giants.” Headline fines target large platforms, but national regulators such as the CNIL, the AEPD, and the Garante regularly sanction smaller companies, including for email prospecting without a valid legal basis. Fines are proportional to the size of the company, not waived for it.
Official sources and legal note
Primary texts and regulator guidance
- Regulation (EU) 2016/679 (GDPR), official text on EUR-Lex
- Directive 2002/58/EC (ePrivacy), the rule behind consent for marketing email
- CNIL: commercial prospecting by email (France)
- ICO: electronic mail marketing under PECR (UK)
Recent enforcement covered by SMTPedia News
- Conseil d’État upholds Orange’s €50 million fine for ads in the inbox
- The largest email marketing fines on record, ranked
Not legal advice. This guide explains how the rules apply to email senders. It is not legal advice: for a decision about your own program, check the official text and ask a qualified lawyer.
Frequently asked questions
Does GDPR apply to B2B email?
Yes. Personal data under GDPR includes any information relating to an identified or identifiable natural person, work email addresses in the format firstname.lastname@company.com are personal data. Business generic addresses (info@, sales@) are outside GDPR scope but often still covered by national ePrivacy law and the EU ePrivacy Directive.
What is the soft opt-in exception?
Article 13(2) of the ePrivacy Directive allows email marketing without prior consent to existing customers for similar products or services, provided the address was collected in the context of a sale, the customer was given a clear opt-out at collection, and every subsequent message includes an easy opt-out. Individual member states implement the exception with slight variations; Germany and Italy interpret it narrowly, the UK PECR interpretation is broader.
Can I use pre-checked consent boxes?
No. The CJEU Planet49 decision (October 2019) and repeated CNIL enforcement have established that pre-ticked boxes do not constitute valid GDPR consent. A positive, unambiguous action from the subject is required.
How long can I keep marketing consent?
GDPR does not set a fixed expiry. The EDPB and national regulators expect controllers to refresh consent when the processing context materially changes, when the subject has been inactive for an extended period (commonly interpreted as 24 to 36 months for marketing lists), or when the legal basis or purpose changes. Retention periods must be published in the privacy notice.
What is a Data Processing Agreement (DPA)?
Article 28 requires a written contract between controller and processor covering processing scope, duration, purpose, categories of data and subjects, controller instructions, confidentiality, security measures, sub-processor engagement rules, data subject rights assistance, breach notification, and end-of-service data handling. Every ESP and marketing tool must provide one; missing or inadequate DPAs are one of the most common enforcement triggers.
Where to go next
- CNIL (France), the most active EU regulator on ad-tech and email marketing consent
- BfDI (Germany), federal DPA and 16 state DPAs with strict opt-in interpretation
- AEPD (Spain), highest volume of fines against SMEs across the EU
- CASL (Canada), express consent regime, stricter than the US opt-out model
- Spam Act 2003 (Australia), opt-in regime enforced by ACMA
- CAN-SPAM Act (US), opt-out contrast with GDPR’s opt-in regime
Building a GDPR-compliant list? Pre-validating recipient addresses with SMTPing before you press send catches disposables, catch-alls, and dead mailboxes that generate complaints from recipients who never gave valid consent. Thirteen validation types, twenty-five free checks daily, no card required. Try SMTPing free.
Did this guide save you time?
SMTPedia is free and independent. A coffee helps keep every guide accurate.
Buy SMTPedia a coffeeAbout the Author

Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.