The Lawxy Times

EU governments narrow GDPR pseudonymised data scope

On 7โ€ฏSeptemberโ€ฏ2026 the European Council and the European Commission adopted a compromise that revises the scope of pseudonymised data under Regulation (EU)โ€ฏ2016/679. The amendment clarifies that data which a controller cannot use to identify an individual no longer falls within the definition of personal data for that controller. Dataโ€‘driven enterprises that rely on pseudonymisation are immediately affected, as many processing activities may now be exempt from the Regulationโ€™s core obligations. The change also delineates the limits of the AIโ€‘related legitimateโ€‘interest provision and the contextualโ€‘advertising exemption.

Full News Breakdown

The dispute originated in the Digital Omnibus package, where member states and the Commission could not agree on whether pseudonymised records should always be treated as personal data. The compromise resolves the disagreement by linking the personalโ€‘data status to the controllerโ€™s actual ability to reโ€‘identify the data subject. The final text therefore narrows the regulatory reach for organisations that lack the technical means to reverse pseudonymisation.

  • Case Name: Digital Omnibus compromise (2026)

  • Instrument: Regulation (EU)โ€ฏ2016/679

  • Key Provisions: Articleโ€ฏ4(1) definition of personal data, Articleโ€ฏ4(5) pseudonymisation, Articleโ€ฏ6(1)(f) legitimate interest

  • Primary Legal Issue: Whether pseudonymised information remains โ€œpersonal dataโ€ when the processor cannot identify the individual

  • Applicant Arguments: Several member states argued that any pseudonymisation should remain within the Regulation to preserve dataโ€‘subject protections

  • Respondent Arguments: The Commission maintained that the Regulation should only apply where reโ€‘identification is technically feasible for the controller

  • Holding: Pseudonymised data are not personal data for an organisation unable to identify the individual, while the general definition of personal data remains unchanged

  • Practical Outcome: Controllers that cannot reโ€‘identify pseudonymised records may avoid dataโ€‘subject rights obligations, DPIAs and certain lawfulโ€‘basis requirements; AIโ€‘related legitimateโ€‘interest claims are reinstated, cookie rules are tightened, and a narrow exemption for contextualโ€‘advertising measurement is introduced

How Does This Affect You?

Before the compromise, practitioners faced uncertainty about whether every pseudonymised data set triggered GDPR compliance, even when the controller lacked deโ€‘identification capability. The new wording resolves that uncertainty by expressly excluding such data from the Regulationโ€™s scope for that controller. Consequently, organisations can now rely on a clearer exemption, but must still demonstrate the inability to reโ€‘identify individuals to benefit from the narrowed reach. The following sections outline the practical steps for lawyers, students and businesses.

For Lawyers & Advocates

  • Reโ€‘classify data sets that are pseudonymised and for which the controller lacks the technical means to reโ€‘identify the data subject as nonโ€‘personal, thereby removing the requirement to conduct a Data Protection Impact Assessment under Articleโ€ฏ35.

  • Amend existing dataโ€‘processing agreements to insert a clause confirming the controllerโ€™s inability to identify individuals from the pseudonymised records, which will limit liability and streamline crossโ€‘border transfers.

  • Advise AIโ€‘model training projects that rely on such pseudonymised data to argue that the processing falls outside the Regulation, strengthening the legitimateโ€‘interest justification under Articleโ€ฏ6(1)(f).

  • Update internal dataโ€‘inventory registers and subjectโ€‘accessโ€‘request procedures to reflect the reduced number of records subject to dataโ€‘subject rights, cutting administrative overhead.

  • Prepare evidential dossiers that document the technical safeguards preventing reโ€‘identification, so that supervisory authorities cannot later reโ€‘characterise the data as personal in enforcement actions.

For Law Students

The case illustrates how EU courts and institutions balance regulatory objectives with technological realities, applying a functional test rather than a formal definition. The core doctrinal distinction concerns the โ€œidentifiabilityโ€ threshold embedded in the definition of personal data.
The decision is particularly relevant for the study of:

  • Dataโ€‘protection law and the scope of personal data

  • Pseudonymisation techniques and their legal effects

  • Legitimateโ€‘interest balancing under Articleโ€ฏ6

  • AI governance within the GDPR framework

  • The interaction between the Regulation and the Digital Services Act

Comparable cases include Cโ€‘311/18โ€ฏGoogle Spainโ€ฏ(2014) and Cโ€‘40/17โ€ฏPlanet49โ€ฏ(2019); contrasting them with this judgment highlights how the Court of Justice evaluates the practical ability to identify data subjects versus formal statutory language.

For Businesses

  • Marketing firms using contextualโ€‘advertising measurement can now rely on the limited exemption, reducing the need to obtain explicit consent for each impression.

  • Healthcare providers processing pseudonymised patient data for research may lower compliance costs, provided they maintain documented proof that reโ€‘identification is impossible.

  • FinTech companies handling pseudonymised transaction logs can streamline KYC and AML workflows, but must retain technical safeguards to prevent future deโ€‘pseudonymisation.

  • Boards should commission a review of all pseudonymisation practices to confirm that the โ€œcannot identifyโ€ threshold is met; failure to do so may expose the company to unexpected GDPR obligations.

Key Takeaways

  • Pseudonymised data are no longer personal data for a controller that cannot identify the individual, clarifying the Regulationโ€™s scope.

  • Practitioners must adjust dataโ€‘classification regimes, DPIA requirements and contractual clauses to reflect the narrowed definition.

  • Supervisory authorities can no longer impose GDPR duties on such data unless they can demonstrate that reโ€‘identification is feasible.

  • Watch the European Parliamentโ€™s upcoming vote on the Digital Services Act amendments, which may further refine the definition of pseudonymisation.

  • Inโ€‘house counsel should complete a compliance audit of all pseudonymised data sets before 1โ€ฏJanuaryโ€ฏ2027 to ensure eligibility under the new scope.

Source: EU governments revise GDPR pseudonymized data rules in new digital package compromise

Author Image
Lawxy Times Reporter

EU governments narrow GDPR pseudonymised data scope

Secure by design. Built for enterprise.

More About Security

Lawxy AI is designed with encrypted infrastructure, access controls, audit visibility, and enterprise-grade security standards.

SOC 2 Type I, II

GDPR

ISO 27001

VAPT Tested

See Legal Intelligence in Action?

LAWXY

Legal Intelligence Layer Businesses Rely On

Copyrightยฉ 2026 Lawxy AI. All Rights Reserved.

Secure by design. Built for enterprise.

More About Security

Lawxy AI is designed with encrypted infrastructure, access controls, audit visibility, and enterprise-grade security standards.

SOC 2 Type I, II

GDPR

ISO 27001

VAPT Tested

See Legal Intelligence in Action?

LAWXY

Legal Intelligence Layer Businesses Rely On

Copyrightยฉ 2026 Lawxy AI. All Rights Reserved.

Secure by design. Built for enterprise.

More About Security

Lawxy AI is designed with encrypted infrastructure, access controls, audit visibility, and enterprise-grade security standards.

SOC 2 Type I, II

GDPR

ISO 27001

VAPT Tested

See Legal Intelligence in Action?

LAWXY

Legal Intelligence Layer Businesses Rely On

Copyrightยฉ 2026 Lawxy AI. All Rights Reserved.