EU outbound and GDPR: what SDR operations has to handle
What B2B outbound requires under GDPR — lawful basis, objections, retention, call recording, data residency — and the controls that make it routine.
Not legal advice. This describes operational controls, not a legal position. GDPR interacts with national implementing law and sector rules, and the detail differs by member state. Take advice for your own jurisdictions and market.
Outbound prospecting in the EU is lawful and routine, but it is not unregulated. Most of the obligations land on operations rather than legal, because they are about what your system does by default, every day.
B2B contact data is personal data
A named individual at a company — their work email, direct line, job title — is personal data about an identifiable person. GDPR applies. What B2B context changes is which lawful basis is realistically available, and how data subject rights get exercised in practice.
Lawful basis: usually legitimate interests
Most cold B2B prospecting in the EU runs on legitimate interests rather than consent. That basis is conditional: you must have weighed your interest against the individual’s rights, be able to show your reasoning, and stop where their interests outweigh yours.
- Document the assessment. A written legitimate-interests assessment is a defence. A belief is not.
- Relevance is part of the basis. Contacting someone whose role has nothing to do with what you sell weakens the argument. Targeting quality is a compliance input.
- Channel rules differ. Electronic marketing, automated calling and SMS also fall under ePrivacy and national rules. Some countries run national opt-out registers for telephone marketing that you must screen against.
Objections must stop all contact
An objection to direct marketing is absolute — there is no balancing test. Once made, you stop.
The familiar failure: someone says “take me off your list”, a rep notes it in a CRM field, the list is re-imported from the original source three months later, and the same person gets called again. That second call is the breach, and the cause is architectural, not individual.
Objection as a note
- Written in a field on the current list row
- Rep is expected to check before calling
- One global list shared across clients
- A fresh CSV import overwrites it
Objection as a suppression
- Stored against the person, not the row
- Filtered out at import, before a rep sees the lead
- Kept per client, as each list is its own processing context
- Survives every re-import
Retention runs on a schedule
Personal data may not be kept longer than necessary. “Necessary” is yours to define, but it must be defined, documented and applied: a written retention period per data category — prospect records, activity history, call recordings, transcripts — enforced by an automated process. A policy nobody implemented is an aggravating factor, not a defence.
Suppression records are a deliberate exception: you need to keep enough to keep honouring an objection, which justifies holding a minimal record indefinitely.
Erasure has to reach everywhere the data went
In an SDR operation a deletion request touches more places than people expect:
Where one prospect's data ends up
- 1
Prospect record
The lead and its company, on every list it was imported into.
- 2
Activity and calls
The timeline, call recordings and transcripts.
- 3
Pushed systems
Client CRMs the booking was synced to, and calendar entries.
- 4
What stays
The minimal suppression record and aggregates that no longer identify anyone.
Write the data map down before the first request arrives, and be ready to explain calmly what you are not deleting and why. That is most of handling a request well.
Call recording adds its own rules
You need a basis for the recording itself, you must tell people it is happening, and some jurisdictions require consent from all parties. Rules differ by country, so a multi-country operation cannot assume one policy covers it.
Treat recordings as high-sensitivity data: tighter access, a shorter retention period than ordinary activity, and automated deletion. Transcripts are personal data too.
Data residency
Transfers outside the EEA are permitted with safeguards, but keeping processing inside the EU removes a category of question — and it is often a procurement requirement regardless.
For reference, Dialbrew runs in AWS eu-central-1 (Frankfurt), with product analytics on EU cloud and anonymous profiling disabled, and error monitoring in the EU region. Retention and right-to-be-forgotten procedures are documented alongside the implementation. We do not hold a SOC 2 or ISO 27001 certification and will not imply otherwise.
The operational checklist
| Obligation | What has to be true in the system |
|---|---|
| Lawful basis | A documented legitimate-interests assessment; targeting relevant to what you sell |
| National channel rules | Screening against applicable opt-out registers per country |
| Objections | Captured against the person and enforced at import, surviving re-import |
| Retention | Defined per data category and applied automatically |
| Erasure | A known data map covering CRM pushes, recordings and transcripts |
| Call recording | Notification, a lawful basis, country-aware policy, short retention |
| Access control | Reps see only the clients they are rostered on, by permission |
| Processor terms | A DPA with every sub-processor in the chain |
Make the compliant path the default
None of this requires heroics. It requires that the default path through your system is the compliant one — suppression enforced before a rep sees a record, retention running on a schedule, access scoped by permission. Compliance that depends on people remembering fails on a busy Thursday.