Sales Prospecting and GDPR: The Email Law Is the Real Gate

    Short answer

    A compliant prospecting workflow from lawful basis to first-contact notice, opt-out wording and retention, with the email rules split by country

    Artem Smirnov
    Artem Smirnov

    Last updated · 13 min read

    Artem Smirnov in a dark suit against a charcoal studio backdrop, next to the line 'GDPR IS NOT THE BLOCKER. The email law on top of it is'

    Not always, and that is where the country matters. B2B sales prospecting is legal under the GDPR, and the GDPR itself does not require consent for every contact.

    The regulation lists several lawful bases. Prospecting usually relies on legitimate interests, in Article 6(1)(f). Recital 47 covers direct marketing. Such processing "may be regarded as carried out for a legitimate interest" (GDPR text on EUR-Lex).

    Two conditions come with that basis. The person's rights must not override your interest, and you must be able to show that you weighed them.

    The GDPR itself seldom stops a B2B campaign. The email law of the recipient's country can, and it sits on top of the GDPR. In the EU that is the ePrivacy Directive as each member state applied it. In the UK it is PECR. In Germany, for example, the national rule is section 7 of the UWG.

    If you sell into several countries, settle that second layer market by market before anything goes out. One list can hold records that are fine to email, records that need consent and records you should only reach on LinkedIn.

    Being outside Europe does not take you out of scope either. The EDPB's 2019 guidelines on territorial scope set out two tests: where a business is established, and whom it targets. Having no EU office does not, on its own, keep you out.

    Article 3(2) applies the GDPR to a business with no EU establishment when it targets people in the Union with goods or services. A US company emailing buyers in the Netherlands is covered.

    This is not legal advice. Take your own setup to your counsel. Regulators have drawn the line in actual cases: the real fines behind cold outreach.

    Is a business email address personal data?

    Usually, yes. Article 4(1) defines personal data as information that relates to a natural person who is identified or identifiable, and a name is the first example in that definition. A work address built from someone's name points to one person, so it is covered.

    The UK regulator draws the same line (ICO guidance on business-to-business marketing). If the address you write to identifies an individual, such as one built from initials and a surname, UK GDPR applies. Marketing to a generic department inbox usually involves no personal data, so UK GDPR usually does not apply there, though PECR can still apply.

    This matters more for list building than for sending. A prospect list is a file of names, titles and personal work addresses, so the GDPR applies from the day you build it, long before anything goes out.

    My team builds every list around the real buyer job titles in each niche, such as contracts manager or head of procurement. Never a bare "manager" title. Every one of those rows names a person, so the GDPR covers the list from row one.

    Role inboxes do not get you around this. A generic inbox may fall outside UK GDPR, but the person who signs the purchase order rarely reads it.

    Lists pulled from LinkedIn profiles are personal data too. Whether scraping those profiles for email addresses is allowed at all is a separate question, and one to put to your counsel before you try it.

    Which rule decides if you can send the email, GDPR or the email law?

    Both apply, and the stricter one wins. You need a GDPR lawful basis to hold and use the data, and you need the email law to allow the message. A strong legitimate interest cannot override an email rule that demands consent.

    EU. Article 13 of the ePrivacy Directive requires prior consent for email direct marketing to subscribers who are natural persons, with some exceptions such as the soft opt-in for existing customers (ePrivacy Directive, consolidated text on EUR-Lex). Member States decide the rules for legal persons.

    For a company mailbox in the EU, the answer sits in each country's national law. The directive does not settle it, so check the market before you send.

    A "subscriber" is simply the party that holds the email account and has the contract with the mail provider. A freelance engineer on her own domain is a natural person. A project director writing from his employer's mailbox sits behind a company subscriber.

    UK. According to the ICO, corporate subscribers fall outside the PECR email marketing rule. Two duties still apply to every message: you must not hide who is sending, and every recipient needs a working address for stopping further messages. Sole traders and some kinds of partnership count as individuals, so the consent rule covers them.

    Germany. Section 7 of the UWG, the German Act Against Unfair Competition (UWG section 7 on gesetze-im-internet.de), counts email advertising sent without the addressee's prior express consent as an unreasonable nuisance. The statute text gives no carve-out for business recipients. It also counts any advertising message that conceals the sender, or gives no valid address for stop requests, as a nuisance in every case.

    The existing-customer exception. The directive and the UWG both carve out a narrow route usually called the soft opt-in. It covers contact details you obtained in the course of a sale, used to market your own similar products. The person must get an easy, free way to object when you collect the address and in every message after that. The UWG adds one condition: the customer must not have objected already.

    A cold prospect never qualifies.

    Recipient type or countryGDPR layerEmail ruleConsent needed for cold email?What every message must include
    EU, natural person subscriber (sole trader or own domain)Legitimate interest possible after a documented checkePrivacy Art. 13, applied in national lawYes, unless the soft opt-in appliesSender identity in full, a valid address to stop messages
    EU, company mailbox (legal person subscriber)Legitimate interest possible after a documented checkNational law decides how company subscribers are protectedSet by each country's law; check before sendingSender identity in full, a valid address to stop messages
    UK, employee of a limited company (corporate subscriber)UK GDPR, usually legitimate interestPECR email rule does not applyNoIdentity not concealed, a valid opt-out address
    UK, sole trader or some partnershipsUK GDPR, usually legitimate interestTreated like individuals under PECRYes, or the soft opt-inIdentity not concealed, a valid opt-out address
    Germany, any recipientGDPR, legitimate interest possibleUWG section 7Yes, prior express consent; existing-customer exception under strict conditionsSender not concealed, a valid address for stop requests

    Read the table row by row before a launch. If a record lands in a "yes" row and you have neither consent nor a customer relationship, email is off for that record, whatever your legitimate interest check says. Move it to a channel the rule permits, or drop it.

    How do you run a legitimate interest check before a campaign?

    The ICO frames legitimate interest as a three-part test: purpose, necessity and balancing (ICO legitimate interests guidance). Recital 47 adds the reasonable expectations test. Ask whether the person could reasonably expect this use of their data, given when and how you got it.

    Here is the check in fill-in form. Answer each question in writing before the list goes near a sending tool.

    QuestionA pass sounds likeA fail sounds like
    1. What business interest does this campaign serve, stated in one sentence?"Offer site welfare unit rental to main contractors starting UK residential schemes.""Grow revenue in Europe."
    2. Is each data field necessary, or could you reach the same buyer with less?Name, job title, work email, company, country, sourcePersonal mobile, home city, every field the enrichment tool offers
    3. Would this person reasonably expect a message about this offer in their job role?A procurement manager at a contractor hearing about site equipmentAn HR assistant at a bank hearing about site equipment

    Worked example (an illustration only). Picture a fictional UK supplier, Northfield Site Services Ltd, that wants to reach contracts managers and procurement managers at main contractors in England.

    • Purpose: rent and service welfare units on new residential sites, a supply these buyers purchase on every project.
    • Necessity: six fields per person (name, job title, work email, company, country, source), nothing personal outside the job.
    • Balancing: these titles buy site equipment as part of the job. Each message gives a one-word way out, and the records come from a source the supplier can name.

    The recipients sit in the UK corporate subscriber row, so the email rule allows the send as long as the identity and opt-out duties are met.

    Article 5(2) makes you responsible for being able to demonstrate compliance. Date the filled check and keep it in the campaign file.

    What does a compliant prospecting workflow look like step by step?

    Run these six steps in order.

    1. Define the ICP and the purpose. Article 5(1)(b) requires you to gather data for a purpose that is specific, clearly stated and legitimate. Write the purpose into the campaign file in one sentence. Data you gathered for one offer does not automatically carry over to another.
    2. Pick fields by necessity. Article 5(1)(c) limits you to what is necessary for that purpose. For most B2B outreach that means name, job title, work email, company, country and source. Tag each record with country and subscriber type (company or individual). Those two tags decide which row of the table applies.
    3. Source the list and record where each record came from. Check how B2B data providers handle GDPR before you buy. Cheap freelancer lists leave you unable to say where a record came from, and in my experience their open rates stay low and their bounces run high. Verify every address before the first send. My team keeps the bounce rate below 0.5%, and a verified list also serves the accuracy principle in Article 5(1)(d).
    4. Run the check and apply the country rule. Fill in the three questions, then tag every record with its channel: "email", "LinkedIn only" or "exclude". A UK sole trader without consent gets "LinkedIn only". A German contact without consent never gets "email".
    5. Check the suppression list before every send, and log every reply. Compare each batch against your suppression list right before it goes out. Record replies and objections in a CRM. Any CRM will do, as long as no lead and no objection ever gets lost.
    6. Review the list on a schedule. Use the retention table below to decide when each record is checked again, deleted or kept.

    What should the opt-out line in a cold email say?

    The email-law floor is short. Both the ePrivacy Directive and PECR require that you do not disguise the sender and that you give a valid address for stop requests.

    The ICO also says anyone may object to your direct marketing, and that the right to object to direct marketing is absolute. Once someone objects to marketing, you stop, and no balancing argument applies. The GDPR adds one more duty. If the data did not come from the person themselves, Article 14 makes you tell them who you are, why you hold the data and where you got it.

    The full Article 14 list also covers the legal basis, the categories of data, how long you keep it and the person's rights, including the right to object.

    Article 14(3)(b) sets the deadline when you use the data to contact someone: your first communication at the latest (GDPR text on EUR-Lex). In practice, that is one line in the first email plus a link to a privacy page that covers each point.

    A reply-to address only works as a stop address if a person reads it. My team puts an inbox manager on every campaign's replies, because a "please stop" buried in a long thread is still an objection.

    Here is a sample first email, written for this article to a fictional recipient at a UK limited company. It sells a 15-minute call and leaves the service out of it, because a pitch in the opening message is the quickest way to get ignored:

    Subject: Welfare units for your Leeds sites

    Hi Laura,

    Your team is starting two residential schemes around Leeds this spring. We supply and service site welfare units for main contractors in Yorkshire. Would a 15-minute call next week help, before those packages are placed?

    Tom Hale, Head of Sales, Northfield Site Services Ltd, 14 Wharf Street, Leeds

    Not relevant? Reply "stop" and I will not contact you again. Where we found your details and your rights: northfield.example/privacy

    A second opt-out line for cold email:

    • Wrong person or wrong time? Reply "no" and you will not get another email from me or my team.

    Opt-out lines for a LinkedIn follow-up:

    • If this is not for you, just say so here and I will not message you again.
    • Happy to leave it there if it is not relevant. One word is enough and I will stop.

    On my team, any negative reply, from "not interested" to an annoyed one-liner, ends the sequence and puts the person on the exclusion list.

    Stopping after a "no" does not clash with follow-ups, because follow-ups only go to people who have not objected. Sending one or two messages never gets the job done. A single "buy or die" message is a lottery ticket. The reply usually comes on the third follow-up, sent after a real gap, which is why my sequences run to 5 or 6 touches over LinkedIn and email.

    Send one more touch after a "no" and you risk a complaint and a damaged domain reputation.

    How long can you keep prospect data?

    The GDPR sets no fixed number of days. Article 5(1)(e) says you keep personal data no longer than necessary for the purpose. You set the periods yourself, and you have to be able to justify them.

    The review points below are my own illustrations and carry no legal force. Tie each one to your own sales cycle, put a date on it and write it down.

    Prospect statusSuggested review pointAction
    No reply after the full sequenceA date you set, for example one sales cycle after the last messageDelete, unless a fresh check for a new offer justifies one more campaign
    Objected or asked to stopImmediatelySuppress: keep the address, the date and "do not contact"; delete the rest
    Bounced or left the companyWhen the bounce or change is loggedDelete the person's details; keep the dead address on a bounce list so a new data pull cannot add it back
    Interested, not readyThe follow-up date you agreed with the personKeep, with conversation notes; delete if it goes quiet past your own written limit
    Became a clientWhen the contract is signedMove to customer records under your client retention rules

    The "objected" row is where most teams slip. Deleting an objector feels respectful, but it backfires. The ICO describes a company that deleted a person's number, later bought a list that contained it and contacted them again, and says a suppression list would have prevented the breach (ICO guidance on respecting people's preferences).

    Keep the "interested, not ready" row only if someone wrote down when the person said "not now" and what would change their mind.

    How do stricter markets like Germany change the plan?

    Our campaigns mostly target the USA, the UK and Europe, and mainly English-speaking markets.

    Germany sits outside our specialty, so when a client asks for it, we apply a stricter set of house rules. For German, Austrian and Czech prospects, cold email stays switched off unless a compliant basis exists, and the outreach runs on LinkedIn.

    Here is one real result from that market. A software development company in Germany got 488 sales calls in 6 months. Its connection rate was 61.9% (52 of 84 requests accepted), and 76.9% of those connections replied (40 of 52). Results differ by company. Treat this as a single data point and never as a forecast.

    Opt-outs and exclusion lists carry across channels, so a person who asked us to stop in one place is excluded everywhere.

    There, LinkedIn is the channel we lean on instead of cold email. That is a house rule and gives no legal safe harbor. Every LinkedIn message still has to fit the person's job and be easy to decline.

    What I wrote above on the UWG comes from the statute text. That is the short version of what German law allows in B2B cold email.

    What should you change before your next send?

    Sort your list this week. Add two columns: country and subscriber type. Sort by them. Every record in a "yes" row without consent moves to LinkedIn before your next send.

    The worst mistake is emailing a record in a "yes" row because the legitimate interest check passed. A passed check does not change the row. Then make sure your first email carries a privacy line like the one in the sample above. Sort first. Then send.

    If you are planning the wider pipeline around these rules, place prospecting inside the full process of the sales lead generation process.

    Checking your outreach against GDPR and the local email law? Book a call and describe your process. I will tell you which step I would look at first.

    FAQ: what else do sales teams ask about GDPR prospecting?

    What are the 7 GDPR requirements?

    They are broad principles rather than seven forms. Article 5(1) lists six: lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; and integrity and confidentiality. Article 5(2) adds accountability. In the workflow above, purpose limitation, data minimisation and storage limitation are steps 1, 2 and 6, and the dated check in your campaign file is your accountability record.

    If a prospect's details are public on LinkedIn, can you use them freely?

    No. According to the ICO, you cannot assume people agree to direct marketing just because their personal data is in the public domain. It adds that people often use professional networking sites for their own career, and a message to someone acting in that personal capacity is not B2B marketing. Public data still needs a lawful basis and a pass under the email rule.

    Does buying data from a provider make the provider responsible?

    No. The provider answers for how it collected and sold the data. The GDPR puts the duty to demonstrate compliance for your campaign on the controller, the business that decides why and how personal data is used. When you choose who to contact and for which offer, that business is you. Ask the provider where each record came from, and file the answer.

    Does the soft opt-in cover people who downloaded a guide from your site?

    The ePrivacy Directive ties the exception to contact details obtained "in the context of the sale of a product or a service". A free download with no purchase is hard to fit into that wording. In any market with a consent rule, treat download leads as needing consent unless your counsel reads your situation differently.

    Is calling UK businesses a safer route than email?

    It runs on different rules. Under the ICO's B2B marketing guidance, live B2B calls must be checked against the TPS and CTPS registers and your own do-not-call list. Automated calls need consent. My team does not do cold calling or run dialing floors. If a client wants phone in the plan, the only version we add is warm calls to people who already replied, engaged or opted in.

    Want to see what we would build for your company?

    I am Artem Smirnov. I help established B2B companies build and run the go-to-market system behind their pipeline, from outbound to AI search visibility. Book a call and we will see what fits yours.

    Artem Smirnov
    Artem Smirnov

    I help established B2B companies build and run their go-to-market systems. 9 years in outbound, 10,000+ campaigns.