Latest / Misar.Blog Podcast / Is Cold Email Legal Under GDPR? A 2026 Compliance Guide for B2B Sales Teams
Transcript
- Is Cold Email Legal Under GDPR? A 2026 Compliance Guide for B2B Sales Teams Is Cold Email Legal Under GDPR? A 2026 Compliance Guide for B2B Sales Teams Legal compliance documents and laptop showing GDPR regulations. Photo by Mika Baumeister on Unsplash Quick Answer: Yes, cold email is legal under GDPR for B2B sales, but only if you have a "legitimate interest" to contact the prospect, you identify yourself clearly, and you honor opt-out requests immediately. The rules are stricter than CAN-SPAM (US) but more permissive than many people think. Below, we break down GDPR's requirements for B2B cold email, the legitimate interest test, a jurisdiction-by-jurisdiction comparison, a 7-step compliance checklist, common mistakes, and 15 FAQs for 2026. On This Page GDPR vs CAN-SPAM: Key Differences The Legal Basis for Cold Email Under GDPR The Legitimate Interest Test (3-Part) B2B vs B2C: Different Rules How GDPR Compares to Other Regional Regimes The 7-Step GDPR Compliance Checklist How Compliance Differs by Company Size and Sales Motion Penalties for Non-Compliance Common Compliance Mistakes How MisarReach Helps with GDPR Compliance Frequently Asked Questions GDPR vs CAN-SPAM: Key Differences GDPR (EU/UK) and CAN-SPAM (US) are the two main regulations governing cold email. They have different requirements: Requirement GDPR (EU/UK) CAN-SPAM (US) Legal basis required Yes (legitimate interest or consent) No Opt-out mechanism Required, must be honored immediately Required, 10 business days to honor Identification Must identify yourself clearly Must include physical address Consent Required for B2C; not for B2B with legitimate interest Not required Penalties Up to €20M or 4% of global revenue Up to $51,744 per email Scope Applies to all data of EU/UK residents Applies to all commercial email sent in/from the US The key difference: GDPR requires a legal basis (usually "legitimate interest") before you can email someone. CAN-SPAM allows unsolicited email as long as you include an opt-out mechanism. Why this distinction matters practically. CAN-SPAM is fundamentally an "opt-out" regime — you can email almost anyone as long as you follow labeling and unsubscribe rules. GDPR is fundamentally a "justify first" regime — you need a lawful reason to process someone's personal data (their email address counts as personal data) before you ever hit send, not just a way for them to opt out afterward. This means a cold email campaign that's perfectly legal under CAN-SPAM (a clean list, clear sender ID, working unsubscribe link) can still violate GDPR if you never established a legitimate interest or consent basis for contacting those specific people. Sales teams operating across both the US and EU/UK often build their compliance process around the stricter GDPR standard and apply it everywhere, since it's easier to maintain one high bar than to segment campaigns by regulatory regime. The Legal Basis for Cold Email Under GDPR Under GDPR, you need one of six legal bases to process personal data (including email addresses): Consent — The person explicitly opted in to receive emails from you. Contract — You need to email them to fulfill a contract they have with you. Legal obligation — You're required to email them by law. Vital interests — You need to email them to protect someone's life. Public task — You're performing a task in the public interest. Legitimate interests — You have a legitimate business interest to email them, and their rights don't override yours. For B2B cold email, legitimate interests is the most common legal basis. Consent is rarely used for cold outreach (because the person hasn't opted in yet). Why legitimate interest exists as a basis at all. GDPR's drafters recognized that requiring prior consent for every possible business communication would make ordinary commerce unworkable — a supplier couldn't email a potential business customer, a recruiter couldn't reach out to a candidate, a researcher couldn't contact an industry expert. Legitimate interest is the basis that lets normal business-to-business communication continue, provided it's balanced against the individual's reasonable expectations and rights. It is not a loophole or a technicality — it's a deliberately built-in basis for exactly the kind of relevant, well-targeted outreach this guide describes. What it is not is a basis for mass, untargeted, or irrelevant email — the moment the "legitimate" and "relevant" qualifiers stop being true, the basis stops applying. The Legitimate Interest Test (3-Part) To rely on legitimate interest, you must pass a 3-part test (per the ICO and EDPB guidelines): Part 1: Purpose — Is There a Legitimate Interest? You must identify a specific, lawful purpose for the email. Examples of legitimate interests: Selling a product or service relevant to the recipient's business Building a business relationship with a potential customer Conducting market research Networking with industry peers Examples of illegitimate interests: Sending spam or unsolicited marketing unrelated to the recipient's business Selling the recipient's data to third parties Harassing the recipient after they've opted out How specific does the purpose need to be? "We want to sell software" is too broad to be a defensible purpose on its own. A defensible purpose statement names the product category, the target persona, and the reason that persona would plausibly care — for example, "We sell outbound sales automation software to Heads of Sales at B2B SaaS companies with 50-500 employees, because that persona is typically responsible for outbound pipeline generation." Writing this sentence down for every campaign — not just thinking it, but documenting it — is what turns "we assume this is fine" into a defensible compliance record if you're ever asked to justify it. Part 2: Necessity — Is Email the Least Intrusive Way? You must show that email is necessary to achieve your purpose. If you could achieve the same result through less intrusive means (e.g., a public LinkedIn post), email may not be justified. For B2B sales, email is generally considered necessary because: It's the standard channel for B2B communication It's less intrusive than phone calls It allows the recipient to respond at their convenience Necessity is a comparative test, not an absolute one. Regulators aren't asking "could you have avoided contacting this person at all" — they're asking "among the realistic ways to reach this specific business contact, is email a reasonable and proportionate choice." Compared to unsolicited phone calls (which interrupt in real time) or SMS (which lands on a personal device many people treat as more private than email), a well-targeted business email to a work address is generally viewed as one of the less intrusive channels available — which is one reason email survives scrutiny that cold calling and cold SMS often don't. Part 3: Balancing — Do the Recipient's Rights Override Your Interest? You must balance your legitimate interest against the recipient's rights and freedoms. Consider: Expectations: Would the recipient reasonably expect to receive this email? (A CEO of a tech company would expect B2B sales emails; a private individual would not.) Impact: What is the impact on the recipient? (A single, relevant email is low impact; a barrage of irrelevant emails is high impact.) Safeguards: What safeguards have you put in place? (Easy opt-out, clear identification, relevant content.) If the recipient's rights override your interest, you cannot rely on legitimate interest. For most B2B sales, the balance favors the sender — but only if the email is relevant and the recipient can easily opt out. Documenting the balancing test: the Legitimate Interest Assessment (LIA). Larger or more risk-conscious teams often formalize this three-part test into a short written Legitimate Interest Assessment for each significant campaign — a one-page document answering: what's the purpose, why is email necessary, and how have we weighed the recipient's rights (including what safeguards are in place). An LIA doesn't need to be a legal document drafted by outside counsel; it needs to exist, be specific to the campaign, and be something you could show a regulator or a concerned prospect if asked. Teams that skip this step aren't necessarily non-compliant, but they have a much harder time demonstrating compliance after the fact — which matters because the burden of proof under GDPR sits with the data controller (you), not the recipient. Hand holding a phone showing an email inbox notification. Photo by Maxim Ilyahov on Unsplash B2B vs B2C: Different Rules GDPR treats B2B and B2C email differently: B2B Cold Email (More Permissive) Legal basis: Legitimate interest is usually sufficient. Consent: Not required if legitimate interest applies. Identification: Must identify yourself and your company. Opt-out: Must be easy and immediate. Content: Must be relevant to the recipient's business. B2C Cold Email (Stricter) Legal basis: Consent is usually required (under PECR/ePrivacy). Consent: Must be explicit, informed, and freely given. Identification: Must identify yourself and your company. Opt-out: Must be easy and immediate. Content: Must be relevant to the recipient's interests. The key difference: B2C cold email generally requires prior consent (under PECR in the UK and ePrivacy Directive in the EU). B2B cold email can rely on legitimate interest. Important: Even in B2B, if you're emailing a sole trader or freelancer (a "natural person" conducting business), GDPR treats them more like a B2C contact. Be cautious about emailing individuals at companies without a legitimate interest test. Where the B2B/B2C line gets blurry. The cleanest cases are easy: emailing the VP of Sales at a 500-person software company using her corporate email address is clearly B2B. Emailing an individual freelance graphic designer at her personal Gmail address about a design tool is closer to B2C territory, even though she's technically running a business. The safest practical rule: the more the recipient's role resembles "employee acting on behalf of an organization" (corporate domain, job title, org-relevant purpose), the more comfortably legitimate interest applies. The more the recipient resembles "an individual who happens to also do freelance or sole-trader work" (personal email domain, no formal company structure, the product is more consumer-adjacent), the more you should treat the email like a B2C send and lean toward consent-based approaches or at minimum an extra-cautious legitimate interest assessment. Role-based vs personal emails. A related distinction worth building into your data hygiene: sales.com or info.com are role-based addresses that GDPR treats somewhat differently from jane.smith.com — role addresses aren't tied to an identifiable individual in the same way, which reduces (though doesn't eliminate) some data protection considerations. Many compliance-conscious teams still apply the same standard to both, since role-based inboxes are frequently monitored by a specific named person anyway. How GDPR Compares to Other Regional Regimes Sales teams selling internationally increasingly need to think beyond GDPR and CAN-SPAM alone. Here's a broader picture of how major regimes treat B2B cold email: Regime Region B2B legal basis Consent needed? Opt-out timeline GDPR EU / UK Legitimate interest (or consent) No, if legitimate interest applies Immediate CAN-SPAM United States None required No 10 business days CASL Canada Implied consent (existing business relationship) or express consent Often yes, with narrow B2B exemptions 10 business days PIPEDA Canada (general privacy) Reasonable purpose Generally consent-oriented Immediate India DPDP Act India Consent (narrow "legitimate use" exemptions) Generally yes Per notice terms Privacy Act / Spam Act Australia Consent (express or inferred from business context) Yes, inferred consent possible for B2B 5 business days LGPD Brazil Legitimate interest (similar structure to GDPR) No, if legitimate interest applies Immediate The practical takeaway for multinational campaigns. If your prospect list spans the EU, UK, Canada, and Australia, the safest approach is to build your process around the strictest applicable regime for each recipient's jurisdiction rather than applying a single global standard that might be too permissive somewhere and unnecessarily strict elsewhere. Canada's CASL, in particular, is stricter than GDPR in some respects — it narrows the "implied consent" business exemption to cases involving an existing business relationship or a recent, specific inquiry, which is a higher bar than GDPR's legitimate interest test for a genuinely first-touch cold email. The 7-Step GDPR Compliance Checklist Here's a step-by-step checklist to ensure your cold email campaigns are GDPR-compliant: Step 1: Identify Your Legitimate Interest Document the specific legitimate interest for your campaign. Examples: "We are selling [product] to [ICP] companies." "We are building a business relationship with [ICP] decision-makers." "We are conducting market research on [topic]." Step 2: Verify the Email Is Business-Related Ensure the email address is a business contact (not a personal Gmail/Yahoo address). B2B rules apply to business emails; B2C rules apply to personal emails. Step 3: Ensure the Content Is Relevant The email must be relevant to the recipient's business. Generic mass-marketing emails are not legitimate interest. Personalized, relevant emails are. Step 4: Identify Yourself Clearly Every email must include: Your name Your company's name Your company's physical address A clear explanation of why you're contacting them Step 5: Include an Easy Opt-Out Every email must include a one-click opt-out mechanism. Honor opt-out requests immediately (within 24 hours, not the 10 days allowed under CAN-SPAM). Step 6: Maintain a Suppression List Keep a list of people who have opted out and ensure they're never emailed again. This is both a legal requirement and a deliverability best practice. Step 7: Document Your Compliance Keep records of: Your legitimate interest assessment How you obtained the email addresses When and how you honored opt-out requests Your suppression list If a data protection authority investigates, you must be able to demonstrate compliance. Building this into your actual workflow. Most sales teams don't fail GDPR compliance because they disagree with these seven steps in principle — they fail because the steps live in a policy document nobody references day-to-day, while actual list-building and sending happen in a completely separate tool with no compliance guardrails. The teams that stay compliant consistently are the ones who bake these steps into the tooling itself: a list-import process that automatically checks against the suppression list, a campaign-launch step that requires a documented purpose before sending is allowed, and an opt-out link that removes a contact from every future campaign automatically rather than relying on someone to update a spreadsheet by hand. How Compliance Differs by Company Size and Sales Motion Solo founders and small teams (1-10 people). Compliance risk is real but manageable — the biggest practical risk is usually informality: no written legitimate interest documentation, no formal suppression list beyond "I remember who asked to be removed," and personal email accounts used for outreach instead of dedicated, authenticated sending domains. At this scale, the fix isn't hiring a compliance team — it's adopting basic structure early: a real suppression list (even a spreadsheet is fine, as long as it's actually checked before every send), a one-paragraph documented purpose per campaign, and a consistent unsubscribe mechanism. Mid-size sales teams (10-100 reps). The main risk shifts from "no process" to "inconsistent process" — different reps building lists from different sources, some more compliant than others, with no central suppression list shared across the whole team. A prospect who opts out from one rep's outreach can still get emailed by a different rep two weeks later if suppression isn't centralized. This is the size where a shared sales engagement or outreach platform with built-in, team-wide suppression handling (rather than per-rep spreadsheets) starts to matter a great deal for compliance, not just productivity. Enterprise sales organizations (100+ reps, multiple business units). Compliance complexity multiplies because different business units may be targeting the same accounts with different products, each maintaining separate lists and separate (or nonexistent) suppression logic. A prospect who opts out of outreach from the core product team might still receive email from a newly launched product line's SDR team, technically violating the spirit (and often the letter) of an opt-out that should apply company-wide. At this scale, GDPR compliance becomes a data governance problem as much as a sales process problem, usually requiring a central data protection function, a company-wide suppression list, and clear ownership of what "opted out" actually means across every team that might contact that person. Inbound-assisted vs pure outbound motions. Teams doing account-based, highly researched outbound (fewer emails, more personalization, tighter ICP) generally have an easier time passing the legitimate interest test than teams doing high-volume, loosely-targeted outbound, because relevance and proportionality are baked into the former approach and have to be actively engineered into the latter. This is one more reason the depth of targeting described throughout our sales prospecting techniques guide isn't just a performance best practice — it's also a compliance best practice, since a well-targeted, relevant email is inherently easier to justify under the necessity and balancing tests than a generic blast. Penalties for Non-Compliance GDPR penalties are severe: Lower tier: Up to €10M or 2% of global annual revenue (whichever is higher). Higher tier: Up to €20M or 4% of global annual revenue (whichever is higher). The higher tier applies to violations of the core principles (including lawful basis for processing). Real examples: Marriott International (2020): Fined €18.4M for failing to protect customer data. British Airways (2020): Fined €22M for a data breach affecting 400,000 customers. Amazon (2021): Fined €746M (proposed) for behavioral advertising violations. While these are extreme cases, they illustrate that GDPR enforcement is real and penalties are substantial. What this means for a typical B2B sales team. It's worth being clear-eyed about what these headline fines actually represent: they're almost all large-scale data breaches or systemic, company-wide data-processing violations at some of the largest companies in the world — not a single sales rep sending a handful of poorly targeted cold emails. That doesn't mean small and mid-size companies are immune from enforcement; national data protection authorities do investigate and sanction smaller B2B spam complaints, typically starting with a warning or an order to stop processing rather than a maximum fine, especially for a first-time, good-faith compliance gap rather than a deliberate, repeated violation. The realistic risk for most B2B sales teams isn't a nine-figure headline fine — it's a formal complaint, a regulator's inquiry, reputational damage, and the operational cost of an investigation, all of which are meaningfully reduced by having the documentation described in the 7-step checklist above ready before you need it. Common Compliance Mistakes Treating "B2B" as a blanket exemption from GDPR. B2B status lowers the bar (legitimate interest instead of consent) — it doesn't remove the bar entirely. Every element of the legitimate interest test still has to be satisfied. Buying or scraping lists with no visibility into how the data was collected. As the data controller for your own outreach, you're responsible for the lawfulness of processing even if a third party originally collected the data — "the list vendor said it was fine" is not, on its own, a valid defense. Using a slow or manual opt-out process. A "reply to unsubscribe" system that depends on someone manually removing a contact within days, rather than an automated system that suppresses instantly, routinely fails the "honor opt-outs immediately" standard. Not distinguishing role-relevance from company-relevance. A legitimate interest to email a company's Head of Sales about a sales tool doesn't automatically extend to emailing every employee at that company with the same pitch — relevance is assessed at the level of the actual recipient's role, not just their employer. Reusing a list across unrelated campaigns. A legitimate interest assessment is specific to a purpose. A list built for one product's outreach shouldn't be silently repurposed for an unrelated product without reassessing whether the original justification still applies. Ignoring the physical address requirement. Teams remember the opt-out link but forget that GDPR-adjacent best practice (and several national implementations) expects a real postal address for the sending organization, not just a website URL. Assuming data residency doesn't matter. Where prospect data is stored and processed (which cloud region, which vendor's servers) can itself be a GDPR consideration for EU/UK contacts, independent of how the email itself is written. No audit trail for opt-outs. If a prospect opts out and is accidentally re-added to a list six months later (a common failure mode when lists get merged or re-imported), the absence of a timestamped opt-out record makes it very hard to prove the re-contact was an honest mistake rather than a pattern of non-compliance. How MisarReach Helps with GDPR Compliance MisarReach includes built-in GDPR compliance features: Opt-out suppression: Automatically suppresses contacts who have opted out of unsolicited outreach. Legitimate interest templates: Pre-built email templates that include identification, opt-out, and relevance signals. Audit trail: Logs every email sent and every opt-out processed for compliance documentation. Data residency: EU data residency available for EU customers. These features reduce your compliance risk and make it easier to demonstrate GDPR compliance if investigated. Frequently Asked Questions Is cold email legal under GDPR? Yes, for B2B sales, if you have a legitimate interest, identify yourself clearly, and honor opt-out requests. B2C cold email generally requires prior consent. Do I need consent to send cold email under GDPR? Not for B2B if you can demonstrate legitimate interest. For B2C, yes — consent is required under PECR/ePrivacy. What is the legitimate interest test? A 3-part test: (1) Is there a legitimate interest? (2) Is email necessary? (3) Do the recipient's rights override your interest? If all three pass, you can rely on legitimate interest. Can I email sole traders or freelancers under GDPR? Yes, but with more caution. Sole traders are "natural persons" conducting business, so GDPR treats them more like B2C contacts. Ensure you have a strong legitimate interest and easy opt-out. How quickly must I honor opt-out requests under GDPR? Immediately. Unlike CAN-SPAM (which allows 10 business days), GDPR requires you to honor opt-outs as soon as possible — ideally within 24 hours. What happens if I violate GDPR? Penalties range from warnings to fines of up to €20M or 4% of global revenue. Data protection authorities can also order you to stop processing. Do I need a Data Protection Officer (DPO) for cold email? Not necessarily. A DPO is required only if your core activities involve large-scale monitoring of individuals or processing of special categories of data. For most B2B sales teams, a DPO is not required. Can I buy email lists under GDPR? Risky. If the list was collected without GDPR-compliant consent or legitimate interest, using it violates GDPR. You're also liable as the "data controller" for how the data was obtained. Build your own lists through compliant methods instead. Does GDPR apply if my company isn't based in the EU? Yes, if you're emailing people located in the EU or UK, GDPR applies regardless of where your company is headquartered. GDPR has extraterritorial scope based on the location of the data subject, not the sender. Can I use a generic "info@" or "sales@" inbox to send cold email instead of a named person's address? You can, but it doesn't remove the underlying compliance obligations — you still need a legitimate interest, clear identification of your organization, and an opt-out mechanism. What it can do is make the email feel less personal and often perform worse from a reply-rate standpoint, independent of compliance. What's the difference between "legitimate interest" and "consent" in practice? Legitimate interest lets you email someone without their prior opt-in, provided you pass the three-part test and can justify it if challenged. Consent means the person actively opted in beforehand (e.g., checked a box, replied to confirm). Legitimate interest is faster to use for first-touch B2B outreach; consent is a stronger, more defensible basis once you have it, which is why many teams try to convert a legitimate-interest relationship into an explicit opt-in over time (e.g., a newsletter signup) rather than relying on legitimate interest indefinitely. If a prospect replies to my cold email, does that count as consent for future marketing? Not automatically. A reply engaging with your specific outreach doesn't necessarily constitute consent for a different kind of processing, such as adding them to a recurring marketing newsletter. If you want to send them something categorically different later, it's best practice to ask explicitly rather than assume the earlier reply covers it. Do opt-out requests need to be honored across my whole company, or just the team that sent the email? Best practice — and in many interpretations, the compliant approach — is company-wide suppression. If a prospect opts out of outreach from one team, a different team at the same company re-contacting them shortly after, using the same underlying data, undermines the opt-out and increases regulatory and reputational risk. This is especially relevant for larger sales organizations running multiple simultaneous campaigns. How does GDPR compliance interact with cold calling and LinkedIn outreach, not just email? The same underlying principles (lawful basis, relevance, ability to opt out) apply to phone and other channels, though the specific regulatory mechanics differ — cold calling is additionally governed by telemarketing rules in many EU countries, and LinkedIn outreach is governed by LinkedIn's own Terms of Service on top of GDPR. See our guide on LinkedIn automation risk for how that channel's compliance picture differs from email's. Should I get legal review before launching a large cold email campaign into the EU? For a small, well-targeted, clearly relevant B2B campaign, many teams operate confidently using the framework in this guide without per-campaign legal sign-off. For large-scale campaigns, campaigns involving sensitive industries (healthcare, finance, children's products), or campaigns where the ICP-relevance is less obvious, a brief legal review of your legitimate interest assessment is a reasonable and often inexpensive safeguard before scaling up. Tags: Related Reads TCPA and SMS Compliance for B2B Sales Outreach: What Changed in 2026 How to Write a Cold Email That Actually Gets a Reply (2026 Framework) Sales Prospecting Techniques That Actually Work in 2026