- Accountability means evidence: for each core obligation, keep the document an authority or customer is likely to ask for, such as the record of processing, DPIAs, processor contracts and a breach log.
- The Article 30 exemption for organisations with fewer than 250 employees is narrow. Routine processing such as payroll, customer and supplier records usually still needs a record.
- Reportable breaches go to the supervisory authority without undue delay and, where feasible, within 72 hours. Every breach must be logged, including those you do not report.
- The UK has an EU adequacy decision valid until 27 December 2031, and Brazil has one since January 2026, so transfers from the EU to either need no standard contractual clauses.
- Rights requests must be answered within one month, extendable by two further months where necessary.
This page covers the day-to-day obligations: the evidence matrix, records of processing, breaches, DPOs, international transfers and data subject rights. For who the GDPR applies to, the lawful bases, the fine structure and a checklist to get your programme in order, see our GDPR compliance guide.
Core obligations and the evidence behind them
GDPR compliance is broader than a register and a breach procedure. The accountability principle in Article 5(2), backed by Article 24, requires controllers to be able to demonstrate compliance, which in practice means evidence. The table maps the main areas to their provisions, the documents an authority or customer is likely to ask for, and whether the obligation applies to every controller or is triggered by specific processing.
| Area | Primary provision | Practical evidence | When it applies |
|---|---|---|---|
| Accountability | Arts 5, 24 | Data protection policies, assigned responsibilities, management review records | Always |
| Lawful processing | Arts 6, 9, 10 | Lawful basis per activity, legitimate interests assessments, consent records, Article 9 conditions | Always; Articles 9 and 10 when special category or criminal offence data is processed |
| Transparency | Arts 12 to 14 | Privacy notices at the point of collection, version history | Always |
| Records of processing | Art 30 | Controller and processor records of processing activities | Almost always; the under-250 exemption is narrow |
| Security | Art 32 | Risk assessment, technical and organisational measures, access reviews, test results | Always |
| Privacy by design and default | Art 25 | Design reviews, default settings, data minimisation decisions | Always, from the design stage |
| Retention and deletion | Art 5(1)(e) | Retention schedule, deletion or anonymisation records | Always |
| Processor governance | Art 28 | Processor contracts, due diligence, sub-processor lists, audit evidence | When a processor acts on your behalf |
| Impact assessments | Arts 35, 36 | DPIA screening records, DPIAs, prior consultation where needed | When processing is likely to result in a high risk |
| Incident handling | Arts 33, 34 | Breach procedure, breach log including unreported breaches, notifications | Log always; notification depends on risk |
| Individual rights | Arts 12 to 22 | Request procedure, request log, identity checks, response templates | Always |
| International transfers | Chapter V (Arts 44 to 49) | Transfer inventory, adequacy checks, SCCs and transfer assessments | When personal data leaves the EEA |
| DPO | Arts 37 to 39 | Appointment record, published contact details, reports to management | When Article 37 criteria are met, or a DPO is appointed voluntarily |
Records of processing activities
Article 30 requires controllers to keep a record of processing activities (RoPA) covering, among other things, the purposes, the categories of individuals and data, recipients, transfers outside the EEA, retention periods where possible and a general description of security measures. Processors keep their own, shorter record of the processing they carry out for each controller.
The Article 30(5) exemption for organisations with fewer than 250 employees is narrower than it looks. It does not apply where the processing is likely to result in a risk to individuals, is not occasional, or includes special category or criminal offence data. Payroll, customer management and supplier administration are routine rather than occasional, so most small organisations need a record for at least those activities. Supervisory authorities can ask to see the record under Article 30(4), and it is the baseline for the rest of the programme.
Security, privacy by design and retention
Article 32 requires security appropriate to the risk, taking into account the state of the art, implementation costs and the nature of the processing. It names measures such as pseudonymisation and encryption, ongoing confidentiality and resilience, the ability to restore access after an incident, and regular testing. Article 25 requires data protection to be built into systems from the design stage, with settings that default to the minimum data necessary. Storage limitation in Article 5(1)(e) means each category of data needs a retention period and a working way to delete or anonymise it when that period ends.
Processors and Article 28 contracts
Where a supplier genuinely acts as your processor, Article 28 requires you to use only processors that give sufficient guarantees, and to have a contract that covers, among other things, processing only on documented instructions, confidentiality, security, approval of sub-processors, help with rights requests and breaches, return or deletion of data at the end, and audits. Where the supplier is an independent or joint controller, an Article 28 contract is the wrong tool: you need a data sharing agreement or an Article 26 arrangement instead.
Data protection impact assessments
Article 35(1) requires a data protection impact assessment (DPIA) before processing that is likely to result in a high risk to individuals' rights and freedoms. Article 35(3) lists three cases where a DPIA is always required: a systematic and extensive evaluation of personal aspects based on automated processing, including profiling, on which decisions are based that produce legal or similarly significant effects; large-scale processing of special category or criminal offence data; and systematic monitoring of a publicly accessible area on a large scale. Each supervisory authority also publishes a list of processing operations that require a DPIA.
If a DPIA shows a high residual risk that you cannot reduce, Article 36 requires prior consultation with the supervisory authority before processing starts. Revisit the DPIA whenever the processing changes in a way that affects the risk.
Breach notification
A personal data breach is a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. A misdirected email or a lost laptop counts, not just a cyberattack. Under Article 33(1), the controller must notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of the breach, unless the breach is unlikely to result in a risk to individuals. A late notification must explain the delay, and information can be provided in phases.
Three further duties are often missed. A processor must notify the controller without undue delay after becoming aware of a breach (Article 33(2)), so your processor contracts should say how. The controller must document every breach, including those it decides not to report, with the facts, effects and remedial action (Article 33(5)). And where a breach is likely to result in a high risk to individuals, Article 34 requires them to be informed without undue delay, subject to limited exceptions.
Data protection officer
Article 37 makes a DPO mandatory in three situations: the processing is carried out by a public authority or body (except courts acting in their judicial capacity); your core activities consist of processing that requires regular and systematic monitoring of individuals on a large scale; or your core activities consist of large-scale processing of special category or criminal offence data. Member state law can add further cases.
If you appoint a DPO, whether required or voluntary, the role must meet Articles 38 and 39: involvement in all data protection issues, adequate resources and expertise, no instructions on how to carry out the tasks, no dismissal or penalty for performing them, direct reporting to the highest management level, and no other duties that create a conflict of interest. If you do not need a DPO, still name someone accountable for data protection, avoid the DPO title unless those conditions are met, and recheck the Article 37 criteria when your processing changes.
International transfers
Chapter V restricts transfers of personal data to countries outside the EEA. A transfer can rely on an adequacy decision under Article 45. Without one, it needs appropriate safeguards under Article 46, most commonly the Commission's standard contractual clauses (SCCs) together with an assessment of the destination country's law and, where needed, supplementary measures. The derogations in Article 49 cover only limited, specific situations.
The UK has an EU adequacy decision. The Commission adopted it in 2021 and renewed it in December 2025 through Implementing Decision (EU) 2025/2574, which sets its expiry at 27 December 2031. Transfers from the EU to the UK therefore do not need SCCs simply because the UK left the EU. Brazil has had an adequacy decision since January 2026 (Implementing Decision (EU) 2026/179), and US organisations are covered only if certified under the EU-US Data Privacy Framework. Check the Commission's list before relying on adequacy, because decisions are reviewed and can be amended or annulled. For data leaving the UK, UK law applies, and it currently allows transfers to the EEA.
Data subject rights
Articles 12 to 22 give individuals a set of rights over their personal data. The list below summarises the main ones. Whether a right applies, and in what form, depends on the processing activity, the lawful basis and the exceptions in the GDPR and member state law.
Under Article 12(3) you must respond without undue delay and in any event within one month of receiving the request. You can extend this by two further months where necessary, given the complexity and number of requests, as long as you tell the individual within the first month and explain why. Responses are normally free. Article 12(5) allows a reasonable fee, or a refusal, where a request is manifestly unfounded or excessive, which you must be able to demonstrate. Article 15(3) allows a reasonable fee for further copies.
The one-month deadline for access requests catches many organisations out because the data sits in several systems: CRM, email, HR software, support tickets and backups. Without a clear procedure and a named owner, requests regularly run past the deadline. An individual who is unhappy with a late or incomplete response can complain to a supervisory authority under Article 77.
The authoritative text of the GDPR, Regulation (EU) 2016/679, is on EUR-Lex. The European Data Protection Board publishes guidelines, recommendations and opinions on topics such as consent, breach notification, transfers and controller and processor roles at edpb.europa.eu. These interpret the GDPR rather than bind organisations directly, although the EDPB can adopt binding decisions in specific disputes under Article 65. The current list of adequacy decisions is on the European Commission website.