Incident to report to a regulator?Incident to report? Intake Line

CJEU in EDPS V SRB: Pseudonymised Data Is Not Personal Data for Everyone in Every Case

The Court of Justice ruled on 4 September 2025 in C-413/23 P that pseudonymised data is not personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. in all cases and for every person. The controllerThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.'s duty to inform is assessed at collection, from the controllerThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.'s point of view, before any transfer.

4 September 2025 · Enforcement

What happened

On 4 September 2025 the Court of Justice set aside the General Court’s judgment in Case C-413/23 P, EDPS v SRB and referred the case back to it. The Single Resolution Board had sent pseudonymised comments from shareholders and creditors to Deloitte without telling them. We read the Court’s press release, not the full judgment, and we did not check what the General Court has done since.

What it changes

The Court made three points:

  • Personal opinions or views are necessarily closely linked to their author, so a regulator need not examine their content, purpose or effects to find that they relate to that person.
  • Pseudonymised data is not personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. in all cases and for every person. PseudonymisationProcessing personal data so that they can no longer be attributed to a specific person without additional information, which is kept separately and protected by technical and organisational measures. Whether a holder or recipient can reasonably identify an individual remains part of the personal-data assessment; pseudonymisation should not be treated as a guarantee of anonymity. may, depending on the circumstances, prevent people other than the controllerThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it. from identifying the individual.
  • The duty to inform is part of the relationship between the individual and the controllerThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.. Whether the person is identifiable is assessed at collection, from the controllerThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.‘s point of view, before any transfer.

The case concerns Regulation 2018/1725, which binds EU bodies. We tagged the GDPRGeneral Data Protection Regulation because the EDPB’s draft anonymisation guidelines rely on this judgment when they discuss the GDPRGeneral Data Protection Regulation. That link is our reading.

Who is affected

ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it. and recipients that share or receive pseudonymised data. The sector tags are our reading, based on the sectors that commonly share such data.

What to do now

  • List the pseudonymised datasets you send out, and who holds the key.
  • Assess identifiability for each recipient separately, and record the result.
  • Keep recipients in your privacy notice, even if the data is not personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. in the recipient’s hands.
  • Check the judgment itself before you change a legal position.

Get updates for the EU

One email a week when something changes. Add other countries if you need them.

Countries
European Union

Pick one or more

One email a week, only when something changed. Each email has an unsubscribe link. Privacy notice

RSS Feed for EU

Loading the form…