Key points
- Separate permission to process data from permission to send marketing.
- Check subscriber type, jurisdiction and channel before campaign approval.
- Record vendor roles, provenance and a workflow for handling objections.
B2B contact data can identify an individual even when it describes their work. A defensible outbound process checks the applicable privacy law, the rules for the communication channel, the data source and the recipient's preferences before activating a list. Buying data does not settle those questions.
This guide separates GDPR data processing, UK electronic marketing, California privacy rights and US commercial email requirements. Use it to define an operational review with your privacy owner for each market and channel, rather than treating “B2B” as a universal exemption.
Start with the person, purpose and jurisdiction
A named work email, job title linked to a person, or individual phone number may be personal data. A company name alone is a different case. Record which information you hold, why you need it, where the people and relevant organisations are based, and how you plan to contact them.
GDPR territorial scope depends on the circumstances, including an EU establishment or relevant offering of goods or services to people in the EU or monitoring of their behaviour. It is not determined solely by citizenship or the location of a spreadsheet. The European Commission's scope guidance explains these starting points.
Separate permission to process from permission to send
A lawful basis for holding or analysing personal data does not automatically authorise email, SMS or telephone marketing. Channel-specific rules may impose additional conditions. For EU campaigns, check the applicable national electronic marketing rules alongside GDPR; do not assume one cold-email rule covers every member state.
When considering legitimate interests, document the purpose, whether processing is necessary, and the balance against the person's rights and reasonable expectations. Relevance is useful evidence, but a matching job title does not by itself complete that assessment. The Commission's guidance on legal grounds describes the available bases and transparency requirements.
UK B2B email: identify the subscriber type
The ICO distinguishes corporate subscribers, such as limited companies, from individual subscribers, which include sole traders and some partnerships. Under its current B2B marketing guidance, the PECR consent rule for electronic mail does not apply to corporate subscribers. Named business contact data can still fall under UK GDPR.
For individual subscribers, consent or an applicable soft opt-in is generally required. An address appearing on a website does not create consent. When the recipient type is uncertain, resolve it before sending. Identify the sender and provide an effective way to stop marketing. The ICO flags this guidance as under review following legislative changes, so consult its current text when approving a campaign.
California: the old B2B exemption has expired
The California Attorney General states that the former exemptions for employment information and B2B transactions expired on December 31, 2022. CCPA applicability also depends on the business and statutory criteria; contacting a California resident is not, by itself, a complete scope analysis. See the Attorney General's CCPA guidance.
Where the law applies, map relevant notice, access, deletion, correction and sale or sharing opt-out obligations into the workflow. Do not label every transfer to a CRM a statutory “sale” or “sharing”: assess the relationship, purpose and contractual conditions. Keep a documented route for handling requests across vendors and downstream systems.
US commercial email: apply CAN-SPAM requirements
The FTC's CAN-SPAM guide applies to commercial email, including B2B messages. Use accurate sender information and subject lines, identify commercial messages as required, include a valid physical postal address, and provide a clear opt-out method.
The FTC requires opt-out requests to be honoured within 10 business days and the mechanism to remain available for at least 30 days after sending. A faster internal suppression process can help prevent accidental resends. Hiring an agency or email platform does not remove the promoted business's responsibility to monitor what is sent on its behalf.
Determine vendor roles from what actually happens
A data provider is not automatically your processor. A controller decides the purposes and means of processing; a processor acts on a controller's behalf. A provider maintaining a database for its own purposes may have a different role from a service processing your uploaded file under instructions. The Irish Data Protection Commission explains this distinction.
Ask what each party collects, determines, discloses and retains. Check provenance, permitted uses, contracts, security arrangements, deletion handling and international transfers. A contract label or a “compliant data” badge is not a substitute for that assessment.
Build a campaign approval record
| Checkpoint | Evidence to retain | Operational owner |
|---|---|---|
| Market and channel | Target locations, subscriber types and approved communication methods | Campaign owner and privacy reviewer |
| Source and purpose | Source, collection context, permitted use and business purpose | Data owner |
| Lawful processing | Applicable legal basis and assessment, where required | Privacy reviewer |
| Notice and preferences | Privacy information, consent evidence where needed, suppression checks | Marketing operations |
| Activation and retention | Approved fields, destination, access controls and review or deletion date | Operations owner |
Separate regional or channel cohorts when their conditions differ. Apply suppression before retrieval, import and sending wherever the workflow permits. Keep only fields needed for the approved purpose and record the list version used for each campaign.

Use the lead-generation privacy workflow to connect the approval record to day-to-day operations. For a technical implementation, compliance documentation for SaaS lists focuses on the evidence that should travel with the workflow.
Make objections propagate across the workflow
The right to object to processing for direct marketing requires the marketing processing to stop. It is not an invitation to re-run a balancing test to continue the campaign. The EDPB's rights guidance explains this distinction.
Assign an owner to receive requests and update connected systems. Avoid simply deleting an address from one list if the next import can add it again. Design any limited suppression record with your privacy owner so future campaigns respect the request without retaining unnecessary data.
Check data quality without calling it legal permission
A populated email field does not prove current deliverability, consent or a lawful marketing purpose. Email verification also does not establish that outreach is permitted. Review contact identity, current company and field quality separately from the legal and preference checks.
Use the B2B data quality checklist for source and field evaluation, and the pre-export hygiene checklist for operational checks. If you use Dievio, validate the audience with a count preview, then review returned records within your approved process.
A healthcare audience requires careful separation of business contact research and patient information. The healthcare prospecting guide addresses that scope; healthtech list planning helps identify the actual business buyer.



