{"id":1779,"date":"2025-09-10T15:33:59","date_gmt":"2025-09-10T12:33:59","guid":{"rendered":"https:\/\/sgklegal.gr\/?p=1779"},"modified":"2025-09-10T15:44:02","modified_gmt":"2025-09-10T12:44:02","slug":"cjeu-clarifies-scope-of-pseudonymisation","status":"publish","type":"post","link":"https:\/\/sgklegal.gr\/en\/cjeu-clarifies-scope-of-pseudonymisation\/","title":{"rendered":"CJEU Ruling on Pseudonymisation: Landmark Case C-413\/23 P (EDPS v SRB) and Its Impact on GDPR Compliance"},"content":{"rendered":"<h2 class=\"text-base font-semibold\">1. Introduction<\/h2>\n<p class=\"whitespace-pre-wrap my-2\">The Court of Justice of the European Union (hereinafter &#8220;CJEU&#8221;) issued <a href=\"https:\/\/curia.europa.eu\/juris\/document\/document_print.jsf?mode=req&amp;pageIndex=0&amp;docid=303863&amp;part=1&amp;doclang=EN&amp;text=&amp;dir=&amp;occ=first&amp;cid=2510741\" target=\"_blank\" rel=\"noopener\">a significant decision on data protection law<\/a> that will reshape how organisations approach pseudonymisation and information obligations under the European data protection framework (hereinafter the &#8220;Decision&#8221;).<\/p>\n<p class=\"whitespace-pre-wrap my-2\">In Case C-413\/23 P (EDPS v SRB), delivered on 4 September 2025, the CJEU set aside a General Court judgment and established important principles for the concept of personal data and the role of pseudonymisation.<\/p>\n<p class=\"whitespace-pre-wrap my-2\">The case arose from the 2017 resolution of Banco Popular Espa\u00f1ol, where affected shareholders and creditors participated in a &#8220;right to be heard&#8221; process. When the Single Resolution Board (SRB) shared pseudonymised comments from this process with external auditor Deloitte, data protection complaints emerged that ultimately reached the EU&#8217;s highest court.<\/p>\n<h2 class=\"text-base font-semibold\">2. The Legal Framework and Core Disputes<\/h2>\n<h3 class=\"text-sm font-semibold\">2.1. Defining Personal Data in the Digital Age<\/h3>\n<p class=\"whitespace-pre-wrap my-2\">The central dispute revolved around <span class=\"cursor-default hover:bg-blue-50\" data-state=\"closed\">Article 3(1) of Regulation 2018\/1725 (hereinafter &#8220;EUDPR&#8221;), which defines &#8216;personal data&#8217; as &#8216;any information relating to an identified or identifiable natural person&#8217;.<\/span><\/p>\n<p class=\"whitespace-pre-wrap my-2\">The General Court had previously found that the European Data Protection Supervisor (hereinafter &#8220;EDPS&#8221;) incorrectly classified comments shared with Deloitte as personal data, arguing that insufficient analysis had been conducted regarding their content, purpose, and effect.<\/p>\n<p class=\"whitespace-pre-wrap my-2\">The CJEU fundamentally disagreed with this approach. Establishing a crucial principle, the Court held that <span class=\"cursor-default hover:bg-blue-50\" data-state=\"closed\">information relates to an identifiable natural person where, by reason of its content, purpose or effect, it is linked to an identifiable person.\u00a0<\/span><\/p>\n<p class=\"whitespace-pre-wrap my-2\">However, the CJEU went further, recognising that subjective expressions such as personal opinions or views, as expressions of a person&#8217;s thinking, are necessarily closely linked to that person and do not require further content analysis.<\/p>\n<p class=\"whitespace-pre-wrap my-2\">This decision may significantly reduce the burden on Data Protection Authorities when dealing with subjective information such as comments, opinions, or assessments, establishing that their inherently personal nature must be recognised without extensive content analysis.<\/p>\n<h3 class=\"text-sm font-semibold\">2.2. Pseudonymisation: Protection Measure, Not Legal Transformation<\/h3>\n<p class=\"whitespace-pre-wrap my-2\">The CJEU analysed the increasingly important technique of pseudonymisation with notable nuance. While confirming that <span class=\"cursor-default hover:bg-blue-50\" data-state=\"closed\">pseudonymisation may impact whether data are personal within the meaning of Article 3(1) EUDPR<\/span>, it clarified that this does not equate to anonymisation. The Decision establishes that this depends entirely on the specific circumstances and the perspective of different processors.<\/p>\n<p class=\"whitespace-pre-wrap my-2\">The CJEU rejected the EDPS&#8217;s argument that pseudonymised data should always be considered personal data simply because identifying information exists somewhere. Instead, it confirmed that effective pseudonymisation measures can render data non-personal for specific recipients, provided they cannot reasonably identify the data subjects through available means.<\/p>\n<p class=\"whitespace-pre-wrap my-2\">This contextual approach means that the same dataset could simultaneously be personal data for the original controller (who retains identification keys) and non-personal data for recipients who lack reasonable means of identification.<\/p>\n<h3 class=\"text-sm font-semibold\">2.3. Information Obligations: Controller&#8217;s Perspective Prevails<\/h3>\n<p class=\"whitespace-pre-wrap my-2\">Perhaps the most practically significant aspect of the decision concerns transparency obligations under Article 15(1)(d) EUDPR. The CJEU clarified that <span class=\"cursor-default hover:bg-blue-50\" data-state=\"closed\">regarding information obligations, the identifiable nature of the data subject must be assessed at the time of collection of information relating to them from the controller&#8217;s perspective.\u00a0<\/span><\/p>\n<p class=\"whitespace-pre-wrap my-2\">This settles a crucial timing question: Controllers cannot avoid transparency obligations by arguing that data becomes non-personal after pseudonymisation for recipients. In short, if the controller can identify the data subject at the time of collection, they must inform them regardless of technical measures that will be applied to the information subsequently.<\/p>\n<h2 class=\"text-base font-semibold\">3. Practical Implications for Legal Practice<\/h2>\n<h3 class=\"text-sm font-semibold\">3.1. For Data Controllers<\/h3>\n<p class=\"whitespace-pre-wrap my-2\">The Decision provides significant clarification for organisations handling personal data:<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Enhanced Transparency Requirements<\/strong>: Controllers must disclose all potential recipients in their data protection privacy notices, even if that data will be pseudonymised before transfer. The recipient&#8217;s subsequent inability to identify natural persons does not exempt the controller from this obligation.<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Pseudonymisation Strategy<\/strong>: While pseudonymisation remains an important technical measure for enhancing confidentiality, controllers should not assume it automatically removes data protection obligations. The technique&#8217;s effectiveness depends on implementation specifics and recipient capabilities.<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Opinion and Comment Handling<\/strong>: Organisations collecting subjective information\u2014surveys, comments, complaints, or consultation responses\u2014should presume this constitutes personal data without requiring extensive content analysis.<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Risk Assessment<\/strong>: Before a data disclosure\/transfer, the effectiveness of pseudonymisation should be evaluated from each recipient&#8217;s perspective, considering their technical capabilities and access to supplementary identifying information.<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Compliance Timing<\/strong>: Privacy impact assessments for information confidentiality and compliance reviews should focus on the controller&#8217;s position at data collection, not post-transfer scenarios involving pseudonymised data.<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Cross-border Transfers<\/strong>: The decision&#8217;s reasoning may influence how adequacy decisions and international transfers are assessed, particularly where pseudonymisation is used as a safeguard measure. Re-evaluation of any Transfer Impact Assessments (TIAs) is recommended.<\/p>\n<h3 class=\"text-sm font-semibold\">3.2. For Banking and Financial Services<\/h3>\n<p class=\"whitespace-pre-wrap my-2\">Given the case&#8217;s origins in banking resolution procedures, financial institutions should note:<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Regulatory Reporting<\/strong>: When sharing data with supervisory authorities, auditors, or resolution authorities, comprehensive privacy statements must identify these potential recipients, regardless of planned pseudonymisation.<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Customer Communication<\/strong>: Standard data protection privacy notices may require updating to reflect the broad interpretation of personal data and recipient disclosure obligations.<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Due Diligence Procedures<\/strong>: When engaging third parties for data analysis, financial institutions must evaluate their capabilities to identify natural persons to determine whether pseudonymisation effectively renders data non-identifiable and consequently falls outside the definition of personal data.<\/p>\n<h2 class=\"text-base font-semibold\">4. Conclusion and Strategic Directions<\/h2>\n<p class=\"whitespace-pre-wrap my-2\">This landmark decision confirms specific conclusions regarding data protection law. Specifically:<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">First<\/strong>, the scope of personal data is generally particularly broad and is influenced by subjective information expressing individual thoughts or opinions. With the (almost automatic) classification of subjective opinions as personal data, the strict compliance scope will encompass cases of collecting comments, questionnaires, or feedback interactions, even where the connection to the person is not obvious.<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Second<\/strong>, pseudonymisation remains useful. However, its effectiveness in removing personal data status depends on contextual factors, particularly the recipient&#8217;s reasonable means of identification. This &#8220;relativisation&#8221; of the concept of pseudonymisation, depending on the recipient&#8217;s technical means, provides flexibility but also uncertainty. While it allows for realistic assessment of identification risk, it may make it difficult for organisations to predict in advance when data will be considered personal, especially in environments with multiple and diverse recipients.<\/p>\n<p class=\"whitespace-pre-wrap my-2\"><strong class=\"text-sm font-semibold\">Third<\/strong>, transparency obligations are formed at data collection based on the controller&#8217;s perspective. Organisations cannot defer or avoid these obligations based on subsequent processing limitations affecting third parties. This means detailed and continuous updating of data protection privacy notices by organisations is required, adding recipients and\/or processors.<\/p>\n<p class=\"whitespace-pre-wrap my-2\">It is noted that the CJEU reiterated that the definition of personal data in the EUDPR must be interpreted in full harmony with the corresponding definition in the GDPR, strengthening the coherence of European data protection law.<\/p>\n<p class=\"whitespace-pre-wrap my-2\">Generally, it is recommended that controllers re-examine existing data protection privacy notices as well as data processing agreements (DPAs) in light of these principles. Particular attention should be paid to consultation processes, comment mechanisms, and any arrangements involving pseudonymised data transfers.<\/p>\n<p class=\"whitespace-pre-wrap my-2\">The CJEU&#8217;s approach reflects the EU&#8217;s commitment to broad data protection coverage while recognising that privacy-enhancing technologies can provide meaningful protection when properly implemented. As pseudonymisation and other technical measures continue to evolve, this decision provides a framework for assessing their legal significance that balances practical privacy benefits with fundamental transparency rights.<\/p>\n<p class=\"whitespace-pre-wrap my-2\">For organisations operating across multiple jurisdictions, this decision reinforces the importance of adopting the most protective approach when designing global privacy compliance programmes, ensuring that EU standards are met regardless of local variations in data protection law.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>1. Introduction The Court of Justice of the European Union (hereinafter &#8220;CJEU&#8221;) issued a significant decision on data protection law that will reshape how organisations approach pseudonymisation and information obligations under the European data protection framework (hereinafter the &#8220;Decision&#8221;). In Case C-413\/23 P (EDPS v SRB), delivered on 4 September 2025, the CJEU set aside [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":1777,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[605,620,612,610,613,615,46,607,618,159,608,616,609,604,611,111,621,400,137,150,123,614,606,617,619,116],"class_list":["post-1779","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-en","tag-anonymisation","tag-banco-popular-en","tag-bank-resolution","tag-c-413-23-p","tag-case-law","tag-cjeu-en","tag-compliance-en","tag-data-controller","tag-data-privacy-en","tag-data-protection-en","tag-data-subjects","tag-edps-en","tag-eu-law","tag-european-court-of-justice","tag-financial-services","tag-gdpr-en","tag-information-privacy-en","tag-legal-analysis","tag-personal-data","tag-privacy-law","tag-pseudonymisation","tag-regulation-2018-1725","tag-right-to-information","tag-srb-en","tag-transparency-obligations-en","tag-psevdonymopoiisi"],"_links":{"self":[{"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/posts\/1779","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/comments?post=1779"}],"version-history":[{"count":2,"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/posts\/1779\/revisions"}],"predecessor-version":[{"id":1781,"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/posts\/1779\/revisions\/1781"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/media\/1777"}],"wp:attachment":[{"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/media?parent=1779"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/categories?post=1779"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sgklegal.gr\/en\/wp-json\/wp\/v2\/tags?post=1779"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}