General Data Protection Regulation, Pseudonymised Data and the Definition of Personal Data (Article 4(1) and (5), Recital 26)
Regulation (EU) 2016/679, Art. 4(1) and (5), recital 26
In force since .
A comprehensive regime rule binding public and private bodies.
- Audit expectation
- none
As of .
What it requires
- If you hold the additional information that attributes pseudonymised data to a natural person, treat the pseudonymised data as personal data and apply the Regulation to it (Article 4(1) and (5) and recital 26).
- For processing to count as pseudonymisation, keep the additional information needed to attribute the data to a specific data subject separately and subject it to technical and organisational measures that ensure the data are not attributed to an identified or identifiable natural person (Article 4(5)).
- If you receive pseudonymised data, treat it as personal data unless you are not in a position to lift the pseudonymisation measures during any processing under your control and the measures in fact prevent you from attributing the data to the person, including by cross-checking with other factors, judged by the means reasonably likely to be used, with regard to cost, time, available technology and technological developments (recital 26; Case C-413/23 P, paragraphs 77 and 85 to 86).
- If you pass pseudonymised data to a recipient, assess whether the data subject is identifiable from your own point of view as controller at the time of collection, whether or not the data are personal for the recipient, when you give the data subject the information about recipients (Case C-413/23 P, paragraphs 111 and 112, decided on the corresponding duty in Regulation (EU) 2018/1725).
- Where you apply pseudonymisation as a security or design measure, treat it as one of the technical and organisational measures Article 32(1), point (a), and Article 25(1) refer to, and not as a ground for taking the data outside the Regulation (Articles 25(1) and 32(1), point (a), and recital 28).
These lines are LexLint's reading of the law's text, as of . Also read by: Case C-413/23 P, European Data Protection Supervisor v Single Resolution Board, judgment of (First Chamber) (recorded ).
Who enforces it
Settledness
- As of
- Case link
- https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62023CJ0413
- Case citation
- Case C-413/23 P, European Data Protection Supervisor v Single Resolution Board, judgment of (First Chamber)
- Open questions
- Does a recipient of pseudonymised data show that it cannot lift the pseudonymisation measures and that they in fact prevent it from attributing the data to the person, a question the Court of Justice left to the General Court by referring Case T-557/20 back to it?
What it makes you log
Logging duty
Article 4(1) and (5) and recital 26 define personal data and pseudonymisation and say how identifiability is judged; none of them requires a log, register or record. The records of processing activities are required by Article 30, held on a separate row.
- Kind
- None
- As of
What this law does
Article 4(1) defines personal data as any information relating to an identified or identifiable natural person, one who can be identified, directly or indirectly, and Article 4(5) defines pseudonymisation as the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that the additional information is kept separately and is subject to technical and organisational measures to ensure that the personal data are not attributed to an identified or identifiable natural person.
Recital 26 provides that personal data which have undergone pseudonymisation, which could be attributed to a natural person by the use of additional information, should be considered to be information on an identifiable natural person, and that, to determine whether a natural person is identifiable, account should be taken of all the means reasonably likely to be used, such as singling out, either by the controller or by another person, with regard to objective factors such as the costs of and the amount of time required for identification, the available technology at the time of the processing and technological developments.
In Case C-582/14, Breyer, the Court of Justice held, under Directive 95/46, that a dynamic IP address registered by an online media services provider constitutes personal data in relation to that provider where it has the legal means that enable it to identify the data subject with additional data which the internet service provider has about that person.
In Case C-413/23 P, European Data Protection Supervisor v Single Resolution Board, judgment of , the Court of Justice held, on the parallel definition in Regulation (EU) 2018/1725, which it said is to be interpreted in the same way as Article 4(1) of the General Data Protection Regulation (GDPR), that pseudonymised data must not be regarded as constituting, in all cases and for every person, personal data.
For a recipient, the Court held that pseudonymised data are not personal in nature only if the recipient is not in a position to lift the pseudonymisation measures during any processing under its control and the measures in fact prevent it from attributing the data to the data subject, including by cross-checking with other factors, and that where third parties have means reasonably allowing them to attribute the data to the data subject the data subject must be regarded as identifiable as regards the transfer and any subsequent processing by those third parties.
For the controller, the Court held that the identifiable nature of the data subject is assessed, for the purposes of the duty to inform the data subject of the recipients of the data, at the time of collection of the data and from the point of view of the controller, so that the duty applied before the transfer and irrespective of whether the data were personal data from the recipient's point of view.
Article 32(1), point (a), lists the pseudonymisation and encryption of personal data among the technical and organisational measures a controller and processor implement to ensure a level of security appropriate to the risk, and Article 25(1) names pseudonymisation as an example of an appropriate technical and organisational measure designed to implement data-protection principles.
When LexLint raises it
When your app profile says your app processes personal data.