Accountability principle
The accountability principle means that the data controller is responsible for, and must be able to demonstrate, compliance with the GDPR principles. The principle is set out in Article 5(2) and is the seventh of the seven GDPR principles. Article 24 puts it into practice: the controller must implement appropriate technical and organisational measures so that processing complies with the Regulation, and be able to demonstrate that it does.
Back to Dictionary- Dictionary
- Accountability principle
Table of Contents
Most of the GDPR is about what you may and must do with personal data. The accountability principle adds a second question: can you show that you did it? Our GDPR compliance guide covers the requirements as a whole. This page covers the principle that ties them together.
Complying and being able to demonstrate it
Article 5(2) reads: "The controller shall be responsible for, and be able to demonstrate compliance with, paragraph 1 ('accountability')." Paragraph 1 holds the other six principles, from lawfulness, fairness and transparency to integrity and confidentiality. They are all explained in our overview of the seven GDPR principles (Regulation (EU) 2016/679).
The sentence has two halves. Being responsible means that the duty to comply sits with the data controller. Being able to demonstrate it means that the controller must be able to prove compliance, for example when the supervisory authority asks. The burden of proof lies with the controller, and compliance that is not documented is hard to demonstrate.
The European Data Protection Board (EDPB) makes the same point in its guidelines on controllers and processors: the GDPR "explicitly introduces the accountability principle, i.e. the controller shall be responsible for, and be able to demonstrate compliance with, the principles relating to processing of personal data in Article 5".
Processors have their own obligations under the GDPR, such as the contract requirements in Article 28 and their own record under Article 30(2). Article 5(2) itself is addressed to the controller.
How Article 24 makes the principle concrete
Under Article 24(1), the controller must implement "appropriate technical and organisational measures to ensure and to be able to demonstrate that processing is performed in accordance with this Regulation". The term technical and organisational measures comes up throughout the Regulation. Article 24 adds four points.
- Risk-based: The measures take into account the nature, scope, context and purposes of the processing and the risks to the rights and freedoms of natural persons.
- Reviewed and updated: The measures "shall be reviewed and updated where necessary". Accountability is therefore an ongoing task, not a one-off exercise.
- Data protection policies: Where proportionate in relation to the processing activities, the measures include appropriate data protection policies (Article 24(2)). Many organisations keep them with their other policies and procedures.
- Codes of conduct and certification: Adherence to approved codes of conduct (Article 40) or approved certification mechanisms (Article 42) may be used as an element in demonstrating compliance (Article 24(3)).
What typically documents accountability
The GDPR has no single list of documents that prove accountability. Several of its own requirements produce the documentation that is typically used, and many organisations start with the record of processing activities. The overview below shows those requirements. It is not a checklist for any particular organisation, because which requirements apply depends on the processing.
| Requirement | Article | What it documents |
|---|---|---|
| Record of processing activities | Art. 30 | Which processing takes place, for which purposes and with which recipients |
| Data protection by design and by default | Art. 25 | That data protection is built into systems and processes |
| Security of processing | Art. 32 | The technical and organisational security measures |
| Data protection impact assessment (DPIA) | Art. 35 | The assessment of processing likely to result in a high risk |
| Data protection officer (DPO) | Art. 37 | That a DPO has been designated where one is required |
| Data processing agreements | Art. 28 | The terms that bind processors |
Infringements of the basic principles in Article 5 can lead to fines of up to EUR 20 million or 4% of total worldwide annual turnover, whichever is higher (Article 83(5)(a)).
Accountability in .legal
In .legal, a progress bar and red markers show which fields are missing on each processing activity, and a full change log records every action on a processing activity. Processing activities can also be validated in a flow where the platform stamps who validated them and when. Whether you comply with the GDPR is still your own assessment.
Frequently asked questions about the accountability principle
What does accountability mean in the GDPR?
Accountability means that the data controller is responsible for complying with the GDPR principles and must be able to demonstrate compliance. The principle is set out in Article 5(2) and is the seventh of the seven principles. Article 24 requires appropriate technical and organisational measures that ensure and demonstrate compliance, reviewed and updated where necessary.
Who is responsible under the accountability principle, the controller or the processor?
Article 5(2) places accountability on the data controller. Processors have their own obligations under the GDPR, for example under Article 28 and a record of processing under Article 30(2). The duty to demonstrate compliance with the principles in Article 5(1) rests with the controller.
What documentation shows that you comply with the accountability principle?
The GDPR does not prescribe specific documents. Typical evidence comes from the Regulation's own requirements: the record of processing activities (Article 30), data protection by design and by default (Article 25), security measures (Article 32), DPIAs (Article 35), data processing agreements (Article 28) and data protection policies where proportionate (Article 24(2)). Which apply depends on the processing.
What is the difference between Article 5(2) and Article 24?
Article 5(2) states the principle: the controller is responsible for, and must be able to demonstrate, compliance with the principles in Article 5(1). Article 24 describes how: risk-based technical and organisational measures that ensure and demonstrate compliance, reviewed and updated where necessary, including data protection policies where proportionate.
Can a certification show that you comply with the GDPR?
A certification can help, but it is not proof on its own. Under Article 24(3), adherence to approved codes of conduct (Article 40) or approved certification mechanisms (Article 42) may be used as an element in demonstrating compliance. The controller remains responsible under Article 5(2).