Storage limitation
Storage limitation is the GDPR principle that personal data must not be kept in a form that identifies data subjects for longer than is necessary for the purposes of the processing. It is set out in Article 5(1)(e) and is one of the seven GDPR principles. It does not say how long data may be kept. That is the job of the data retention period the controller sets.
Back to Dictionary- Dictionary
- Storage limitation
Table of Contents
Storage limitation is a rule about time, not a number. It says personal data must not stay linked to a person for longer than the purpose requires, but it sets no periods. Our GDPR compliance guide covers the wider requirements, and the article on the seven GDPR principles shows where this one fits.
What the principle requires
Article 5(1)(e) requires personal data to be "kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed" (Regulation (EU) 2016/679). The Regulation itself calls this ‘storage limitation’.
The key word is identification. The principle is about how long data can be linked to data subjects. Under Recital 26, the principles of data protection do not apply to anonymous information, including personal data rendered anonymous in such a manner that the data subject is not or no longer identifiable. Data anonymised in that way falls outside the principle.
There is one exception. Personal data may be stored for longer periods if it will be processed solely for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes in accordance with Article 89(1), subject to appropriate technical and organisational measures. Article 89(1) requires safeguards for the rights and freedoms of data subjects, and where those purposes can be fulfilled without identifying data subjects, they must be fulfilled in that manner.
From principle to practice: the retention period
The principle is in the Regulation, but the controller sets the period. Recital 39 says the period for which personal data are stored should be limited to a strict minimum, and that time limits should be established by the controller for erasure or for a periodic review. That time limit is a data retention period. It must be stated in two places:
- In the record: Under Article 30(1)(f), the record of processing activities contains, "where possible, the envisaged time limits for erasure of the different categories of data".
- In the information to data subjects: Under Article 13(2)(a), data subjects must be told the period for which the personal data will be stored or, if that is not possible, the criteria used to determine that period.
This page does not recommend periods for particular types of data. They depend on the purpose of the processing.
Storage limitation, retention period, data deletion and right to erasure
| Term | What it is | Where it comes from |
|---|---|---|
| Storage limitation | The principle that data must not be kept in identifiable form for longer than necessary | Article 5(1)(e) |
| Data retention period | The specific period after which a category of personal data is erased or anonymised | Set by the controller (Recital 39, Article 30(1)(f)) |
| Data deletion | The act of erasing the data from systems and archives | The controller’s procedures |
| Right to erasure | The data subject’s right to have data erased, for example when it is no longer necessary | Article 17(1)(a) |
In short: storage limitation is the rule, the retention period is the time limit and data deletion is the act. The right to erasure works from the data subject’s side: when the data is no longer necessary for the purposes for which it was collected or otherwise processed, the data subject can require its erasure under Article 17(1)(a).
How it relates to the other principles
There are seven principles: six in Article 5(1) and accountability in Article 5(2). Storage limitation is closely tied to three of them:
- Purpose limitation: Purpose limitation fixes the purpose, and the purpose decides how long the data is necessary.
- Data minimisation: Data minimisation limits how much data you process. Storage limitation limits for how long.
- Accountability: Under Article 5(2), the controller is responsible for, and must be able to demonstrate, compliance with the principles in Article 5(1), storage limitation included.
Storage limitation in .legal
In .legal, storage limitation is documented with retention periods as your own master data on the processing activity, and under each retention period there is a field to justify the choice of period. The platform does not set the periods for you.
Frequently asked questions about storage limitation
What does storage limitation mean in the GDPR?
Storage limitation is the principle in Article 5(1)(e): personal data must not be kept in a form which permits identification of data subjects for longer than is necessary for the purposes for which it is processed. It is one of the seven GDPR principles.
What is the difference between storage limitation and a data retention period?
Storage limitation is the principle, and it sets no periods. A data retention period is the specific period the controller sets for a category of data in order to comply with the principle. Recital 39 says controllers should establish time limits for erasure or for a periodic review.
Can personal data be kept forever if it is used for statistics?
Not without conditions. Article 5(1)(e) allows longer storage if the data will be processed solely for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes in accordance with Article 89(1), subject to appropriate technical and organisational measures. Where those purposes can be fulfilled without identifying data subjects, Article 89(1) requires them to be fulfilled in that manner.
Does storage limitation apply to anonymised data?
No. Under Recital 26, the principles of data protection do not apply to anonymous information, including personal data rendered anonymous in such a manner that the data subject is not or no longer identifiable. If the data can still be linked to a person, it is not anonymous.
How do you show that you comply with storage limitation?
Under Article 5(2), the controller must be able to demonstrate compliance with the principles. In practice that means retention periods for each category of data in the record of processing activities, where possible (Article 30(1)(f)), information about the storage period for data subjects (Article 13(2)(a)), and data that is actually erased or anonymised when the period expires.