B2B Prospecting and GDPR: Where Contacts Can Come From
Under B2B prospecting GDPR rules, a named contact can go into your CRM when you have a lawful basis (usually legitimate interests), can show where the data came from, inform the person within the Article 14 deadlines and stop at their first objection. That’s the short version. Now picture the founder of a six-person EU services firm in November 2026, putting together a list of 300 target companies for 2027. Company details on their own? Few questions there. The regulation protects people, not legal entities. Below I go through what the regulation actually says and what you should write down. It is not legal advice.
Table of Contents
Does GDPR apply to a B2B prospect list?
Yes. As soon as the list holds names, named work emails or direct phone numbers of individuals, you’re in GDPR territory. According to recital 14 of the General Data Protection Regulation, processing that concerns legal persons, including their name, legal form and contact details, falls outside its scope. So a generic info@ address carries less risk than jan.kowalski@. What I’d do in practice: split the sheet into company-level rows (name, sector, website) and person-level rows for decision makers. Only that second group needs the safeguards below.
Legitimate interest in B2B sales: the legal basis most prospect lists rely on
Article 6(1)(f) allows processing for legitimate interests, but only after you weigh your interest against the person’s rights and freedoms. Recital 47 adds that direct marketing may be regarded as a legitimate interest. May. It’s possible, never automatic. The EDPB Guidelines 1/2024 on legitimate interest lay out a three-step test: a real interest, necessity of the processing and a balancing exercise. And reasonable expectations count for a lot here. A head of procurement contacted about a relevant service expects that kind of email. Someone you dug up on an unrelated forum? Much less so. My advice: write the test down once for the whole campaign and keep it next to the list.
Where can contacts on a B2B prospect list come from?
When you build a B2B prospect list, sources differ in risk mostly on two things: can you prove where each contact came from, and what did the person know? Read the notes below as practical guidance, not legal certainty:
- Your own channels: people who sent enquiries from website forms started the conversation themselves, so the source is obvious and expectations are high.
- Events: business cards picked up at a stand prove a direct exchange; log trade show leads in the CRM with the event name and date.
- Public company registers and company websites: generic addresses are low risk, but named staff addresses still need the balancing test and a notice.
- Referrals: an introduction from a client or partner is a traceable source; just note who made it.
Bought lists are the risky exception. Usually you can’t show where the data originated or what the person was told. Skip them. Or, if you really must, get the seller’s source and the notice the person received in writing before importing a single row.
Article 14 GDPR prospecting: telling people where you got their data
If the data didn’t come from the person directly, Article 14 says you have to inform them, and that includes the source. The text of Article 14 GDPR puts the deadline at the first communication if you use the data to contact them; otherwise within a reasonable period, one month at the latest. In practice it’s easy. The first outreach message carries a short notice: who you are, the purpose, where you found the details, the legal basis, the right to object and a link to your privacy notice. Then record the date it went out. Don’t skip that bit.
GDPR cold outreach in B2B: email rules and the right to object
Here’s the part people miss. GDPR is only half the picture, because unsolicited marketing email falls under Article 13 of the ePrivacy Directive 2002/58/EC and the national laws implementing it. Those rules vary between member states, especially for legal persons and work addresses, so check the law of the recipient’s country (in Poland that’s the Electronic Communications Law). Don’t assume B2B cold email is fine everywhere. It isn’t. On top of that, Article 21(2) and (3) give an absolute right to object to direct marketing, and once someone objects, the data can no longer be processed for that purpose. Keep an objection flag on the record so nobody on your team emails that person again.
What to record for each prospect in the CRM
Every contact needs a short trail that answers two questions: where did the data come from, and why do you still hold it? A workable prospect data source CRM record includes:
- Data source (form, event, register, referral).
- Date obtained.
- Legal basis, with a reference to your written balancing test.
- Date of the Article 14 notice.
- Objection or opt-out status.
- Review or deletion date if no relationship develops.
In EpicCRM, website form leads land in the lead inbox, lists come in via CSV or XLSX import, and custom tags plus the relationship history on the contact card can hold the source and key dates. Same fields, same habits, and they also back up your wider approach to storing customer data under GDPR.
Keeping the list clean through 2027
A prospect list stays defensible only if you review it on a fixed schedule and delete what went nowhere. Recital 39 asks the controller to set time limits for erasure or periodic review. For a small team, a quarterly pass over contacts past their review date does the job: delete or anonymise inactive records and note what you removed. Then there are access requests. When someone asks what you hold, you have to find every copy of that person (spreadsheets on someone’s laptop included), and that’s where a routine for handling GDPR requests in a CRM pays off. On the processor side, EpicCRM offers data export, EU servers and a data processing agreement.
So, B2B prospecting GDPR compliance boils down to four habits. A clear source for every name. A written balancing test. A timely notice. And objections respected for good.
FAQ
Can I add contacts from LinkedIn or a company website to my CRM?
Possibly, under legitimate interests, once you’ve done and recorded the balancing test. After that you owe the person an Article 14 notice, at the latest with your first message. Generic company addresses carry less risk than named personal ones.
Do I need consent to email B2B prospects?
GDPR may let you rely on legitimate interests to hold the data. But whether you can send marketing email without consent is a question for national ePrivacy laws, and those differ by country, particularly for work addresses. Check the rules of the recipient’s country before the first send.
How long can I keep a prospect who never replied?
GDPR doesn’t set a fixed period here. Pick your own review or deletion date, record it on each contact and actually act on it. If nothing has developed by then, delete or anonymise the record.



