Definition
The GDPR is an EU regulation, published on EUR-Lex and listed in this page's sources. It applies to the processing of Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier., a term it defines broadly as any information relating to an identified or identifiable person, and "processing" covers almost anything done with that data: collecting, recording, storing, using, sharing, combining and deleting. The organisation that decides why and how data is processed is the controller and carries the main responsibility; a supplier processing data on its behalf is a processor.
It is a framework of principles and duties rather than a list of permitted marketing tactics. That is why the site's guides describe what the regulation requires and then leave decisions about a specific business to whoever owns data protection there.
In practice: the four parts marketers meet
Principles. Personal data must be processed lawfully, fairly and transparently; collected for specified purposes and not further processed in incompatible ways (purpose limitation); adequate, relevant and limited to what the purpose needs (data minimisation); accurate; kept in identifiable form no longer than necessary (storage limitation); and kept secure. The controller must be able to show that it complies.
Lawful bases. Every processing purpose needs one of the grounds the regulation lists, chosen before the processing starts. Consent is one of them, and the regulation describes it as freely given, specific, informed and unambiguous.
Rights. People have rights over their data, including to be informed, to access it, to have it corrected or erased in defined circumstances, and to object. The right to object to processing for direct marketing is absolute: once someone objects, their data is no longer processed for that purpose.
Breach duties. A breach of security leading to accidental or unlawful disclosure, loss or alteration of personal data is a personal data breach, and the regulation sets duties to assess it, notify the supervisory authority unless the risk to people is unlikely, tell those affected where the risk to them is high, and document it. The guide to handling an AI mistake shows why data protection hears first when an AI output exposes customer details.
Where the GDPR meets marketing lists, tracking and AI
The principles turn into working rules in specific places. The guide to keeping personal data out of analytics applies minimisation and storage limitation to reporting tools that quietly collect email addresses. The routine for minimising data before prompting applies the same principles before material reaches an AI tool. The playbook for customer lists across ad platforms treats each upload as a use of personal data that the business decides on before it becomes an ad setting, and the guide to personalising email content uses purpose limitation to rule out repurposing data in ways a subscriber would not expect.
The GDPR does not settle everything on its own. Whether a marketing email or text may be sent is governed by separate electronic marketing rules that apply alongside it; the ICO's direct marketing guidance explains how UK data protection and electronic marketing rules apply to marketing, and other markets have their own regimes.
A language school checks its lists before an ad platform upload
Quindlemoss Language Courses plans to upload its enquiry lists to two ad platforms to exclude existing students and build audiences. It holds three lists: 2,300 people who requested a brochure, 1,150 who signed up for "course start dates only", and 4,800 past students. Before uploading, the marketing lead checks each list against what people were told when they gave their details. The brochure form's notice mentioned advertising use, and the student enrolment terms did too; the course-dates sign-up promised only date announcements, so those 1,150 people are left out of the upload. The school's data protection lead records the decision, the purpose and the lawful basis relied on for each list before anything is sent.
Related terms
Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier. is the regulation's subject, and its broad definition decides when the rules apply. A Lawful BasisOne of the six grounds the GDPR accepts for processing personal data, such as consent, contract or legitimate interests, chosen for each purpose. is required for each purpose, chosen in advance. A CMPSoftware that collects, stores and passes on visitors' consent choices for cookies and tracking. records the choices visitors make about tracking, which is one place where consent is collected and evidenced. Double Opt-InA sign-up process in which the subscriber confirms through a link sent to the address given. is a sign-up practice that creates a clear record that a person asked to join a list, which helps a business show what it can rely on.
Common confusions
- The GDPR is a consent law. Consent is one lawful basis among several; the principles and rights apply whichever basis is used.
- The GDPR decides when marketing emails may be sent. Electronic marketing rules sit alongside it and set their own consent and opt-out requirements.
- Hashing or pseudonymising takes data outside the regulation. Pseudonymised data is still personal data; only data that can no longer be linked to a person falls outside it.
- A vendor's compliance covers the business. The controller decides what data is sent and why, and stays responsible for that decision whatever the vendor's terms say.
- A privacy notice settles everything. Telling people about a use does not make an incompatible or excessive use acceptable.
