GDPR explained in short: the General Data Protection Regulation is the EU law that sets the rules for how organisations collect, use and protect personal data, and the rights people hold over it.
It sits at the centre of modern data privacy, and this guide describes it from the official text.
What the GDPR is and when it applies
The regulation was adopted in Brussels as a law that is binding in its entirety and directly applicable in all Member States. According to the official text on EUR-Lex, it applies from 25 May 2018. It replaced an older directive, so organisations across the Union now follow one common rulebook rather than a patchwork of national laws.
As of the date shown on its EUR-Lex record, the regulation is in force, the record notes that the act has been changed, and its current consolidated version is dated 4 May 2016. This guide describes that text and the Commission explainer, so readers should check EUR-Lex for any later consolidated version.
The territorial reach is wide. The text covers processing carried out in the context of the activities of an establishment of a controller or processor in the Union, wherever the processing physically happens. It also covers organisations outside the Union when they offer goods or services to people who are in the Union, or monitor their behaviour there, and this applies whether or not a payment is required.
This article describes the regulation for general information and does not give legal advice. Readers who need to apply it to a real project should check the current law and consult a qualified lawyer.
Key terms: personal data, controllers and processors
The vocabulary matters because every duty attaches to a defined role. The European Commission’s data protection explainer says personal data is any information that relates to an identified or identifiable living individual, and that data which has been pseudonymised but can still be used to re-identify a person remains personal data. Typical examples include a name, a home address, an email address, an IP address and a cookie identifier.
- Data subject: the person the information relates to.
- Controller: the body that, alone or jointly with others, determines the purposes and means of the processing of personal data.
- Processor: a body that processes personal data on behalf of the controller, such as a hosting or analytics provider.
- Processing: any operation performed on personal data, including collection, storage, retrieval, sharing, restriction and erasure.
Because the definition of processing includes simply storing data, almost every digital service that holds user details is processing personal data in the legal sense.
The principles behind every rule
The regulation’s article on principles sets the foundation that the other provisions build on. Per the same official text, personal data must be:
- processed lawfully, fairly and in a transparent manner;
- collected for specified, explicit and legitimate purposes and not used in ways incompatible with them (purpose limitation);
- adequate, relevant and limited to what is necessary (data minimisation);
- accurate and kept up to date where necessary;
- kept in a form that identifies people for no longer than needed (storage limitation);
- protected by appropriate security (integrity and confidentiality).
The same article adds accountability: the controller is responsible for, and must be able to demonstrate, compliance with all of these. Teams that want a practical treatment of one of them can read the wider discussion in the data privacy hub, and the idea of collecting only what is needed is the starting point for most design decisions.

Lawful bases and special categories of data
Processing is lawful only when at least one listed legal ground applies. The grounds in the official text include the person’s consent, the need to perform a contract, compliance with a legal obligation, protection of vital interests, a task carried out in the public interest, and the legitimate interests of the controller or a third party, provided those interests are not overridden by the rights of the individual.
Consent has a strict definition in the text: any freely given, specific, informed and unambiguous indication of the person’s wishes, given by a statement or a clear affirmative action. Pre-ticked boxes and silence therefore do not fit the definition.
Stronger protection applies to special categories of data. The regulation’s article on these categories says processing data that reveals racial or ethnic origin, political opinions, religious or philosophical beliefs or trade union membership is prohibited by default, as is processing genetic data, biometric data used to identify a person uniquely, health data, and data about sex life or sexual orientation. The text then lists narrow exceptions, so organisations handling such data face a higher bar.
The rights people can exercise
Chapter three of the regulation gives individuals a set of rights over their data. In plain terms, the main rights include:
| Right | What it means in the official text |
|---|---|
| Access | Obtain confirmation of whether data is being processed and get access to it, with information on purposes, categories and recipients. |
| Rectification | Have inaccurate personal data corrected without undue delay, and incomplete data completed. |
| Erasure | The “right to be forgotten”: deletion without undue delay where grounds such as the data no longer being necessary apply. |
| Restriction | Limit processing in listed cases, for example while the accuracy of the data is contested. |
| Portability | Receive data you provided in a structured, commonly used, machine-readable format and transmit it to another controller. |
| Objection | Object, on grounds relating to a particular situation, to processing based on public interest or legitimate interests, including profiling. |
The table summarises the rights as worded in the regulation on EUR-Lex and the European Commission’s explainer.
These rights are not unlimited. The text attaches conditions and exceptions to each of them, and controllers must handle requests without undue delay. Anyone planning to rely on a right in a dispute should read the exact article and take advice.
Duties for organisations
Beyond respecting individual rights, the regulation places operational duties on controllers and processors. The most visible ones in the official text are these.
- Data protection by design and by default: technical and organisational measures must be built in when the means of processing are chosen and during the processing itself.
- Records of processing: controllers must maintain a record of processing activities, including purposes and categories of data.
- Data protection officers: a designated officer is required where processing is done by a public authority, or where core activities involve regular and systematic monitoring of people on a large scale or large-scale processing of special categories.
- Breach notification: according to the regulation’s text, a controller must notify the competent supervisory authority of a personal data breach without undue delay and, where feasible, not later than 72 hours after becoming aware of it, unless the breach is unlikely to result in a risk to people’s rights and freedoms.
Publicly funded and civic projects are not exempt. A city dataset or a community app built on resident information raises the same questions, and the discussion of contact tracing app privacy shows how these principles were tested during the pandemic.
Enforcement and how it compares elsewhere
Independent supervisory authorities in each Member State monitor and enforce the regulation, and the European Data Protection Board coordinates consistent application. The text requires fines to be effective, proportionate and dissuasive. For the most serious infringements, the upper limit is twenty million euros or, for a company, four percent of total worldwide annual turnover of the preceding financial year, whichever is higher, as stated in the official regulation. A lower tier applies to other listed obligations, such as those on controllers and processors.
Outside Europe the picture differs. The United States has no single national equivalent, and states have passed their own statutes; the overview of US state privacy laws explains how they compare in approach and scope.
Frequently asked questions
Does the GDPR apply to organisations outside the EU?
It can. The official text extends to organisations outside the Union that offer goods or services to people in the Union, or monitor their behaviour there, whether or not payment is involved.
Is a pseudonymised record still personal data?
Yes, where it can be used to re-identify a person. The European Commission explainer states that pseudonymised data of this kind remains personal data and stays within the scope of the regulation.
How quickly must a breach be reported?
The official text says a controller must notify the supervisory authority without undue delay and, where feasible, within seventy-two hours of becoming aware, unless the breach is unlikely to risk people’s rights and freedoms.
Does the regulation ban collecting data altogether?
No. It regulates how data is processed and requires a lawful ground, defined purposes and safeguards. Processing that meets those conditions is permitted.
Is this guide legal advice?
No. It is a general description of the official text. Current law and individual circumstances differ, so readers should check the current regulation or consult a qualified lawyer.
