GDPR and email marketing lists
Two separate instruments govern marketing email in the EU, and conflating them is the source of most of the confusion.
The GDPR (Regulation (EU) 2016/679, applicable since 25 May 2018) governs the processing of personal data. An email address that identifies a person is personal data, so collecting, storing and mailing a list is processing under the GDPR.
The ePrivacy Directive (2002/58/EC, as amended) governs electronic communications specifically. Article 13 sets the rules on unsolicited commercial email. Because it is a directive rather than a regulation, it is implemented separately in each member state's national law — which is precisely why the answer to "can I email businesses without consent?" is different in Germany and in Ireland.
You need to satisfy both. The GDPR tells you whether you may hold and process the data; ePrivacy tells you whether you may send the message.
Lawful basis under the GDPR
Processing needs a lawful basis from Article 6. For marketing lists, two are realistic.
Consent, Article 6(1)(a)
The GDPR defines consent in Article 4(11) as a freely given, specific, informed and unambiguous indication of the data subject's wishes, given by a statement or a clear affirmative action. Article 7 adds the conditions. In practice that means:
- Unticked by default. A pre-ticked box is not a clear affirmative action; this was settled in the Planet49 ruling of the Court of Justice.
- Separate from other terms. Consent to marketing cannot be bundled into acceptance of the terms of service.
- Specific. If you will send a newsletter and also share the address with partners, those are separate purposes needing separate consent.
- Not a condition of service where the service does not require it. Article 7(4) makes consent extracted as the price of an unrelated service questionable.
- As easy to withdraw as to give, under Article 7(3).
- Demonstrable. Article 7(1) puts the burden of proof on you.
Legitimate interest, Article 6(1)(f)
Recital 47 of the GDPR acknowledges that direct marketing may be carried out on the basis of legitimate interest. This is real, but narrower than people hope: it requires a documented balancing test weighing your interest against the rights and reasonable expectations of the recipient, and it does not override the ePrivacy rules on sending. Relying on legitimate interest to cold-email consumers in a member state that requires prior consent for electronic marketing does not work, however good your balancing test is.
Where legitimate interest is more defensible is in B2B contexts in jurisdictions that permit it, and for related processing such as maintaining a suppression list.
The soft opt-in
Article 13(2) of the ePrivacy Directive creates an exception that a great deal of legitimate marketing depends on. Where you obtained an address in the context of a sale of a product or service to that person, you may market your own similar products or services to them, provided they were clearly given the opportunity to object at the point of collection and in every subsequent message.
Each element is load-bearing. The address must come from an actual sale or negotiation of a sale, not from a whitepaper download in some implementations; the products must be similar to what was sold; the opt-out must have been offered at collection, not only later. National implementations vary on how strictly "sale" and "similar" are read.
Check an address before you send to it
Mailcheq runs syntax, MX, disposable, role-account and live SMTP checks in the browser, free.
Verify an address →B2B is not exempt
The most persistent myth in European email marketing is that B2B sits outside the rules. It does not, in two distinct ways.
Under the GDPR, a named business address such as firstname.lastname@company.com identifies an individual and is personal data. A pure role address such as info@company.com generally does not identify a person, which is one reason role addresses are treated differently — though that is a data-protection argument, not a deliverability one, and mailing role addresses remains a reliable way to generate complaints.
Under ePrivacy, member states chose different approaches for corporate subscribers. Some require prior consent for all electronic marketing regardless of recipient; others permit unsolicited B2B mail subject to an opt-out. Germany is at the strict end; Ireland and the Netherlands draw a clearer line at corporate subscribers. If you are sending across Europe, you are subject to the rules of each recipient's country, so the practical compliance posture is the strictest one in your target set.
Purchased and scraped lists
A bought list fails on several grounds at once. Consent is not transferable: the people on it consented to something else, with someone else, if they consented at all. You cannot satisfy Article 7(1) and demonstrate consent you never obtained. Articles 13 and 14 require you to tell people where their data came from and what you will do with it, which a list vendor's records rarely support.
Beyond the legal problem there is a mechanical one. Bought lists are the single most reliable source of spam traps, and the fastest route to a blocklisting and an ESP account suspension. There is no version of this that goes well.
Verifying a purchased list does not help with any of this. Verification confirms addresses are deliverable; it says nothing about whether you are allowed to mail them.
Proving consent
Because Article 7(1) puts the burden on you, the records are the control. For each subscriber, keep:
- the timestamp of the consent action;
- the source — which form, on which page;
- the exact wording shown at the time, or a version reference to it;
- the IP address and user agent, where you collect them;
- for confirmed opt-in, the timestamp of the confirmation click.
Keeping the wording matters more than people expect. "They consented" is worth little if you cannot show what they were agreeing to. Confirmed opt-in produces much the strongest record, which is a compliance argument for it on top of the deliverability one.
Erasure versus suppression
Article 17 gives a right to erasure, and an unsubscribe is also a withdrawal of consent under Article 7(3). This creates an apparent conflict: if you delete every trace of someone, how do you avoid mailing them again after they are re-imported from another source?
The accepted resolution is a suppression list holding the minimum needed to recognise the address — commonly a hash of it — processed on the basis of your legal obligation not to contact them again. Keep it separate from the marketing database, keep it minimal, and explain it in your privacy notice. Do not use a suppression list as a place to quietly retain profile data.
What this means operationally
- Collect consent on an unticked, separate, specific control, and log what was shown.
- Use confirmed opt-in for anything collected through a public form.
- Put a working unsubscribe link in every marketing message and process it promptly; for bulk senders to Gmail and Yahoo, one-click unsubscribe headers are a technical requirement as well as a legal courtesy.
- Name your organisation and purpose at the point of collection, and link your privacy notice from the form.
- Have a data processing agreement with your ESP and your verification provider, both of which act as processors.
- Apply retention: an address nobody has engaged with for years is hard to defend as necessary for the purpose it was collected for, and mailing it is bad for reputation anyway. Compliance and deliverability point the same direction here.
That last point is worth holding on to. Almost everything the GDPR and ePrivacy require of an email sender — genuine consent, accurate records, easy exit, no stale data — is also what keeps complaint rates down and mail in the inbox. The rules and the results are not in tension.
Spotted an error on this page? Email hello@mailcheq.com and we will fix it.