Data Protection Monitor
Global Privacy & Data Protection Intelligence

European Economic Area (Bloc) Data Protection & Privacy Regulation

EEA schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 91 claims · 66 sources in the cumulative register

On 21 October 2026, the Council's Permanent Representatives Committee agreed its negotiating mandate on the European Commission's Digital Omnibus proposal, COM(2025) 837, which would amend the GDPR's definition of personal data under Article 4(1), the interplay between fines methodology and Article 83(2), and related provisions.

Data collected Data published

Expert reviewed as at 24 Oct 2026 · peter-pink-howitt-ramparts

Not fully checked this cycle: Regulator & Framework, Enforcement & Redress (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 12 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix143 claims · 62 sources · expert reviewed
38 Confirmed45 Probable8 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: Expert-reviewed · As-of date: 2026-11-17

Member jurisdictions

This page covers law made at European Economic Area (Bloc) level once. Each member’s page covers implementation, national authorities, national options and local enforcement (30 of 30 members covered here).

Jurisdiction brief

European Economic Area (Bloc) operates under a regulated (omnibus) framework supervised by European Data Protection Board (EDPB), coordinating the national supervisory authorit, with 10 regulatory modules assessed in the current cycle.

  • D1 · Regulator & Framework: Harmonised 30-state EEA regime anchored in Regulation (EU) 2016/679 (GDPR), updated by the Cross-Border Procedural Regulation (EU) 2025/2518 (adopted 26 Nov 2025, entered into force 1 Jan 2026, applicable 2 April 2027) and active legislative negotiations on the Digital Omnibus Proposal COM(2025) 837 final.
  • D2 · Lawful Processing: Core provisions are stable and enforced, but the Digital Omnibus proposal (still in trilogue as of mid-2026) creates near-term uncertainty over consent-signal mechanics and the sensitive-data/AI derogation.
  • D3 · Data Subject Rights: Rights are robustly enforced and subject to active coordinated supervisory scrutiny, but a pending legislative change (abuse-of-access-rights clarification) could alter practical scope.
  • D4 · Controller & Processor: Baseline obligations are stable and well-enforced, but simplification proposals (still in trilogue) will materially change SME/SMC recordkeeping and breach-notification thresholds once adopted.
All 10 module posture summaries
  • D1 · Regulator & Framework: Harmonised 30-state EEA regime anchored in Regulation (EU) 2016/679 (GDPR), updated by the Cross-Border Procedural Regulation (EU) 2025/2518 (adopted 26 Nov 2025, entered into force 1 Jan 2026, applicable 2 April 2027) and active legislative negotiations on the Digital Omnibus Proposal COM(2025) 837 final.
  • D2 · Lawful Processing: Core provisions are stable and enforced, but the Digital Omnibus proposal (still in trilogue as of mid-2026) creates near-term uncertainty over consent-signal mechanics and the sensitive-data/AI derogation.
  • D3 · Data Subject Rights: Rights are robustly enforced and subject to active coordinated supervisory scrutiny, but a pending legislative change (abuse-of-access-rights clarification) could alter practical scope.
  • D4 · Controller & Processor: Baseline obligations are stable and well-enforced, but simplification proposals (still in trilogue) will materially change SME/SMC recordkeeping and breach-notification thresholds once adopted.
  • D5 · Cross-Border & Adequacy: Comprehensive Chapter V transfer architecture with 17 active European Commission adequacy decisions (including UK adequacy renewed on 19 December 2025 until 27 December 2031, European Patent Organisation adequacy in July 2025, and Brazil adequacy adopted 27 January 2026) and the EU–US Data Privacy Framework upheld by the General Court in Case T-553/23 Latombe v Commission (3 September 2025), balanced against active DPC/EDPB transfer enforcement (TikTok €530m fine, May 2025; Case T-354/22 Bindl v Commission, Jan 2025).
  • D6 · Sectoral Watch: Health and telecoms/eprivacy overlays are actively evidenced; other sectoral overlays (financial, employment, education, insurance) lack direct 2026 sourcing in this pass and are flagged as gaps.
  • D7 · AdTech & Marketing: Cookie-consent fatigue is a recognised, unresolved policy problem; the principal legislative fix (Art. 88b) is currently stalled in the Council, leaving practical mechanics unsettled.
  • D8 · AI, Biometrics & Automated: Article 22 is settled law with recent CJEU interpretation, but the practical GDPR/AI Act interface remains in active development pending joint EDPB-Commission guidelines and AI Act simplification.
  • D9 · Children's Privacy: Core Article 8 mechanism is well-established law, but dedicated children's-data guidelines remain in development and several sub-areas (age verification specifics, education settings, dependent adults) lack direct 2026 sourcing in this pass.
  • D10 · Enforcement & Redress: Enforcement powers are broad, actively used at scale (billion-euro-class fines), collective redress mechanisms are in force, and a further procedural-harmonisation regulation is already adopted (pending 2027 application).
Key regulatory facts for European Economic Area (Bloc)
Key regulatory facts for European Economic Area (Bloc)
Regulatory DimensionEuropean Economic Area (Bloc) Standing Position
JurisdictionEuropean Economic Area (Bloc) (EEA)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 91 sourced findings)
Regulator & FrameworkHarmonised 30-state EEA regime anchored in Regulation (EU) 2016/679 (GDPR), updated by the Cross-Border Procedural Regulation (EU) 2025/2518 (adopted 26 Nov 2025, entered into force 1 Jan 2026, applicable 2 April 2027) and active legislative negotiations on the Digital Omnibus Proposal COM(2025) 837 final.
Lawful Processing & Special DataCore provisions are stable and enforced, but the Digital Omnibus proposal (still in trilogue as of mid-2026) creates near-term uncertainty over consent-signal mechanics and the sensitive-data/AI derogation.
Data Subject RightsRights are robustly enforced and subject to active coordinated supervisory scrutiny, but a pending legislative change (abuse-of-access-rights clarification) could alter practical scope.
Controller/Processor DutiesBaseline obligations are stable and well-enforced, but simplification proposals (still in trilogue) will materially change SME/SMC recordkeeping and breach-notification thresholds once adopted.
Primary Instruments CitedEFTA EEA-Lex factsheet (AI Act), European Economic Area (Bloc) Official Instrument (atomity.de eu-data-act-switching-charges-20), Nordia Law (commentary), Kennedys Law, CJEU, Meta Platforms v Bundeskartellamt, C-252/21
Last Confirmed / Updated (66 sources in cumulative register)

#

Harmonised 30-state EEA regime anchored in Regulation (EU) 2016/679 (GDPR), updated by the Cross-Border Procedural Regulation (EU) 2025/2518 (adopted 26 Nov 2025, entered into force 1 Jan 2026, applicable 2 April 2027) and active legislative negotiations on the Digital Omnibus Proposal COM(2025) 837 final.

Primary frameworkRegulation (EU) 2016/679 (GDPR), incorporated into the EEA Agreement (Annex XI)
Traffic-light rationale — AmberHarmonised 30-state EEA regime anchored in Regulation (EU) 2016/679 (GDPR), updated by the Cross-Border Procedural Regulation (EU) 2025/2518 (adopted 26 Nov 2025, entered into force 1 Jan 2026, applicable 2 April 2027) and active legislative negotiations on the Digital Omnibus Proposal COM(2025) 837 final.

Sub-modules (5)

Category narrative 245 words

The European Economic Area (EEA) data protection regime applies across all 27 EU Member States and the 3 EEA EFTA states (Iceland, Liechtenstein, and Norway, where the GDPR was incorporated into Annex XI to the EEA Agreement by EEA Joint Committee Decision No 154/2018 effective 20 July 2018). The core architecture comprises Regulation (EU) 2016/679 (GDPR), Directive (EU) 2016/680 (Law Enforcement Directive), Directive 2002/58/EC (ePrivacy Directive, following the European Commission's formal withdrawal of the long-stalled ePrivacy Regulation proposal in February 2025), and Regulation (EU) 2018/1725 (EUDPR for EU institutions). Supervision is decentralised across national Data Protection Authorities (DPAs) in each of the 30 EEA states (including decentralized Land-level DPAs in Germany) coordinated through the One-Stop-Shop (Art. 56) and Consistency Mechanism (Arts. 60–65) by the European Data Protection Board (EDPB), in which the three EEA EFTA DPAs (Datatilsynet Norway, Persónuvernd Iceland, DSS Liechtenstein) and the EFTA Surveillance Authority participate as full operational members without voting rights or eligibility to hold the Chair (Decision No 154/2018). Two major legislative developments reshape the framework in 2025–2026: first, Regulation (EU) 2025/2518 on additional procedural rules for cross-border GDPR enforcement was enacted on 26 November 2025 (OJ L, 12.12.2025), entered into force on 1 January 2026, and applies from 2 April 2027; second, on 19 November 2025 the European Commission tabled the Digital Omnibus Regulation proposal (COM(2025) 837 final; EDPB–EDPS Joint Opinion 2/2026 issued 10 February 2026), proposing targeted amendments to the GDPR, ePrivacy Directive, Data Act, and AI Act.

Sources and claims (18)
  1. Confirmed EDPS — National data protection authorities of the EU Member States and the EEA EFTA states (Iceland, Liechtenstein, Norway) are the primary enforcement bodies for the GDPR, cooperating through the EDPB's consistency and cooperation framework. observed
  2. Confirmed European Parliament Legislative Train Schedule — The EDPB may issue binding decisions under Article 65 GDPR that direct a lead supervisory authority to alter proposed measures, including materially increasing proposed fines, as occurred in the Meta Ireland Facebook/Instagram inquiries where the EDPB directed the fine be raised from a proposed maximum of €59 million to €390 million. observed
  3. Confirmed European Parliament Legislative Train Schedule — Regulation (EU) 2016/679 (GDPR) repealed and replaced Directive 95/46/EC as the EU's general data protection framework. observed
  4. Confirmed European Parliament Legislative Train Schedule — Regulation (EU) 2025/2518, laying down additional procedural rules for GDPR cross-border enforcement (harmonising complaint admissibility, lead/concerned-authority cooperation and party rights), was adopted on 26 November 2025, published in the Official Journal on 12 December 2025, and applies from 2 April 2027. observed
  5. Confirmed European Parliament Legislative Train Schedule — GDPR Article 2 material scope covers processing of personal data by automated means and manual processing forming part of a filing system, as reflected in EDPB and CNIL guidance defining personal data broadly (any information relating to an identified or identifiable natural person). observed
  6. Confirmed European Parliament Legislative Train Schedule — Since 25 May 2018, GDPR applies to processing in the context of an EU/EEA establishment's activities and to processing by non-established controllers/processors targeting EEA data subjects through the offering of goods or services or the monitoring of their behaviour within the Union. observed
  7. Confirmed EDPB — An EDPB report on extraterritorial enforcement notes that any exercise of a DPA's investigative powers outside EU/EEA territory requires the consent of the foreign state, limiting practical extraterritorial reach notwithstanding Article 3's broad scope. observed
  8. Confirmed European Parliament Legislative Train Schedule — The GDPR is generally understood to have abolished the ex-ante notification/registration regime that existed under Directive 95/46/EC, substituting an accountability-based compliance model (Article 5(2), Article 24). observed
  9. Probable Legiscope — European Data Protection Board comprises: The EDPB's membership consists of the head of each national supervisory authority, one per EU Member State plus Iceland, Liechtenstein and Norway. observed
  10. Confirmed European Parliament Legislative Train Schedule — Regulation (EU) 2025/2518 extends deadline: Reforms GDPR cross-border enforcement procedure (complaint admissibility, lead/concerned-authority cooperation, party rights); adopted 26 Nov 2025, published in the OJ 12 Dec 2025, applying from 2 Apr 2027. observed
  11. Probable ppc.land (explainer, corroborating official EFTA dates) — GDPR (Regulation (EU) 2016/679) — Incorporated into the EEA Agreement by EEA Joint Committee Decision No 154/2018 of 6 July 2018, entering into force in Iceland, Liechtenstein and Norway on 20 July 2018. observed
  12. Confirmed EFTA EEA-Lex factsheet (AI Act) — AI Act, DSA, Data Act — None has been incorporated into the EEA Agreement for Iceland, Liechtenstein and Norway as of this cycle; each is listed by EFTA as under scrutiny with a draft Joint Committee Decision pending. observed
  13. Probable Quasa — Digital Omnibus Regulation (2025/0360 COD) — Coreper failed to adopt a Council negotiating mandate on 7 October 2026 and again on 11 October 2026, principally over Data Act trade-secret provisions observed
  14. Probable ppc.land (explainer, corroborating official EFTA dates) — The EDPB's membership consists of the head of each national supervisory authority, one per EU Member State plus Iceland, Liechtenstein and Norway. observed
  15. Probable ppc.land (explainer, corroborating official EFTA dates) — European Data Protection Board — The EDPB's membership consists of the head of each national supervisory authority, one per EU Member State plus Iceland, Liechtenstein and Norway. observed
  16. Probable EFTA EEA-Lex factsheet (AI Act) — Regulation (EU) 2025/2518 — Reforms GDPR cross-border enforcement procedure (complaint admissibility, lead/concerned-authority cooperation, party rights); adopted 26 Nov 2025, published in the OJ 12 Dec 2025, applying from 2 Apr 2027. observed
  17. Probable Legal247 — Digital Omnibus proposal COM(2025) 837 — On 21 October 2026 Coreper agreed the Council's negotiating mandate on the Commission's Digital Omnibus proposal, which would amend GDPR Art 4(1) (personal data definition), Art 83(2) (fines methodology interplay) and related provisions; the mandate keeps the current personal-data definition, permits AI training on the legitimate-interest basis, and supports a 4-month (reduced from 6-month) breach-notification re-request deadline. observed
  18. Probable EFTA EEA-Lex factsheet (AI Act) — Digital Omnibus proposal (COM(2025)837) — Proposal to amend GDPR Article 33 remains unenacted; Council negotiating mandate agreed 21 October 2026 but European Parliament has not adopted a position and trilogue has not started. observed

#

Core provisions are stable and enforced, but the Digital Omnibus proposal (still in trilogue as of mid-2026) creates near-term uncertainty over consent-signal mechanics and the sensitive-data/AI derogation.

Primary frameworkGDPR Articles 4-11 (Regulation (EU) 2016/679); proposed amendments under the Digital Omnibus (COM(2025) 836 final)
Traffic-light rationale — AmberCore provisions are stable and enforced, but the Digital Omnibus proposal (still in trilogue as of mid-2026) creates near-term uncertainty over consent-signal mechanics and the sensitive-data/AI derogation.

Sub-modules (4)

Category narrative 314 words

All processing must rest on one of the six exhaustive lawful bases in Art. 6(1)(a)–(f) GDPR. Following CJEU Case C-252/21 Meta Platforms v Bundeskartellamt, Case C-621/22 Koninklijke Nederlandse Lawn Tennisbond (4 October 2024, confirming a purely commercial interest can constitute a legitimate interest under Art. 6(1)(f) if strictly necessary and balanced), and EDPB Opinion 28/2024 on AI Models (17 December 2024), controllers relying on Art. 6(1)(f) must satisfy a rigorous three-step test (legitimate interest, strict necessity / data minimisation, and balancing against reasonable expectations) supplemented by unconditional opt-out safeguards. Consent under Art. 4(11) and Art. 7 must be freely given, specific, informed, and unambiguous; under EDPB Opinion 08/2024 on 'Consent or Pay' deployed by Large Online Platforms (17 April 2024), binary 'pay or consent to behavioural advertising' models without a genuinely equivalent tracking-free third option generally fail the 'freely given' requirement. Special category data under Art. 9(1) requires an Art. 9(2) derogation (where Member State law may maintain or introduce further conditions for genetic, biometric, or health data under Art. 9(4)), and in Case C-446/21 Schrems v Meta Platforms (4 October 2024) the CJEU held that a user's public statement about their own sexual orientation at a panel discussion does not authorize a platform under Art. 9(2)(e) ('manifestly made public') to aggregate off-platform special category data for personalised advertising. On pseudonymisation, the CJEU Grand Chamber in Case C-413/23 P EDPS v SRB (4 September 2025) held that whether pseudonymised data is personal data is assessed from the perspective of the recipient ('relative approach'), though the disclosing controller's own transparency duties under Art. 13/15 remain assessed at the point of collection before transmission. Separately, the Commission's proposed Digital Omnibus Regulation (COM(2025) 837 final, 19 November 2025; legislative proposal, NOT yet in force) proposes codifying the SRB relative identifiability test in Art. 4(1) GDPR and introducing specific AI training provisions under Art. 9(2)(k) and Art. 88c.

Sources and claims (8)
  1. Confirmed European Parliament Legislative Train Schedule — The Irish DPC, implementing EDPB binding decisions, fined Meta Ireland a combined €390 million (€210m Facebook, €180m Instagram) after finding that Meta could not rely on the contractual-necessity legal basis under Article 6 GDPR for behavioural-advertising processing. observed
  2. Confirmed European Parliament Legislative Train Schedule — The Digital Omnibus proposal introduces a new GDPR Article 88b that would allow individuals to express privacy choices automatically through technical means such as browser settings, rather than manual cookie-banner interaction. observed
  3. Probable European Parliament Legislative Train Schedule — In June 2026 the Council of the EU removed the proposed Article 88b automated-consent-signal provision from its negotiating position following lobbying from media and advertising industry groups, creating legislative uncertainty over the final mechanism. observed
  4. Confirmed European Parliament Legislative Train Schedule — The EDPB and EDPS welcomed the Digital Omnibus's proposed derogation permitting incidental and residual processing of special-category (Article 9) data in the context of developing and operating AI systems, while recommending improvements to scope and lifecycle safeguards. observed
  5. Confirmed EDPB — EDPB Guidelines 01/2025 clarify that pseudonymised data, when attributable to an individual via additional information, remains personal data, and detail how pseudonymisation supports Articles 5, 25 and 32 compliance. observed
  6. Confirmed European Parliament Legislative Train Schedule — Following the CJEU's September 2025 EDPS v SRB ruling that the same dataset can be personal data for one recipient and anonymous for another, the EDPB published draft Guidelines 02/2026 on Anonymisation (7 July 2026, consultation to 30 October 2026) setting out a two-question, three-criteria (no isolation, no linkage, no inference) test for anonymisation. observed
  7. Probable Praxikon (reporting OEIL procedure status) — Digital Omnibus Regulation proposal (COM(2025)837) — As of 15 Sep 2026, the Parliament's Legislative Observatory lists the proposal (amending GDPR Arts 4, 6/88c, 9) as 'Awaiting committee decision': no committee vote, no plenary vote, no Parliament position; Council has not adopted a negotiating mandate; no trilogue started. observed
  8. Probable CJEU, Meta Platforms v Bundeskartellamt, C-252/21 — GDPR Art 6(1)(f) — Each controller must independently satisfy the Art 6(1)(f) balancing test for its own processing; a private commercial operator cannot in principle rely on Art 6(1)(f) to share data with law enforcement for crime-prevention purposes unrelated to its own economic activity (CJEU Meta v Bundeskartellamt, C-252/21, 4 July 2023). observed

#

Rights are robustly enforced and subject to active coordinated supervisory scrutiny, but a pending legislative change (abuse-of-access-rights clarification) could alter practical scope.

Primary frameworkGDPR Articles 12-23 (Regulation (EU) 2016/679)
Traffic-light rationale — AmberRights are robustly enforced and subject to active coordinated supervisory scrutiny, but a pending legislative change (abuse-of-access-rights clarification) could alter practical scope.

Sub-modules (5)

Category narrative 257 words

Chapter III (Arts. 12–23) GDPR guarantees transparent information (Arts. 13–14), right of access and a free first copy of personal data undergoing processing (Art. 15; CJEU Case C-487/21 Österreichische Datenschutzbehörde and Case C-307/22 FT v DW confirming the right to a free initial copy of medical records even when requested for non-data-protection litigation), rectification (Art. 16), erasure / right to be forgotten (Art. 17), restriction (Art. 18), data portability (Art. 20, reinforced from 12 September 2025 by real-time IoT/connected-product data switching rights under the EU Data Act Regulation (EU) 2023/2854), objection (Art. 21, unconditional for direct marketing), and rights against solely automated decision-making (Art. 22). In Case C-203/22 Dun & Bradstreet Austria (27 February 2025), the CJEU held that under Art. 15(1)(h) GDPR a controller conducting automated credit scoring must explain the actual procedure and principles applied to the data subject's profile so the individual can verify accuracy and consistency, and cannot rely on a blanket 'trade secrets' refusal (instead disclosing contested algorithms to the DPA or court for case-by-case balancing). Response deadlines under Art. 12(3) are one calendar month from receipt, extendable by two further months for complex or numerous requests upon notice within the first month. Under the Digital Omnibus Proposal COM(2025) 837 final (legislative proposal, not yet in force), the Commission has proposed clarifying Art. 12(5) so that abusive DSARs pursued solely for non-data-protection purposes (such as pre-trial discovery abuse) may be treated as manifestly unfounded or excessive, though the EDPB–EDPS Joint Opinion 2/2026 (10 February 2026) opposed restricting access rights on motive grounds.

Sources and claims (5)
  1. Confirmed EDPB — The CJEU has confirmed (Case C-307/22) that data subjects may legitimately exercise the Article 15 right of access for objectives other than becoming aware of processing or verifying its lawfulness, without needing to provide particular motivation. observed
  2. Confirmed European Parliament Legislative Train Schedule — The Digital Omnibus proposes to give controllers legal clarity for cases of abuse of rights by data subjects, but the EDPB and EDPS consider that exercising the access right for purposes other than data protection should not itself be treated as an element defining abuse. observed
  3. Confirmed EDPB — The EDPB ran a year-long 2025 Coordinated Enforcement Framework action on the Article 17 right to erasure/right to be forgotten, adopting a report on the action's findings in 2026. observed
  4. Confirmed EDPB — The right to data portability under Article 20 GDPR continues to be interpreted per the WP29 Guidelines on the right to data portability, as endorsed by the EDPB. observed
  5. Confirmed EDPB — During 2026, 25 DPAs across Europe are participating in the EDPB's Coordinated Enforcement Framework action assessing controller compliance with Article 12-14 transparency and information obligations that condition the effective exercise of data subject rights. observed

#

Baseline obligations are stable and well-enforced, but simplification proposals (still in trilogue) will materially change SME/SMC recordkeeping and breach-notification thresholds once adopted.

Primary frameworkGDPR Articles 24-39 (Regulation (EU) 2016/679); Digital Omnibus (COM(2025) 836 final)
Traffic-light rationale — AmberBaseline obligations are stable and well-enforced, but simplification proposals (still in trilogue) will materially change SME/SMC recordkeeping and breach-notification thresholds once adopted.

Sub-modules (7)

Category narrative 262 words

Chapter IV (Arts. 24–43) GDPR establishes harmonised accountability obligations across all 30 EEA jurisdictions: Data Protection by Design and by Default (Art. 25; enforced in CJEU Case C-446/21 Schrems v Meta as requiring strict purpose-bounded data compartmentalisation), Joint Controller arrangements (Art. 26), mandatory Processor agreements and prior authorisation for sub-processors (Art. 28; reinforced by EDPB Opinion 22/2024 of 7 October 2024 requiring controllers to identify and verify safeguards down the entire sub-processor chain), written electronic Records of Processing Activities (Art. 30 ROPA), risk-based security measures (Art. 32), mandatory DPO designation where Art. 37(1) criteria or stricter national thresholds (such as Germany's § 38 BDSG 20-employee rule) apply, and Data Protection Impact Assessments (Art. 35 DPIA) prior to high-risk processing (the EDPB's 2025 Coordinated Enforcement Framework action focused on Art. 17 erasure, following its 2024 action on Art. 15 access and 2023 action on DPOs). Personal data breaches must be notified to the competent DPA within 72 hours under Art. 33 unless unlikely to result in a risk, and communicated to data subjects without undue delay under Art. 34 where high risk is likely. Under the proposed Digital Omnibus Regulation COM(2025) 837 final (19 November 2025; legislative proposal, NOT yet in force), the Commission has proposed raising the Art. 33 DPA breach-notification threshold to 'high risk', extending the reporting deadline from 72 to 96 hours via the ENISA Single Entry Point built for NIS2/DORA/CER, and expanding the Art. 30(5) ROPA exemption from <250 employees to small mid-cap enterprises (<750 employees) unless processing is likely to result in a high risk under Art. 35.

Sources and claims (5)
  1. Confirmed EDPB — As part of its 2026-2027 work programme, the EDPB is developing ready-to-use EU templates for legitimate interest assessments, records of processing, privacy notices, data breach notifications and data protection impact assessments to facilitate compliance. observed
  2. Confirmed European Parliament Legislative Train Schedule — The Commission's Digital Omnibus proposal would amend Article 30(5) GDPR to raise the records-of-processing exemption threshold from enterprises/organisations under 250 employees to those under 750 employees, unless the processing is likely to result in high risk to individuals. observed
  3. Confirmed EDPB — EDPB guidance explains how pseudonymisation, alongside encryption, functions as a technical safeguard supporting Article 32 security-of-processing obligations and Article 25 data protection by design. observed
  4. Confirmed European Parliament Legislative Train Schedule — The EDPB and EDPS support the Digital Omnibus proposal to increase the risk threshold that triggers the Article 33 duty to notify a personal data breach to the competent DPA, and to extend the notification deadline, alongside introducing common breach-notification and DPIA templates. observed
  5. Confirmed EDPB Guidelines 9/2022 on personal data breach notification — GDPR Art 33 — As processor, a provider must notify each affected controller of a personal-data breach 'without undue delay'; there is no statutory 72-hour allowance for the processor. observed

#

Comprehensive Chapter V transfer architecture with 17 active European Commission adequacy decisions (including UK adequacy renewed on 19 December 2025 until 27 December 2031, European Patent Organisation adequacy in July 2025, and Brazil adequacy adopted 27 January 2026) and the EU–US Data Privacy Framework upheld by the General Court in Case T-553/23 Latombe v Commission (3 September 2025), balanced against active DPC/EDPB transfer enforcement (TikTok €530m fine, May 2025; Case T-354/22 Bindl v Commission, Jan 2025).

Primary frameworkGDPR Chapter V, Articles 44-50 (Regulation (EU) 2016/679)
Traffic-light rationale — AmberComprehensive Chapter V transfer architecture with 17 active European Commission adequacy decisions (including UK adequacy renewed on 19 December 2025 until 27 December 2031, European Patent Organisation adequacy in July 2025, and Brazil adequacy adopted 27 January 2026) and the EU–US Data Privacy Framework upheld by the General Court in Case T-553/23 Latombe v Commission (3 September 2025), balanced against active DPC/EDPB transfer enforcement (TikTok €530m fine, May 2025; Case T-354/22 Bindl v Commission, Jan 2025).

Sub-modules (6)

Category narrative 309 words

Personal data circulates freely across all 30 EEA states under Art. 1(3) GDPR and EEA Joint Committee Decision No 154/2018. Outbound transfers to third countries or international organisations are governed by Chapter V (Arts. 44–50) GDPR. Under Art. 45 GDPR, the European Commission has adopted adequacy decisions covering Andorra, Argentina, Canada (PIPEDA commercial organisations), Faroe Islands, Guernsey, Israel, Isle of Man, Japan, Jersey, New Zealand, Republic of Korea, Switzerland, the United Kingdom (renewed on 19 December 2025 by Implementing Decisions (EU) 2025/2545 and (EU) 2025/2546 for six years until 27 December 2031, and incorporated into the EEA Agreement by EEA Joint Committee Decision No 37/2026 on 20 February 2026), the United States (EU–US Data Privacy Framework, Implementing Decision (EU) 2023/1795, upheld by the EU General Court on 3 September 2025 in Case T-553/23 Latombe v Commission and pending appeal in Case C-715/25 P), Uruguay, the European Patent Organisation (Implementing Decision (EU) 2025/1382 of 15 July 2025 — first Art. 45 adequacy decision for an international organisation), and Brazil (mutual adequacy decision adopted 27 January 2026). Where no adequacy decision applies, exporters must implement Art. 46 appropriate safeguards — primarily the 2021 Standard Contractual Clauses (Decision (EU) 2021/914, to be supplemented by the Commission's dedicated Module 5 SCCs for third-country controllers/processors already directly subject to Art. 3(2) GDPR) or Binding Corporate Rules (Art. 47) — supported by a Schrems II Transfer Impact Assessment (TIA) and supplementary technical measures, alongside Art. 48 blocking restrictions against non-treaty third-country foreign-authority disclosure orders (EDPB Guidelines 02/2024 of 2 December 2024). Active transfer enforcement includes the Irish DPC's €530 million fine against TikTok (2 May 2025) for remote access to EEA user data from China and the General Court's award of €400 non-material damages in Case T-354/22 Bindl v Commission (8 January 2025) for unlawful transfer of IP/browser data to the US via Facebook Login.

Sources and claims (12)
  1. Confirmed EDPB — Article 46 GDPR lists appropriate-safeguards transfer tools (including SCCs and BCRs), and Article 49 provides derogations for specific situations, both usable absent an adequacy decision, subject to the exporter maintaining Article 5 GDPR compliance. observed
  2. Confirmed European Parliament Legislative Train Schedule — The GDPR framework positions the European Commission as the body issuing adequacy decisions under Article 45 to third countries (e.g. the UK, renewed 19 December 2025 to run until 27 December 2031); the EEA itself is not a recipient of inbound adequacy findings under this mechanism. observed
  3. Confirmed EDPB — The European Commission has recognised adequate third countries/territories including Andorra, Argentina, Canada, the Faroe Islands, Guernsey, Israel, Isle of Man, Japan, Jersey, New Zealand, South Korea, Switzerland, the United Kingdom, Uruguay and the United States. observed
  4. Confirmed European Parliament Legislative Train Schedule — The EU-US Data Privacy Framework adequacy decision, adopted 10 July 2023, allows personal data to flow to certified US organisations without additional transfer safeguards; as of early 2026 more than 3,500 US companies had self-certified, though the framework remains subject to potential CJEU review and EDPB monitoring including a first-review report. observed
  5. Confirmed European Parliament Legislative Train Schedule — The European Commission adopted modernised Standard Contractual Clauses via Implementing Decision (EU) 2021/914 in June 2021, and since 27 September 2021 only the current SCCs may be used for new transfer contracts; the EDPB continues to issue opinions approving Member State DPAs' draft BCR authorisations (e.g. multiple 2026 opinions on Dutch SA BCR decisions). observed
  6. Confirmed European Parliament Legislative Train Schedule — A Transfer Impact Assessment must be carried out by an exporter relying on an Article 46 GDPR transfer tool prior to transferring data to a third country, unless the destination is covered by an adequacy decision or an Article 49 derogation applies. observed
  7. Probable European Commission — A separate EU legislative proposal for sovereign cloud computing services (impact assessment submitted to the Regulatory Scrutiny Board, positive opinion 8 May 2026) introduces safeguards for EU-citizen personal data processed via cloud infrastructure and is framed as complementary to, not a replacement for, the GDPR and EU-US DPF transfer regime. observed
  8. Probable Lexology — EU UK adequacy decision (Implementing Decision (EU) 2021/1772) grants adequacy: Does not cover Gibraltar, including under its December 2025 renewal to 27 December 2031; Gibraltar is not deemed adequate by the European Commission. observed
  9. Probable EFTA EEA-Lex factsheet (AI Act) — ANPD Resolution CD/ANPD No. 32/2026 (Brazil) — Brazil's ANPD Resolution recognises the EU as adequate for LGPD purposes and extends that recognition to Iceland, Liechtenstein and Norway as EEA-EFTA states, alongside the Commission's corresponding EU adequacy decision for Brazil. observed
  10. Probable CJEU, Meta Platforms v Bundeskartellamt, C-252/21 — EU UK adequacy decision (Implementing Decision (EU) 2021/1772) — Does not cover Gibraltar, including under its December 2025 renewal to 27 December 2031; Gibraltar is not deemed adequate by the European Commission. observed
  11. Probable ppc.land (explainer, corroborating official EFTA dates) — Transfers within the EEA (including to/from Iceland, Liechtenstein and Norway) are not third-country transfers under GDPR Chapter V because GDPR is incorporated EEA-wide via EEA Joint Committee Decision No 154/2018. observed
  12. Confirmed EDPB — EDPB Opinions 24-26/2026 — On 13 October 2026 the EDPB adopted Opinion 24/2026 (Michelin Group Controller BCRs, French SA), Opinion 25/2026 (Snowflake Group Controller BCRs, Dutch SA) and Opinion 26/2026 (Snowflake Group Processor BCRs, Dutch SA) under GDPR Art 64. observed

#

Health and telecoms/eprivacy overlays are actively evidenced; other sectoral overlays (financial, employment, education, insurance) lack direct 2026 sourcing in this pass and are flagged as gaps.

Primary frameworkGDPR (Regulation (EU) 2016/679) with sector-specific overlays (ePrivacy Directive 2002/58/EC)
Traffic-light rationale — AmberHealth and telecoms/eprivacy overlays are actively evidenced; other sectoral overlays (financial, employment, education, insurance) lack direct 2026 sourcing in this pass and are flagged as gaps.

Sub-modules (8)

Data access sharingNot assessed

No narrative recorded for this sub-module.

Claims (8):

  • EU Data Act Art. 29 prohibits: From 12 January 2027, providers of data processing services shall not impose any switching charges on the customer for the switching process; until that date, only cost-covering reduced switching charges are permitted.
  • EU Data Act (data access by design) requires: The Data Act's data-access-by-design obligation for connected products and related services applies from 12 September 2026, forward-looking only.
  • EU Data Act Art. 29 — From 12 January 2027, providers of data processing services shall not impose any switching charges on the customer for the switching process; until that date, only cost-covering reduced switching charges are permitted.
  • EU Data Act (data access by design) — The Data Act's data-access-by-design obligation for connected products and related services applies from 12 September 2026, forward-looking only.
  • EU Data Act (Regulation (EU) 2023/2854) Art.29 — From 12 Jan 2027, data-processing-service providers must not impose any switching charges for the switching process; until then only cost-covering reduced charges are permitted.
  • Data Act (Regulation (EU) 2023/2854) — Applies generally in the EU since 12 September 2025; its Art 3(1) 'access by design' duty, per Art 50, applies to connected products and related services placed on the market after 12 September 2026.
  • Data Act EEA incorporation — As of 10 October 2026 the Data Act has not been incorporated into the EEA Agreement for Iceland, Liechtenstein and Norway; no EEA Joint Committee Decision has been adopted and no incorporation date has been announced.
  • EU Data Act Art 29(1) — From 12 January 2027 providers of data processing services shall not impose any switching charges on the customer for the switching process, including data egress charges; until then Art 29(2)-(3) permits only reduced charges capped at costs directly linked to the switching process.
Category narrative 241 words

Across the EEA, horizontal GDPR obligations intersect with dense EU sectoral regulations and national opening-clause laws. In financial services, DORA (Regulation (EU) 2022/2554, applicable since 17 January 2025), PSD2 (and the incoming PSR/PSD3 package), and the AML Regulation (EU) 2024/1624 require strict ICT incident reporting, fraud-monitoring data governance, and AML retention reconciled with GDPR data minimisation (per EDPB Guidelines on PSD2/AML interplay). In health and life sciences, Regulation (EU) 2025/327 establishing the European Health Data Space (EHDS) was adopted on 11 February 2025 and entered into force on 26 March 2025 (with phased application from March 2027 to 2031), creating harmonised primary patient electronic health record rights and a permit-based secondary health-data research framework across all Member States alongside Art. 9(4) national laws. Electronic communications remain governed by Directive 2002/58/EC (ePrivacy Directive) and national transpositions following the Commission's February 2025 withdrawal of the proposed ePrivacy Regulation. Employment data is governed by Art. 88 GDPR national rules (such as § 26 BDSG in Germany as interpreted in CJEU Case C-34/21 and Case C-65/23 MK v K GmbH of 19 December 2024, confirming national collective agreements and laws must still satisfy every substantive Art. 5/6 GDPR condition) and the Platform Work Directive (EU) 2024/2831 (enacted October 2024, prohibiting processing of platform workers' emotional state, private conversations, and off-duty data). Credit scoring is tightly constrained by CJEU Case C-634/21 SCHUFA Holding (7 December 2023) and Case C-203/22 Dun & Bradstreet Austria (27 February 2025).

Sources and claims (11)
  1. Confirmed European Parliament Legislative Train Schedule — CNIL imposed a €5 million fine against IQVIA in connection with health-data processing, evidencing active French enforcement in the health sector. observed
  2. Confirmed European Parliament Legislative Train Schedule — The Digital Omnibus proposes amendments to the ePrivacy Directive including limited additional derogations to the general prohibition on storing or accessing data in terminal equipment, which the EDPB/EDPS urge be balanced by incentivising contextual over behavioural advertising. observed
  3. Confirmed European Parliament Legislative Train Schedule — In December 2023, the CJEU issued its first interpretation of Article 22 GDPR (right not to be subject to solely automated decision-making) in the context of automated credit scoring (Case C-634/21, SCHUFA). observed
  4. Probable ePrecisio — EU Data Act Art. 29 prohibits: From 12 January 2027, providers of data processing services shall not impose any switching charges on the customer for the switching process; until that date, only cost-covering reduced switching charges are permitted. observed
  5. Probable McCann FitzGerald (law firm commentary) — EU Data Act (data access by design) requires: The Data Act's data-access-by-design obligation for connected products and related services applies from 12 September 2026, forward-looking only. observed
  6. Probable EDPB Guidelines 9/2022 on personal data breach notification — EU Data Act Art. 29 — From 12 January 2027, providers of data processing services shall not impose any switching charges on the customer for the switching process; until that date, only cost-covering reduced switching charges are permitted. observed
  7. Probable McCann FitzGerald (law firm commentary) — EU Data Act (data access by design) — The Data Act's data-access-by-design obligation for connected products and related services applies from 12 September 2026, forward-looking only. observed
  8. Probable https://atomity.de/blog/eu-data-act-switching-charges-2027-cloud-exit — EU Data Act (Regulation (EU) 2023/2854) Art.29 — From 12 Jan 2027, data-processing-service providers must not impose any switching charges for the switching process; until then only cost-covering reduced charges are permitted.
  9. Probable McCann FitzGerald (law firm commentary) — Data Act (Regulation (EU) 2023/2854) — Applies generally in the EU since 12 September 2025; its Art 3(1) 'access by design' duty, per Art 50, applies to connected products and related services placed on the market after 12 September 2026. observed
  10. Probable Nordia Law (commentary) — Data Act EEA incorporation — As of 10 October 2026 the Data Act has not been incorporated into the EEA Agreement for Iceland, Liechtenstein and Norway; no EEA Joint Committee Decision has been adopted and no incorporation date has been announced. observed
  11. Probable Atomity — EU Data Act Art 29(1) — From 12 January 2027 providers of data processing services shall not impose any switching charges on the customer for the switching process, including data egress charges; until then Art 29(2)-(3) permits only reduced charges capped at costs directly linked to the switching process. observed

#

Cookie-consent fatigue is a recognised, unresolved policy problem; the principal legislative fix (Art. 88b) is currently stalled in the Council, leaving practical mechanics unsettled.

Primary frameworkePrivacy Directive 2002/58/EC read with GDPR consent standards (Regulation (EU) 2016/679)
Traffic-light rationale — AmberCookie-consent fatigue is a recognised, unresolved policy problem; the principal legislative fix (Art. 88b) is currently stalled in the Council, leaving practical mechanics unsettled.

Sub-modules (6)

Category narrative 247 words

AdTech and commercial tracking in the EEA are governed by the dual layer of Art. 5(3) of the ePrivacy Directive 2002/58/EC (device storage/access) and the GDPR (subsequent personal data processing and profiling). Under EDPB Guidelines 2/2023 on the Technical Scope of Art. 5(3) (adopted 7 October 2024), Art. 5(3) prior opt-in consent applies not only to traditional HTTP cookies but also to tracking pixels, URL/link decoration, local storage, SDKs, IoT telemetry, and IP-only / device fingerprinting. For platform profiling, the Digital Services Act (Regulation (EU) 2022/2065) strictly prohibits targeted advertising based on profiling using Art. 9 special categories (Art. 26(3) DSA) or profiling of minors (Art. 28(2) DSA), while Art. 5(2) of the Digital Markets Act (Regulation (EU) 2022/1925) prohibits designated gatekeepers from combining or cross-using personal data across core platform services and third-party services without valid GDPR opt-in consent. On 'Consent or Pay', EDPB Opinion 08/2024 (17 April 2024) and the European Commission's DMA non-compliance decision against Meta (€200m fine, 23 April 2025) establish that gatekeepers and large platforms cannot force a binary choice between pervasive behavioural tracking and a paid subscription without offering a less-personalised free alternative. In the Digital Omnibus Proposal COM(2025) 837 final (19 November 2025; legislative proposal, NOT yet in force), the Commission has proposed folding device-access rules for personal data directly into a new Art. 88a GDPR (preserving exemptions for transmission, user-requested services, first-party aggregated audience measurement, and security) and mandating browser/OS-level automated consent/refusal signals under Art. 88b within 24–48 months.

Sources and claims (7)
  1. Confirmed European Parliament Legislative Train Schedule — The Digital Omnibus's proposed Article 88b GDPR would allow automated, machine-readable expression of individuals' data-processing choices, with oversight of such mechanisms entrusted to DPAs; in June 2026 the Council of the EU removed this provision from its position paper after industry lobbying. observed
  2. Probable European Parliament Legislative Train Schedule — Cookie banners are widely characterised as causing consent fatigue and facilitating data exploitation rather than achieving the meaningful, effective data protection the ePrivacy Directive and GDPR were intended to deliver. observed
  3. Confirmed European Parliament Legislative Train Schedule — Global Privacy Control is implemented on at least 385,000 websites and recognised under California, Colorado, Connecticut and other US state privacy laws, and is discussed as a candidate technical standard for the EU's proposed automated consent-signal mechanism, though as an opt-out-only specification it cannot natively express affirmative consent. observed
  4. Confirmed European Parliament Legislative Train Schedule — The EDPB and EDPS welcome limited additional ePrivacy derogations proposed in the Digital Omnibus and invite co-legislators to incentivise contextual advertising over behavioural advertising through a specific, safeguarded exception. observed
  5. Confirmed European Parliament Legislative Train Schedule — Digital Omnibus (Data track) classifies as: The Digital Omnibus's Data track (amending GDPR, ePrivacy, NIS2 and DORA, including the Art. 88b automated-consent-signal mechanism) remained under negotiation as of this cycle, separate from and slower than the AI Omnibus track which entered into force 27 July 2026. observed
  6. Probable Nordia Law (commentary) — Digital Omnibus (Data track) — The Digital Omnibus's Data track (amending GDPR, ePrivacy, NIS2 and DORA, including the Art. 88b automated-consent-signal mechanism) remained under negotiation as of this cycle, separate from and slower than the AI Omnibus track which entered into force 27 July 2026. observed
  7. Confirmed EFTA EEA-Lex factsheet (DSA) — DSA (Regulation (EU) 2022/2065) — Platforms must set out the main parameters of their recommender systems and any user options to change them (Art 27); very large platforms must offer at least one non-profiling-based option (Art 38); profiling-based advertising to known minors is banned (Art 28(2)); these bind the EU-27 but have not been EEA-incorporated for the EFTA-3. observed

#

Article 22 is settled law with recent CJEU interpretation, but the practical GDPR/AI Act interface remains in active development pending joint EDPB-Commission guidelines and AI Act simplification.

Primary frameworkGDPR Article 22 (Regulation (EU) 2016/679); interplay with Regulation (EU) 2024/1689 (AI Act)
Traffic-light rationale — AmberArticle 22 is settled law with recent CJEU interpretation, but the practical GDPR/AI Act interface remains in active development pending joint EDPB-Commission guidelines and AI Act simplification.

Sub-modules (6)

Category narrative 288 words

Algorithmic, AI, and biometric governance in the EEA is governed by the dual regime of the GDPR (Arts. 5, 6, 9, 15(1)(h), 22, and 35) and the EU Artificial Intelligence Act (Regulation (EU) 2024/1689, entered into force 1 August 2024). Under Art. 22 GDPR and CJEU Case C-634/21 SCHUFA Holding (7 December 2023), automated profiling (such as probability credit scoring) falls within the Art. 22(1) prohibition even where a third party makes the final formal decision, if that third party relies predominantly on the automated score; and under Case C-203/22 Dun & Bradstreet Austria (27 February 2025), controllers must give data subjects a concrete, understandable explanation of how their specific attributes produced the automated output under Art. 15(1)(h). On AI model training and deployment, EDPB Opinion 28/2024 (17 December 2024) establishes the criteria for evaluating when a trained AI model can be considered anonymous (requiring negligible likelihood of both direct training-data extraction and query-based regurgitation) and how Art. 6(1)(f) legitimate interests applies to web-scraped training data. Under the EU AI Act, Chapter II prohibitions entered into force on 2 February 2025 — banning untargeted scraping of facial images from the internet or CCTV to build facial recognition databases (Art. 5(1)(e)), emotion recognition in workplaces and educational institutions (Art. 5(1)(f)), biometric categorisation inferring sensitive traits (Art. 5(1)(g)), social scoring (Art. 5(1)(c)), and real-time remote biometric identification in publicly accessible spaces for law enforcement save under narrow judicial-warrant exceptions (Art. 5(1)(h)) — while General-Purpose AI (GPAI) obligations applied from 2 August 2025 and high-risk AI system obligations (including Art. 27 Fundamental Rights Impact Assessments aligned with Art. 35 GDPR DPIAs) apply from 2 August 2026 (subject to targeted timeline adjustments proposed in the Digital Omnibus Package of 19 November 2025).

Sources and claims (12)
  1. Confirmed European Parliament Legislative Train Schedule — Article 22 GDPR provides data subjects with the right not to be subject to a decision based solely on automated processing, including profiling, that produces legal effects or similarly significantly affects them. observed
  2. Probable European Parliament Legislative Train Schedule — The EDPB and the European Commission are jointly preparing guidelines on the interplay between the GDPR and the AI Act, addressing transparency, risk assessments, bias detection and accountability, with a first draft potentially available soon and final adoption possible by end of 2026. observed
  3. Confirmed European Parliament Legislative Train Schedule — The EU's AI Act high-risk system compliance timeline, originally set for August 2026, is being extended via the Digital Omnibus on AI, with organisations to receive six months to comply once implementing standards and support tools are confirmed, capped at December 2027. observed
  4. Confirmed European Parliament Legislative Train Schedule — Genetic data falls within the Article 9 special-category regime; the Digital Omnibus's proposed derogation for incidental/residual sensitive-data processing in AI development would potentially extend to genetic data, subject to EDPB/EDPS-recommended lifecycle safeguards. observed
  5. Confirmed EDPB — The EDPB has issued formal correspondence to the European Commission addressing the privacy implications of proposed US legislative changes to entry conditions for EEA citizens, and separately regarding a US Supreme Court judgment, reflecting ongoing EDPB engagement with law-enforcement and surveillance-adjacent international-cooperation matters. observed
  6. Confirmed European Parliament Legislative Train Schedule — Regulation (EU) 2026/1744 (Digital Omnibus on AI) extends deadline: Entered into force 27 July 2026 (published in the OJ 24 July 2026); postpones AI Act high-risk-system obligations to 2 December 2027 for Annex III systems and 2 August 2028 for Annex I product-embedded systems. observed
  7. Probable Kennedys Law — AI Act Art. 4a grants: Permits providers of high-risk AI systems, and under Art. 4a(2) deployers and providers/deployers of other AI systems, to exceptionally process special-category personal data strictly necessary for bias detection and correction under Art. 10(2)(f)-(g), subject to stated safeguards. observed
  8. Probable EFTA EEA-Lex factsheet (DSA) — Regulation (EU) 2026/1744 (Digital Omnibus on AI) — Entered into force 27 July 2026 (published in the OJ 24 July 2026); postpones AI Act high-risk-system obligations to 2 December 2027 for Annex III systems and 2 August 2028 for Annex I product-embedded systems. observed
  9. Probable European Commission — AI Omnibus enters into force — AI Act Art. 4a — Permits providers of high-risk AI systems, and under Art. 4a(2) deployers and providers/deployers of other AI systems, to exceptionally process special-category personal data strictly necessary for bias detection and correction under Art. 10(2)(f)-(g), subject to stated safeguards. observed
  10. Probable CJEU, Meta Platforms v Bundeskartellamt, C-252/21 — The EU AI Act has been marked by EFTA as a proposed act with possible EEA relevance and remains under EEA-EFTA scrutiny, with a draft Joint Committee Decision under consideration but not yet adopted. observed
  11. Probable Praxikon — Regulation (EU) 2026/1744 (Digital Omnibus on AI) — Entered into force 27 Jul 2026, postponing AI Act Annex III high-risk obligations to 2 Dec 2027 and Annex I to 2 Aug 2028; Art.50 transparency obligations remain from 2 Aug 2026 (grace period to 2 Dec 2026 for pre-existing systems under Art.50(2)); re-verified against the Commission's own timeline and unchanged since the 2026-09-15 calibration baseline. observed
  12. Confirmed European Commission — AI Omnibus enters into force — AI Act as amended by Digital Omnibus (Regulation (EU) 2026/1744) — Postponed Annex III high-risk AI obligations to 2 December 2027 and Annex I to 2 August 2028; Art 50 transparency duties have applied since 2 August 2026 with a watermarking grace period to 2 December 2026. None of this yet binds Iceland, Liechtenstein or Norway, since the AI Act itself is not EEA-incorporated. observed

#

Core Article 8 mechanism is well-established law, but dedicated children's-data guidelines remain in development and several sub-areas (age verification specifics, education settings, dependent adults) lack direct 2026 sourcing in this pass.

Primary frameworkGDPR Article 8 (Regulation (EU) 2016/679)
Traffic-light rationale — AmberCore Article 8 mechanism is well-established law, but dedicated children's-data guidelines remain in development and several sub-areas (age verification specifics, education settings, dependent adults) lack direct 2026 sourcing in this pass.

Sub-modules (5)

Category narrative 198 words

Under Art. 8(1) GDPR, the default digital age of consent for the direct offer of Information Society Services (ISS) to a child is 16 years, with an opening clause allowing Member States to set a lower threshold not below 13 years. Across the 30 EEA states, national thresholds span the full 13–16 range (e.g., 13 in Belgium, Denmark, Estonia, Finland, Latvia, Malta, Norway, Portugal, Sweden; 14 in Austria, Bulgaria, Cyprus, Italy, Lithuania, Spain; 15 in Czechia, France, Greece, Slovenia; 16 in Croatia, Germany, Hungary, Ireland, Liechtenstein, Luxembourg, Netherlands, Poland, Romania, Slovakia). Beyond Art. 8 consent, the Digital Services Act (Regulation (EU) 2022/2065) imposes directly applicable Union-wide child protection rules on all online platforms accessible to minors: Art. 28(1) DSA requires providers to ensure a high level of privacy, safety, and security of minors by design (amplified by the European Commission's Article 28(4) DSA Guidelines on Protection of Minors and the EU privacy-preserving age-verification blueprint released in July 2025), and Art. 28(2) DSA imposes an absolute prohibition on presenting advertisements based on profiling (as defined in Art. 4(4) GDPR) using personal data of a recipient when the platform is aware with reasonable certainty that the recipient is a minor.

Sources and claims (2)
  1. Confirmed European Parliament Legislative Train Schedule — Article 8 GDPR sets a default minimum age of 16 for a child to consent to processing in relation to information-society services, permitting Member States to lower this threshold by law to no less than 13 years, with parental-responsibility-holder consent required below the applicable age. observed
  2. Confirmed EDPB — The EDPB's 2026-2027 work programme includes the development of dedicated Guidelines on children's data as one of its Pillar I harmonisation priorities. observed

#

Enforcement powers are broad, actively used at scale (billion-euro-class fines), collective redress mechanisms are in force, and a further procedural-harmonisation regulation is already adopted (pending 2027 application).

Primary frameworkGDPR Articles 77-84, 58, 83 (Regulation (EU) 2016/679); Regulation (EU) 2025/2518; Directive (EU) 2020/1828
Traffic-light rationale — GreenEnforcement powers are broad, actively used at scale (billion-euro-class fines), collective redress mechanisms are in force, and a further procedural-harmonisation regulation is already adopted (pending 2027 application).

Sub-modules (6)

Category narrative 334 words

Under Art. 83 GDPR, administrative fine ceilings are €10 million or 2% of total worldwide annual turnover (Art. 83(4)) and €20 million or 4% of total worldwide annual turnover (Art. 83(5)–(6)). In three landmark judgments — Case C-807/21 Deutsche Wohnen (5 December 2023), Case C-383/23 ILVA A/S (13 February 2025), and Case C-768/21 (26 September 2024) — the CJEU confirmed that: (1) a legal person can only be fined under Art. 83 if the infringement was committed intentionally or negligently; (2) the concept of 'undertaking' for calculating the 2%/4% turnover ceiling AND for determining the actual proportionate fine amount under Art. 83(1) corresponds to the EU competition-law concept of an economic unit (Arts. 101–102 TFEU), meaning parent-group global turnover governs; and (3) a DPA is not strictly obliged to impose a fine for every established infringement where a reprimand or corrective measure under Art. 58(2) suffices. Cross-border enforcement under the Art. 56/60 One-Stop-Shop is overhauled by Regulation (EU) 2025/2518 of 26 November 2025 (entered into force 1 January 2026; applicable from 2 April 2027), which sets binding 15-month investigation deadlines for simple/standard cross-border cases (extendable by 12 months for complex cases), early-resolution mechanisms, and harmonised complainant and party procedural rights. Cumulative EEA GDPR fines exceed €5.8 billion, led by Meta (€1.2bn, May 2023; €251m, Dec 2024), Amazon (€746m), TikTok (€530m by Irish DPC on 2 May 2025 for China data transfers; €345m in Sept 2023), LinkedIn (€310m, Oct 2024), and Uber (€290m by Dutch AP, Aug 2024). Private redress is governed by Art. 82 GDPR (compensation for material or non-material damage under CJEU Cases C-300/21 Österreichische Post, C-340/21 Natsionalna agentsia za prihodite, and C-507/23 Patēriētāju tiesību aizsardzības centrs of 4 October 2024 confirming an apology alone cannot replace financial compensation where damage is proven but an infringement alone does not automatically equal damage) and by opt-in/opt-out collective actions under Art. 80 GDPR and the Representative Actions Directive (EU) 2020/1828 (confirmed in CJEU Case C-757/22 Meta Platforms Ireland v Verbraucherzentrale Bundesverband of 11 July 2024).

Sources and claims (11)
  1. Confirmed European Parliament Legislative Train Schedule — GDPR Article 83 authorises fines for certain violations of up to 4% of an undertaking's total global annual turnover of the preceding financial year or €20 million, whichever is greater. observed
  2. Confirmed European Parliament Legislative Train Schedule — Ireland's Data Protection Commission imposed a record €1.2 billion fine on Meta Ireland in May 2023 over unlawful EU-US data transfers, the largest GDPR fine to date, alongside orders to suspend future transfers and cease unlawful US processing of EEA users' data. observed
  3. Confirmed EDPB — The Czech supervisory authority's appellate decision confirmed a first-instance fine of approximately €13.9 million against a controller for infringing Articles 6 and 13(1) GDPR over the transfer of antivirus-software users' browsing data to a sister company. observed
  4. Confirmed European Parliament Legislative Train Schedule — CNIL fined IQVIA €5 million over health-data violations, and Ireland's DPC separately fined WhatsApp Ireland €5.5 million for transparency and consent failures in its Terms of Service, illustrating continued multi-jurisdictional enforcement momentum. observed
  5. Confirmed European Parliament Legislative Train Schedule — The European Commission identified fragmented national procedures and limited DPA resourcing as factors hindering effective cross-border GDPR enforcement, a key motivation for the new procedural regulation (EU) 2025/2518. observed
  6. Confirmed Publications Office of the EU — Directive (EU) 2020/1828 on representative actions for the protection of the collective interests of consumers, applicable in Member States since 25 June 2023, empowers qualified entities to bring both injunctive and redress collective actions against traders for infringements including, where available under national or EU law, data protection. observed
  7. Confirmed European Parliament Legislative Train Schedule — Complaints filed in May 2018 by advocacy group NOYB under Articles 77-79/82 GDPR underpinned the enforcement chain leading to the Irish DPC's Meta Facebook, Instagram and WhatsApp fines, and NOYB has indicated it intends to challenge the EU-US Data Privacy Framework adequacy decision before the CJEU. observed
  8. Confirmed European Parliament Legislative Train Schedule — On 11 February 2026, the EDPB and EDPS adopted Joint Opinion 2/2026 on the Digital Omnibus Regulation proposal, supporting simplification aims while urging co-legislators not to adopt the proposed narrowing of the GDPR's personal-data definition. observed
  9. Confirmed EDPB — On 7 July 2026, the EDPB published draft Guidelines 02/2026 on Anonymisation for public consultation (open until 30 October 2026), responding to the CJEU's September 2025 EDPS v SRB ruling. observed
  10. Confirmed EDPB — On 19 March 2026, the EDPB launched its 2026 Coordinated Enforcement Framework action, with 25 participating DPAs assessing controller compliance with GDPR transparency and information obligations (Articles 12-14). observed
  11. Probable Gibson Dunn — EDPB Guidelines 04/2026 set out a five-step methodology for deciding whether to impose a GDPR administrative fine, adopted 17 September 2026 and open for public consultation until 13 November 2026. observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 58 sub-module(s), 91 claim(s) (91 category placement(s)), 66 source(s) in the cumulative register.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (37 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsaccess right
Art. 14Data Subject Rightsaccess right
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrectification and erasure
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy granted
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacytransfer mechanisms
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties