Under GDPR a lead generation agency is a processor when it contacts people on a client's instructions with the client's purposes, and a controller when it decides for itself whom to contact and why. The role decides who needs the Article 28 contract, who needs the lawful basis under Article 6, and who owes each recipient a privacy notice under Article 14. A business email address that names a person is personal data either way.

This page is a plain-language map of the articles an agency meets in practice, each tied to its source and read on 15 November 2026; the GDPR quotes are from the official text of Regulation (EU) 2016/679 on EUR-Lex. It is not legal advice, and email rules sit under a second law as well, the ePrivacy rules each country passes, which can be stricter than GDPR. For the cross-country basics see whether cold email is legal. For how agencies structure the work itself see agencies running acquisition for clients. The UK has its own version of these laws, UK GDPR and PECR. Where this page cites the ICO, that is the UK regulator, and the article numbers it explains match those quoted here.

Business emails are personal data

GDPR Article 4(1) defines personal data as "any information relating to an identified or identifiable natural person". The UK regulator, the ICO, says that if you can identify a person, the data is personal data even in a business setting: "it will constitute personal data even if they are acting in their business capacity" (ICO, business-to-business marketing, read 15 November 2026). A generic address like a department mailbox that names no one is not personal data, but a named director's work address is. A B2B campaign that lists names, titles and emails is therefore a processing activity under GDPR, whoever it is for.

Processor or controller: who decides

Article 4(7) says a controller is the body which "determines the purposes and means of the processing of personal data". Article 4(8) says a processor is one that "processes personal data on behalf of the controller". Article 28(10) adds the point that bites agencies: a processor that infringes the Regulation "by determining the purposes and means of processing" shall "be considered to be a controller in respect of that processing." The ICO puts it the same way and adds that such a processor "will have the same liability as a controller" (ICO, what are controllers and processors, read 15 November 2026). What you actually do decides the role, not the heading in your contract.

What the agency does Likely role What follows
Sends a client's own approved list, from the client's domain, to the client's instructions Processor (Art. 4(8)) Art. 28 contract; the client holds the Art. 6 basis and the notice
Builds a contact database for itself and sells access to several clients Controller for that database (Art. 4(7)) Its own Art. 6 basis, Art. 14 notice and objection handling
Takes a client's brief, then picks who to contact and keeps the data for its own other work Controller for the part beyond instructions Same liability as a controller (ICO)

Take an invented agency, Agency A in Copenhagen, with three clients. For client 1 it sends mail to the client's own prospect list: processor. For client 2 it researches 400 procurement managers from public company pages on the client's brief and discards the file when the project ends: still processor if the client sets the purpose and criteria. For client 3 it keeps every researched contact in a shared sheet to reuse for the next client. That last habit makes Agency A a controller of the sheet, with its own duties, and a client that expected its data to be kept private has a contract problem too.

The lawful basis: legitimate interests

Article 6(1) says processing is lawful "only if and to the extent that at least one of the following applies". For B2B outreach the ICO says the two most relevant bases are consent and legitimate interests, and that where consent is required by another rule, that consent is usually the appropriate basis (ICO, business-to-business marketing). Article 6(1)(f) allows processing "necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject". Recital 47 says "The processing of personal data for direct marketing purposes may be regarded as carried out for a legitimate interest", and "may" is the operative word. The ICO says there is "no absolute rule" and tells you to apply a three-part test: identify the interest, show the processing is necessary for it, and balance it against the person's interests. Write the test down for each campaign, because the written test is what you can show a regulator.

Tell people where you got their data

If you did not collect the data from the person, Article 14(1) requires the controller to provide the controller's identity and contact details, the purposes and legal basis, and the categories of data. Article 14(2)(f) adds the source: "from which source the personal data originate, and if applicable, whether it came from publicly accessible sources". On timing, Article 14(3) says within a reasonable period and "at the latest within one month", or "at the latest at the time of the first communication" if the data is used to communicate with the person. For cold email, the simplest way to meet that is for the first message to carry the notice or link to it. There is an exception in Article 14(5)(b) for where providing the information "proves impossible or would involve a disproportionate effort", and it comes with safeguards, so it should not be assumed for an email you are about to send to a named person.

Objections must be honoured

Article 21(2) gives the person "the right to object at any time" to processing for direct marketing, and Article 21(3) says that once they object, "the personal data shall no longer be processed for such purposes". Article 21(4) requires that the right be brought to their attention "at the latest at the time of the first communication", clearly and separately from other information. The ICO says "This right is absolute and there are no grounds for you to refuse," and recommends a suppression list rather than deleting every record, so that new lists can be screened against it and the person is not contacted again. An agency running several clients should keep one suppression list that every client's campaigns check, and say so in the contract.

The Article 28 contract

Where you are a processor, Article 28(1) says the controller "shall use only processors providing sufficient guarantees", and 28(3) says the processing "shall be governed by a contract or other legal act". The contract must cover, among other things, processing only on documented instructions (28(3)(a)), confidentiality (b), security (c), conditions for engaging other processors (d), help with data subject requests (e), deletion or return at the end (g) and audits (h). Article 28(2) says you cannot engage another processor without the controller's prior specific or general written authorisation. If your sending, data or hosting suppliers touch client data, they are sub-processors, and the client should have agreed to them in writing. Keep a list.

Email rules are a second layer

Whether you may send the email at all is decided by the ePrivacy Directive, as each country passes it. Article 13(1) allows direct marketing email "only in respect of subscribers or users who have given their prior consent". Article 13(5) applies that to subscribers who are natural persons, and says Member States must ensure the legitimate interests of other subscribers, such as companies, are "sufficiently protected" (Directive 2002/58/EC, consolidated version, read 15 November 2026). So the rule for company addresses is left to each country. Germany's Act Against Unfair Competition, section 7(2) no. 2, treats advertising using "electronic mail" without the addressee's prior express consent as an unacceptable nuisance (UWG, English translation on gesetze-im-internet.de including the amendments by the Act of 12 February 2026, read 15 November 2026). The line just above it, no. 1, splits telephone advertising between consumers and other market participants; no. 2 makes no such split, so on the text a business recipient needs the same prior express consent, subject only to the existing-customer exception in section 7(3). Check the country of the recipient, with local counsel, before a campaign there.

The penalty side

Article 83(5) sets fines of up to 20,000,000 euros or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher, for infringing Articles 5, 6, 7 and 9 and the data subject rights in Articles 12 to 22. Article 83(4) sets up to 10,000,000 euros or 2% for obligations including Article 28. Those are ceilings, not predictions.

A short checklist

  • Decide the role for each service and write it into the contract.
  • Keep a written legitimate interests test per campaign.
  • Put the source and your identity in the first message or its linked notice.
  • Run one suppression list across clients and honour objections.
  • List sub-processors and get written authorisation.
  • Check the recipient country's ePrivacy law before the first send.

If you run outreach for your own agency, Rocketship finds business buyers, emails them from your own Gmail, follows up, answers replies and books the meeting. Mission Control is built for teams running outreach at volume, at $1,499 a month, and the cheapest plan starts at $12 a month, 7-day trial, card required (see pricing). You supply the offer and the answers to booked meetings, and whether a campaign is lawful in the recipient's country stays your decision.