Data Protection Monitor
Global Privacy & Data Protection Intelligence

Not every instrument is backed by its official text yet. At least one law or rulebook covered here has no official source (tier 1) retrieved for it yet. No finding on this page is shown with confidence above “Probable” until stronger sources are retrieved.

Washington State, USA Data Protection & Privacy Regulation

US-WA schema gdpri-v2 trajectory: not yet assessed hybrid regime overlaps: artificial-intelligence

Last updated · 10 categories · 55 claims · 43 sources in the cumulative register

Washington State's data-protection picture this cycle is defined not by new legislation but by the widening practical reach of an existing sectoral statute.

Data collected Data published

AI-assembled from cited sources

Not covered: Children & Vulnerable Groups. Not fully checked this cycle: Data Subject Rights, Algorithmic, Biometric & Surveillance Governance (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 11 binding instruments
Next milestone
JAN12027
Washington comprehensive privacy bill (Peoples Privacy Act / HB 1671 successor) potential renewed consideration in the 2027 legislative session
Record & confidence mix55 claims · 36 sources · machine-compiled
52 Probable3 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: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

United States federal law that applies in Washington State, USA is covered once, on the United States page. This page covers Washington State, USA’s own layer: its own law, regulators and enforcement.

Jurisdiction brief

Latest update · 8 November 2026

Lead Signal

Washington's Attorney General has, for the first time, put an official number on a long-observed structural fact: the state's own August 2026 Data Privacy Report states that Washington has no comprehensive consumer-privacy statute, and that privacy protection in the state is instead assembled from targeted laws covering consumer health data, student data, biometric data, driver data, and electronic reader systems. That self-assessment from the enforcing authority itself is a meaningful marker, because it frames the sectoral patchwork not as an oversight observers have noted from outside but as a gap the regulator is naming for its own legislative-advocacy purposes.

Key regulatory facts for Washington State, USA
Key regulatory facts for Washington State, USA
Regulatory DimensionWashington State, USA Standing Position
JurisdictionWashington State, USA (US-WA)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 55 sourced findings)
Regulator & FrameworkReal, enforceable sectoral obligations exist (MHMDA, biometric law, breach notice) but there is no general omnibus statute or dedicated DPA — coverage is fragmented and health/biometric-centric.
Lawful Processing & Special DataRobust consent/necessity rules exist for health and biometric data specifically, but no general lawful-basis framework covers personal data broadly.
Data Subject RightsMeaningful rights exist but are scoped narrowly to consumer health data rather than personal data generally.
Controller/Processor DutiesBreach notification and MHMDA privacy-policy disclosure are binding; broader GDPR-style controller/processor accountability apparatus (DPIA, DPO, ROPA, security-measures mandates) is absent.
Primary Instruments CitedIAPP, OneTrust DataGuidance, IAPP, IAPP, Washington State, USA Official Instrument (iapp.org washingtons-attorney-general-ref)
Last Confirmed / Updated (43 sources in cumulative register)

#

Real, enforceable sectoral obligations exist (MHMDA, biometric law, breach notice) but there is no general omnibus statute or dedicated DPA — coverage is fragmented and health/biometric-centric.

Primary frameworkMy Health My Data Act (HB 1155); Washington Biometric Privacy Protection Act (RCW 19.375); Washington data-breach notification statute; federal FTC Act Section 5 baseline — no comprehensive consumer-privacy statute in force
Traffic-light rationale — AmberReal, enforceable sectoral obligations exist (MHMDA, biometric law, breach notice) but there is no general omnibus statute or dedicated DPA — coverage is fragmented and health/biometric-centric.

Sub-modules (5)

Regulator and authorityAmber

The WA AG enforces sectoral privacy statutes; there is no privacy-specific regulator or DPA.

Claims (3):

  • Washington State has no dedicated data-protection supervisory authority; the Washington State Attorney General enforces sectoral privacy statutes, including the My Health My Data Act, under its consumer-protection enforcement powers.
  • Washington Attorney General Nick Brown — Washington is 'behind where we should be' on comprehensive privacy legislation and no comprehensive bill is expected to be introduced in 2027; his office continues to rely on the CPA and targeted sectoral statutes.
  • Washington Attorney General — Washington is 'behind where we should be' on comprehensive privacy legislation and lawmakers are not expected to introduce comprehensive privacy legislation next year, while defending the office's measured enforcement approach under MHMDA.

Act and instrumentsAmber

Sectoral instruments (MHMDA, biometric law, breach law) exist; the comprehensive Washington Privacy Act never passed.

Claims (5):

  • Washington's data-protection landscape is sectoral rather than comprehensive, anchored by the My Health My Data Act (enacted 27 April 2023), the Washington Biometric Privacy Protection Act (RCW 19.375, effective 23 July 2017), and the state's general data-breach notification statute.
  • Washington never enacted a GDPR/CCPA-style comprehensive consumer privacy statute; the Washington Privacy Act, which served as a model for several other states' comprehensive privacy laws, failed repeatedly in the Washington legislature and was never signed into law.
  • HB 1671 (Protecting personal data privacy) — Reintroduced for the 2026 session on 12 January 2026 and remains in House Appropriations without further committee action.
  • Washington State — No comprehensive consumer-privacy statute; targeted laws only.
  • Washington has no comprehensive consumer-privacy statute per the AG's own August 2026 Data Privacy Report; coverage is targeted/sectoral.

Material scopeAmber

MHMDA's broad definitions bring a wide range of data/entities into scope.

Claims (1):

  • The My Health My Data Act's broad definitions of 'consumer,' 'covered data' and 'health care services' bring a wide range of data types and entities into scope.

Territorial scopeAmber

MHMDA applies extraterritorially to out-of-state businesses processing WA consumers' health data per AG guidance.

Claims (1):

  • The Washington Attorney General's My Health My Data Act FAQ specifically addresses the law's impact on businesses located outside Washington State, indicating extraterritorial application to entities processing Washington consumers' health data.

Regulator registration and filingAmber

No registration/filing regime; MHMDA requires a published consumer health data privacy policy instead.

Claims (1):

  • The My Health My Data Act does not require regulatory registration or filing with the Attorney General, but does require regulated entities to publish a consumer health data privacy policy disclosing categories of data collected, purposes, and third-party sharing.
Category narrative 102 words

Washington State has no dedicated data-protection regulator and no comprehensive omnibus consumer-privacy statute. The Washington State Attorney General enforces sectoral privacy laws — principally the My Health My Data Act (HB 1155, 2023) and the Washington Biometric Privacy Protection Act (RCW 19.375, 2017) — under its general Consumer Protection Act authority. The influential Washington Privacy Act (WaPA), which served as a legislative template copied by Virginia, Colorado and other states, was itself never enacted in Washington despite multiple attempts (2019–2022). The federal FTC Act Section 5 unfair/deceptive-practices authority applies as a national baseline. This is a sectoral patchwork, not an omnibus regime.

Periodic update · new data 2026-11-08

Washington's Attorney General has made explicit, in the state's own August 2026 Data Privacy Report, what the regulatory landscape has long implied: Washington has no comprehensive consumer-privacy statute. Privacy protection in the state is instead built from a set of targeted laws, each addressing a specific category of data or activity: consumer health data, student data, biometric data, driver data, and electronic reader systems. There is no single omnibus framework comparable to the general consumer-privacy statutes enacted in a growing number of other states, and no single regulator-administered rulemaking track of the kind an omnibus statute typically creates. Enforcement authority over the existing sectoral statutes sits with the Attorney General, operating through the targeted statutes themselves and, where a sectoral law ties into it, through the state's general Consumer Protection Act.

The report's framing matters beyond its descriptive content: it reads as the Attorney General's own positioning for future legislative advocacy, naming the absence of an omnibus statute as a structural gap rather than treating the current patchwork as complete. No draft legislation or active consultation toward an omnibus statute was identified in this record, so this remains a named gap rather than a pending reform.

Outlook

The most likely forward path signalled by the Attorney General's own report is legislative advocacy toward a comprehensive privacy statute, though no specific bill has been identified as in progress. Future reporting cycles should watch for any legislative proposal responding to the report's framing.

Sources and claims (11)
  1. Probable IAPP — Washington State has no dedicated data-protection supervisory authority; the Washington State Attorney General enforces sectoral privacy statutes, including the My Health My Data Act, under its consumer-protection enforcement powers. observed
  2. Probable OneTrust DataGuidance — Washington's data-protection landscape is sectoral rather than comprehensive, anchored by the My Health My Data Act (enacted 27 April 2023), the Washington Biometric Privacy Protection Act (RCW 19.375, effective 23 July 2017), and the state's general data-breach notification statute. observed
  3. Probable IAPP — Washington never enacted a GDPR/CCPA-style comprehensive consumer privacy statute; the Washington Privacy Act, which served as a model for several other states' comprehensive privacy laws, failed repeatedly in the Washington legislature and was never signed into law. observed
  4. Probable IAPP — The My Health My Data Act's broad definitions of 'consumer,' 'covered data' and 'health care services' bring a wide range of data types and entities into scope. observed
  5. Probable IAPP — The Washington Attorney General's My Health My Data Act FAQ specifically addresses the law's impact on businesses located outside Washington State, indicating extraterritorial application to entities processing Washington consumers' health data. observed
  6. Probable IAPP — The My Health My Data Act does not require regulatory registration or filing with the Attorney General, but does require regulated entities to publish a consumer health data privacy policy disclosing categories of data collected, purposes, and third-party sharing. observed
  7. Probable https://iapp.org/news/a/washingtons-attorney-general-reflects-on-states-privacy-legislation-and-enforcement — Washington Attorney General Nick Brown — Washington is 'behind where we should be' on comprehensive privacy legislation and no comprehensive bill is expected to be introduced in 2027; his office continues to rely on the CPA and targeted sectoral statutes.
  8. Probable Washington State Attorney General's Office — HB 1671 (Protecting personal data privacy) — Reintroduced for the 2026 session on 12 January 2026 and remains in House Appropriations without further committee action. observed
  9. Probable Washington State Office of Attorney General — Washington Attorney General — Washington is 'behind where we should be' on comprehensive privacy legislation and lawmakers are not expected to introduce comprehensive privacy legislation next year, while defending the office's measured enforcement approach under MHMDA. observed
  10. Probable Washington State Attorney General's Office — Washington State — No comprehensive consumer-privacy statute; targeted laws only. observed
  11. Probable Washington State Attorney General's Office — Washington has no comprehensive consumer-privacy statute per the AG's own August 2026 Data Privacy Report; coverage is targeted/sectoral. observed

#

Robust consent/necessity rules exist for health and biometric data specifically, but no general lawful-basis framework covers personal data broadly.

Primary frameworkMy Health My Data Act consent/necessity framework; Washington Biometric Privacy Protection Act (RCW 19.375)
Traffic-light rationale — AmberRobust consent/necessity rules exist for health and biometric data specifically, but no general lawful-basis framework covers personal data broadly.

Sub-modules (4)

Lawful basesAmber

Consent-or-necessity standard under MHMDA; no general lawful-basis enumeration exists.

Claims (1):

  • The My Health My Data Act permits collection of consumer health data only on the basis of consumer consent or a defined necessity standard; Washington has no broader enumerated set of lawful bases for personal data generally.

Special categoriesAmber

Consumer health data (including reproductive/gender-affirming care data) and biometric identifiers are treated as specially protected categories under two separate statutes.

Claims (2):

  • The My Health My Data Act treats broadly defined 'consumer health data' as a specially protected category, filling a gap left by HIPAA's narrower scope, which does not reach data from many apps, wearables, and non-covered entities.
  • Washington's Biometric Privacy Protection Act (RCW 19.375, effective 23 July 2017) separately imposes notice-and-consent requirements on private entities enrolling a person's biometric identifiers in a database for commercial purposes, and the MHMDA additionally treats biometric data as consumer health data subject to its own private right of action.

Pseudonymisation and anonymisationAmber

MHMDA defines 'deidentified data' with litigation-risk uncertainty around the standard's application.

Claims (1):

  • The My Health My Data Act defines 'deidentified data' among its core terms, though the Act's broad definitions and private right of action create litigation risk around what qualifies as properly deidentified data.
Category narrative 56 words

Washington has no general enumerated set of lawful bases for processing personal data akin to GDPR Art 6. Instead, the My Health My Data Act imposes a consent-or-necessity standard specific to consumer health data, with heightened written-authorization requirements for sale, and Washington's Biometric Privacy Protection Act imposes separate notice-and-consent duties for commercial enrollment of biometric identifiers.

Sources and claims (6)
  1. Probable IAPP — The My Health My Data Act permits collection of consumer health data only on the basis of consumer consent or a defined necessity standard; Washington has no broader enumerated set of lawful bases for personal data generally. observed
  2. Probable IAPP — Under the My Health My Data Act, sharing consumer health data requires separate consent or satisfaction of the necessity standard, and selling consumer health data requires specific prior written and signed authorization from the consumer. observed
  3. Probable IAPP — The My Health My Data Act treats broadly defined 'consumer health data' as a specially protected category, filling a gap left by HIPAA's narrower scope, which does not reach data from many apps, wearables, and non-covered entities. observed
  4. Probable Federal Trade Commission — Washington's Biometric Privacy Protection Act (RCW 19.375, effective 23 July 2017) separately imposes notice-and-consent requirements on private entities enrolling a person's biometric identifiers in a database for commercial purposes, and the MHMDA additionally treats biometric data as consumer health data subject to its own private right of action. observed
  5. Probable OneTrust DataGuidance — The My Health My Data Act defines 'deidentified data' among its core terms, though the Act's broad definitions and private right of action create litigation risk around what qualifies as properly deidentified data. observed
  6. Probable RecordingLaw.com — MHMDA requires separate consent for collection, separate consent for sharing, and signed authorization for sale of consumer health data. observed

#

Meaningful rights exist but are scoped narrowly to consumer health data rather than personal data generally.

Primary frameworkMy Health My Data Act consumer rights (access, deletion, consent withdrawal)
Traffic-light rationale — AmberMeaningful rights exist but are scoped narrowly to consumer health data rather than personal data generally.

Sub-modules (5)

Access rightAmber

MHMDA grants a right to confirm and access whether/how health data is collected, shared or sold.

Claims (1):

  • The My Health My Data Act grants consumers the right to confirm whether a regulated entity is collecting, sharing, or selling their consumer health data, and to access that data.

Rectification and erasureAmber

MHMDA grants rights to withdraw consent and to delete consumer health data.

Claims (1):

  • The My Health My Data Act grants consumers the right to access, delete, and withdraw consent from the collection, sharing, or sale of their health data.

Restriction and objectionRed

No general restriction/objection right beyond MHMDA's consent-withdrawal mechanism was identified.

Data portabilityRed

No statutory data-portability right exists under Washington law.

Deadlines and response windowsRed

No specific numeric statutory response-window for MHMDA rights requests was confirmed in available sources.

Claims (1):

  • My Health My Data Act (RCW 19.373) — Regulated entities must respond to consumer health-data rights requests within 45 days, with one possible 45-day extension.
Category narrative 45 words

Data subject rights in Washington are confined to the health-data context under MHMDA: consumers have rights to confirm/access, withdraw consent, and delete consumer health data. There is no general right to restrict processing, no data-portability right, and no statutory deadline framework outside MHMDA's health-data scope.

Sources and claims (3)
  1. Probable OneTrust DataGuidance — The My Health My Data Act grants consumers the right to confirm whether a regulated entity is collecting, sharing, or selling their consumer health data, and to access that data. observed
  2. Probable IAPP — The My Health My Data Act grants consumers the right to access, delete, and withdraw consent from the collection, sharing, or sale of their health data. observed
  3. Probable Ashurst Perkins Coie — My Health My Data Act (RCW 19.373) — Regulated entities must respond to consumer health-data rights requests within 45 days, with one possible 45-day extension. observed

#

Breach notification and MHMDA privacy-policy disclosure are binding; broader GDPR-style controller/processor accountability apparatus (DPIA, DPO, ROPA, security-measures mandates) is absent.

Primary frameworkWashington data-breach notification statute; My Health My Data Act privacy-policy disclosure duty
Traffic-light rationale — AmberBreach notification and MHMDA privacy-policy disclosure are binding; broader GDPR-style controller/processor accountability apparatus (DPIA, DPO, ROPA, security-measures mandates) is absent.

Sub-modules (7)

Accountability & DPIARed

No general DPIA/accountability-principle statute identified for Washington.

DPO requirementsRed

No DPO appointment requirement identified under Washington law.

Ropa requirementsAmber

MHMDA's mandatory published consumer health data privacy policy functions as a public-facing analogue to a record of processing.

Claims (1):

  • The My Health My Data Act requires regulated entities to maintain and publish a consumer health data privacy policy disclosing categories of data collected, sources, purposes, and third parties with whom data is shared.

Joint controller arrangementsRed

No joint-controller concept defined in Washington law.

Security measuresRed

No general Washington statute mandates specific technical/organizational security measures beyond breach-notification triggers.

Breach notificationAmber

Washington maintains a general data-breach notification statute, amended over time to strengthen requirements.

Claims (2):

  • Washington maintains a general data-breach notification statute requiring entities to notify affected state residents (and, above certain thresholds, the Attorney General) following breaches of specified personal information; the law has been amended over time to strengthen notification requirements.
  • Agencies must notify the AG within 30 days for breaches affecting >500 WA residents, and affected individuals within the same 30-day window.

Retention and disposalRed

No specific statutory retention limit for general personal data was identified.

Category narrative 49 words

There is no general accountability/DPIA, DPO, ROPA, joint-controller, or security-measures regime in Washington law outside sector-specific requirements. Washington's general data-breach notification statute requires notification of breaches of specified personal information, and MHMDA requires regulated entities to publish a consumer health data privacy policy that functions as a quasi-ROPA disclosure.

Sources and claims (3)
  1. Probable National Association of Attorneys General — Washington maintains a general data-breach notification statute requiring entities to notify affected state residents (and, above certain thresholds, the Attorney General) following breaches of specified personal information; the law has been amended over time to strengthen notification requirements. observed
  2. Probable OneTrust DataGuidance — The My Health My Data Act requires regulated entities to maintain and publish a consumer health data privacy policy disclosing categories of data collected, sources, purposes, and third parties with whom data is shared. observed
  3. Probable Washington State Office of Attorney General — Agencies must notify the AG within 30 days for breaches affecting >500 WA residents, and affected individuals within the same 30-day window. observed

#

Five of six sub-modules represent a genuine regulatory gap; only one MHMDA-derived proxy mechanism exists.

Primary frameworkMy Health My Data Act sale/sharing authorization requirement (partial proxy only)
Traffic-light rationale — RedFive of six sub-modules represent a genuine regulatory gap; only one MHMDA-derived proxy mechanism exists.

Sub-modules (6)

Transfer mechanismsAmber

MHMDA's consent/authorization rules for sharing/selling health data function as the state's primary transfer control.

Claims (1):

  • Washington State has no dedicated cross-border data-transfer mechanism regime; the My Health My Data Act's consent/authorization requirements for sharing and selling consumer health data function as the state's primary control on transfers of that data to third parties, wherever located.

Adequacy receivedRed

Not applicable/no finding — Washington is a US state, not a jurisdiction subject to adequacy determinations.

Adequacy grantedRed

Not applicable — no WA-specific adequacy-granting mechanism exists.

SCCs and BCRsRed

No SCC/BCR framework exists under Washington law.

Transfer impact assessmentRed

No TIA requirement identified under Washington law.

Data localisationRed

No data-localisation mandate identified under Washington law.

Category narrative 44 words

Washington has no state-level adequacy, SCC, BCR, transfer-impact-assessment, or data-localisation regime. The only WA-specific control affecting data transfers is MHMDA's consent/authorization requirement for 'sharing' and 'selling' consumer health data, which functions as a de facto transfer gate for that data category regardless of destination.

Sources and claims (1)
  1. Probable IAPP — Washington State has no dedicated cross-border data-transfer mechanism regime; the My Health My Data Act's consent/authorization requirements for sharing and selling consumer health data function as the state's primary control on transfers of that data to third parties, wherever located. observed

#

Strong health-sector overlay exists; other sectors rely entirely on federal law with no WA-specific supplement identified.

Primary frameworkMy Health My Data Act (health-sector overlay)
Traffic-light rationale — AmberStrong health-sector overlay exists; other sectors rely entirely on federal law with no WA-specific supplement identified.

Sub-modules (7)

Financial sector overlayRed

No WA-specific financial-sector privacy overlay identified; federal GLBA applies as baseline.

Health sector overlayGreen

MHMDA fills HIPAA gaps for non-covered health-data collectors.

Claims (3):

  • The My Health My Data Act was enacted specifically to close gaps left by the federal HIPAA framework, which does not reach a substantial share of health-related data collected by non-covered entities such as wearables, apps and consumer-facing health platforms.
  • My Health My Data Act (RCW 19.373) — Applies to any business handling the consumer health data of a Washington resident with no revenue or data-volume threshold, extending beyond HIPAA's reach.
  • MHMDA reaches entities and data types HIPAA does not cover, including a geofencing prohibition near health facilities.

Telecoms and eprivacyRed

No WA-specific telecoms/ePrivacy overlay identified.

Employment dataRed

No WA-specific employment-data privacy overlay identified.

Credit and scoringRed

No WA-specific credit/scoring privacy overlay identified; federal FCRA applies as baseline.

educationRed

No WA-specific education-sector privacy overlay identified.

insuranceRed

No WA-specific insurance-sector privacy overlay identified.

Category narrative 54 words

The My Health My Data Act is Washington's flagship sectoral overlay, enacted specifically to close gaps left by HIPAA for non-covered health-data collectors (apps, wearables, websites). No WA-specific overlays for financial services, telecoms/ePrivacy, employment, credit-scoring, education, or insurance were identified beyond generally applicable federal sectoral law (GLBA, FCRA, etc., addressed at the US-federal JID).

Periodic update · new data 2026-11-04

The General Motors OnStar Smart Driver settlement has surfaced a gap in Washington's sectoral coverage of connected-vehicle data. General Motors is understood to have sold driver behavior and location data collected through its OnStar Smart Driver program between 2016 and 2024 to data brokers, who resold that data to insurers for use in setting rates, without adequate disclosure to or consent from drivers. Washington, together with Oregon, co-led a 36-state attorney general coalition that reached a $220 million settlement with General Motors, with Washington's share set at approximately $12.3 million.

What is notable from a sectoral standpoint is the absence of any Washington statute comparable to the EU Data Act that would specifically govern access to and sharing of connected-product data. The case against General Motors was pursued instead under general unfair-and-deceptive-practices consumer-protection authority. This indicates that connected-vehicle and similar data-broker arrangements currently sit outside any dedicated access-and-sharing regime in the state and are instead captured, when captured at all, through broader consumer-protection enforcement.

Outlook

It remains unresolved whether this settlement will prompt a Washington-specific legislative response, such as a connected-vehicle data bill, in the 2027 legislative session. Absent such a development, connected-vehicle and data-broker practices of this kind will likely continue to be addressed primarily through general consumer-protection enforcement rather than a sector-specific access-and-sharing statute.

Sources and claims (4)
  1. Probable IAPP — The My Health My Data Act was enacted specifically to close gaps left by the federal HIPAA framework, which does not reach a substantial share of health-related data collected by non-covered entities such as wearables, apps and consumer-facing health platforms. observed
  2. Probable PrivacyTerms.io — My Health My Data Act (RCW 19.373) — Applies to any business handling the consumer health data of a Washington resident with no revenue or data-volume threshold, extending beyond HIPAA's reach. observed
  3. Probable Washington State Office of Attorney General — Washington State — Washington has no connected-product data-access-and-sharing statute analogous to the EU Data Act; the GM Smart Driver settlement was brought under general unfair/deceptive-practices consumer-protection authority rather than any sector-specific data-sharing right. observed
  4. Probable RecordingLaw.com — MHMDA reaches entities and data types HIPAA does not cover, including a geofencing prohibition near health facilities. observed

#

Indirect adtech controls exist only through MHMDA's health-data sale/sharing rules; no general commercial-privacy adtech regime exists.

Primary frameworkMy Health My Data Act sale/sharing authorization requirement (health-data scope only)
Traffic-light rationale — AmberIndirect adtech controls exist only through MHMDA's health-data sale/sharing rules; no general commercial-privacy adtech regime exists.

Sub-modules (6)

Cookies and trackersAmber

MHMDA's 'sell' definition can capture third-party cookie/pixel-based sharing of health-derived data.

Claims (1):

  • The My Health My Data Act's broad definition of 'sell' can capture disclosure of health-derived data gathered via third-party cookies, pixels, and tags to service providers, triggering the Act's prior-authorization requirement.

Dark patternsRed

No WA-specific dark-pattern prohibition identified.

Opt out signalsRed

No WA-specific universal opt-out signal (GPC-equivalent) mandate identified.

Clean rooms and dcrRed

No WA-specific clean-room/data-collaboration-room rule identified.

Cross context advertisingRed

No CCPA-style 'sale'/'share' cross-context advertising regime exists generally; only MHMDA's health-data-specific sale rule applies.

Direct marketingAmber

MHMDA's sale-authorization requirement constrains health-data-driven direct marketing.

Claims (1):

  • By restricting the sale of consumer health data absent specific consumer authorization, the My Health My Data Act indirectly constrains health-data-driven direct marketing and advertising practices in Washington.
Category narrative 28 words

Washington has no dedicated cookie-consent, dark-pattern, opt-out-signal, or clean-room statute. MHMDA's broad 'sell' definition indirectly reaches health-data monetization via third-party cookies/pixels/tags and constrains health-data-driven direct marketing absent authorization.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (2)
  1. Probable IAPP — The My Health My Data Act's broad definition of 'sell' can capture disclosure of health-derived data gathered via third-party cookies, pixels, and tags to service providers, triggering the Act's prior-authorization requirement. observed
  2. Probable IAPP — By restricting the sale of consumer health data absent specific consumer authorization, the My Health My Data Act indirectly constrains health-data-driven direct marketing and advertising practices in Washington. observed

#

Biometric and facial-recognition governance is comparatively mature; general algorithmic/ADM/AI-risk-assessment and genetic-data governance is absent.

Primary frameworkWashington Biometric Privacy Protection Act (RCW 19.375); SB 6280 facial-recognition regulation; MHMDA biometric-as-health-data treatment
Traffic-light rationale — AmberBiometric and facial-recognition governance is comparatively mature; general algorithmic/ADM/AI-risk-assessment and genetic-data governance is absent.

Sub-modules (6)

Profiling restrictionsRed

No WA-specific profiling-restriction statute identified.

Automated decision making transparencyRed

No WA-specific ADM-transparency statute identified.

AI risk assessmentsRed

No WA-specific AI-risk-assessment statute (unlike Colorado's AI Act) identified.

Claims (2):

  • Washington Attorney General Nick Brown — Despite Washington's AI Task Force completing its work, Brown does not currently anticipate an AG-request bill addressing artificial intelligence for the 2027 legislative session.
  • HB 1170 (AI content provenance disclosure) — AI content-provenance disclosure requirement, effective 1 February 2027 (not yet commenced).

Biometric regimeGreen

RCW 19.375 imposes notice-and-consent duties for commercial biometric-identifier enrollment; MHMDA separately treats biometric data as consumer health data.

Claims (5):

  • The Washington Biometric Privacy Protection Act (RCW 19.375, effective 23 July 2017) is one of the earliest state biometric statutes in the U.S., cited by the FTC as an example of state biometric regulation, and the My Health My Data Act separately treats biometric data as consumer health data subject to its private right of action.
  • RCW 19.375.020 / .030 — RCW 19.375.020 bars enrolling a biometric identifier in a database for a commercial purpose without first providing notice, obtaining consent, or providing an opt-out mechanism; RCW 19.375.030 limits enforcement to the Attorney General under the CPA (civil penalties up to $7,500 per violation), with no private right of action.
  • Washington maintains Chapter 19.375 RCW as a dedicated biometric-identifiers statute separate from and in addition to the My Health My Data Act.
  • RCW 19.375 (Biometric Identifiers) — Businesses must provide notice and obtain consent before enrolling biometric identifiers for a commercial purpose; AG enforcement penalties up to $7,500 per violation; no private right of action.
  • RCW 19.375 governs biometric data without a private right of action, per secondary sourcing not independently verified this cycle.

Genetic dataRed

No standalone WA genetic-data statute identified; genetic data is not explicitly confirmed as a distinct MHMDA/biometric-law category in sources retrieved.

State surveillance carveoutsAmber

SB 6280 (2020) regulates public and private facial-recognition technology use in Washington.

Claims (2):

  • In 2020, the Washington Legislature passed SB 6280, establishing regulations governing public and private-sector use of facial-recognition technology in the state.
  • SB 6002 (Driver Privacy Act) — ALPR data retention to 21 days.
Category narrative 69 words

Washington's Biometric Privacy Protection Act (RCW 19.375, 2017) was one of only three state biometric statutes for years and is cited by the FTC as an early state biometric-privacy model. MHMDA additionally treats biometric data as consumer health data subject to its private right of action. SB 6280 (2020) governs public/private facial-recognition technology use. No WA-specific profiling-restriction, ADM-transparency, AI-risk-assessment, or genetic-data statute (comparable to Colorado's AI Act) was identified.

No periodic updates recorded in this cycle

Sources and claims (9)
  1. Probable Federal Trade Commission — The Washington Biometric Privacy Protection Act (RCW 19.375, effective 23 July 2017) is one of the earliest state biometric statutes in the U.S., cited by the FTC as an example of state biometric regulation, and the My Health My Data Act separately treats biometric data as consumer health data subject to its private right of action. observed
  2. Probable IAPP — In 2020, the Washington Legislature passed SB 6280, establishing regulations governing public and private-sector use of facial-recognition technology in the state. observed
  3. Probable RecordingLaw — SB 6002 (Driver Privacy Act) — ALPR data retention to 21 days. observed
  4. Probable Tri-Cities Business News — Washington Attorney General Nick Brown — Despite Washington's AI Task Force completing its work, Brown does not currently anticipate an AG-request bill addressing artificial intelligence for the 2027 legislative session. observed
  5. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/washington-data-privacy-laws/biometric-privacy/ — RCW 19.375.020 / .030 — RCW 19.375.020 bars enrolling a biometric identifier in a database for a commercial purpose without first providing notice, obtaining consent, or providing an opt-out mechanism; RCW 19.375.030 limits enforcement to the Attorney General under the CPA (civil penalties up to $7,500 per violation), with no private right of action.
  6. Probable Ashurst Perkins Coie — Washington maintains Chapter 19.375 RCW as a dedicated biometric-identifiers statute separate from and in addition to the My Health My Data Act. observed
  7. Probable RecordingLaw — HB 1170 (AI content provenance disclosure) — AI content-provenance disclosure requirement, effective 1 February 2027 (not yet commenced). observed
  8. Probable RecordingLaw — RCW 19.375 (Biometric Identifiers) — Businesses must provide notice and obtain consent before enrolling biometric identifiers for a commercial purpose; AG enforcement penalties up to $7,500 per violation; no private right of action. observed
  9. Uncertain RecordingLaw.com — RCW 19.375 governs biometric data without a private right of action, per secondary sourcing not independently verified this cycle. observed

#

This is a legitimate, explicit regulatory gap: no WA-specific children's/vulnerable-groups privacy statute was located in this research.

Traffic-light rationale — RedThis is a legitimate, explicit regulatory gap: no WA-specific children's/vulnerable-groups privacy statute was located in this research.

Sub-modules (5)

Age verificationRed

No WA-specific age-verification statute identified.

Minor profiling bansRed

No WA-specific minor-profiling ban identified.

Claims (1):

  • Washington Attorney General Nick Brown — AG Brown will not seek renewed social-media-limitation legislation for minors because a multistate settlement with Meta secures comparable or stronger protections, including school-hours push-notification pauses, midnight-6am access blocks, an algorithmic-feed opt-off, and removal of cosmetic filters and like-counts for minors.

Education settingsRed

No WA-specific education-settings privacy rule identified.

Dependent adultsRed

No WA-specific dependent-adults data-protection provision identified.

Category narrative 57 words

No Washington state-specific statute establishing an age-of-consent threshold, parental-consent mechanism, minor-profiling ban, education-settings privacy rule, or dependent-adults protection was identified for the general privacy domain (as distinct from federal COPPA, which is addressed at the US-federal JID). Washington has no comprehensive privacy statute of the kind that in other states (e.g., Colorado, Connecticut) carries children's-privacy duty-of-care amendments.

No periodic updates recorded in this cycle

Sources and claims (1)
  1. Probable Route Fifty / Washington State Standard — Washington Attorney General Nick Brown — AG Brown will not seek renewed social-media-limitation legislation for minors because a multistate settlement with Meta secures comparable or stronger protections, including school-hours push-notification pauses, midnight-6am access blocks, an algorithmic-feed opt-off, and removal of cosmetic filters and like-counts for minors. observed

#

A strong private right of action and CPA enforcement mechanism exist and are actively used by plaintiffs; documented state AG enforcement activity and regulator capacity data are thin.

Primary frameworkMy Health My Data Act private right of action under Washington's Consumer Protection Act
Traffic-light rationale — AmberA strong private right of action and CPA enforcement mechanism exist and are actively used by plaintiffs; documented state AG enforcement activity and regulator capacity data are thin.

Sub-modules (6)

Regulator powers and penaltiesAmber

AG enforcement operates via the Consumer Protection Act; MHMDA violations are deemed to satisfy CPA elements automatically for private claims.

Claims (3):

  • Violations of the My Health My Data Act are enforceable both by the Washington Attorney General and by private plaintiffs under the state's Consumer Protection Act, which for private MHMDA claims dispenses with the CPA's usual requirement that plaintiffs prove the violation is an unfair/deceptive act, since any MHMDA violation is deemed to satisfy those elements.
  • My Health My Data Act (RCW 19.373) — A violation of MHMDA is a per se violation of the CPA; the AG may seek civil penalties up to $7,500 per violation, while private plaintiffs may obtain injunctive relief, actual damages, attorney fees, and treble damages up to $25,000.
  • My Health My Data Act (RCW 19.373) — A violation of MHMDA is a per se violation of the Washington Consumer Protection Act, enforceable by the Attorney General and through private action.

Enforcement activity indexRed

No documented WA AG enforcement actions or fines under MHMDA were identified as of August 2026.

Claims (3):

  • General Motors — GM $220M OnStar data-sale settlement; WA share ~$12.3M.
  • MHMDA enforcement activity — The first businesses sued under MHMDA include a cannabis retailer and Amazon's advertising business, not hospitals, indicating enforcement is reaching adtech-adjacent rather than traditional healthcare defendants first.
  • General Motors — Agreed to pay $220 million to settle allegations by 36 state AGs (co-led by Washington and Oregon) that it sold OnStar Smart Driver connected-vehicle data (2016-2024) to data brokers who resold it to insurers for rate-setting without adequate disclosure or consent; Washington's share is approximately $12.3 million, and GM must obtain express consent before future comparable data collection.

Regulator funding and capacityRed

No data on WA AG office budget/headcount specific to privacy enforcement was identified.

Collective redress and class actionsAmber

MHMDA is cited among newer state privacy statutes driving a surge in privacy class-action litigation.

Claims (3):

  • Washington's My Health My Data Act is cited among the newer state privacy statutes, alongside the CCPA and New Jersey's Daniel's Law, that plaintiffs increasingly use as grounds for privacy class-action litigation amid an overall surge in U.S. data-privacy lawsuits.
  • Washington Attorney General Nick Brown — Brown's office has been 'thoughtful about enforcement because the law is still relatively new,' explaining the relative absence of public AG enforcement actions despite an active private-litigation pipeline including a Feb 10, 2026 consumer class action against Amazon.com, Inc. and Amazon Advertising, LLC.
  • My Health My Data Act private right of action — Private pixel-tracking litigation against Washington businesses, including Amazon and Uncle Ike's.

Private right of actionAmber

MHMDA contains a broad, low-threshold private right of action with treble-damages exposure.

Claims (4):

  • The My Health My Data Act contains a broad private right of action enforceable under Washington's Consumer Protection Act, authorizing consumers to sue for a violation of any provision of the Act without a mitigating cure period, with potential recovery of actual damages, litigation costs, attorney's fees, and treble damages upon proof of injury.
  • My Health My Data Act / Washington Consumer Protection Act — Violations of the My Health My Data Act are per se violations of the Washington Consumer Protection Act, enforceable by both the Attorney General and through private consumer actions.
  • The My Health My Data Act gives Washington consumers a private right of action by making violations enforceable as per se violations of the Washington Consumer Protection Act.
  • MHMDA violations are per se CPA violations carrying a private right of action with treble damages capped at $25,000, plus a separate AG civil-penalty track up to $7,500 per violation.

Recent developments 180dAmber

No WA-specific MHMDA enforcement development within the last 180 days was identified; the most relevant recent development is the FTC's July 2026 federal Section 5 suit against Hims & Hers (joined by Utah and California), evidencing continued national health-privacy enforcement under the federal baseline applicable in Washington.

Claims (2):

  • In July 2026, the FTC, joined by Utah and California, filed suit against telehealth provider Hims & Hers alleging deceptive and unlawful sharing of consumers' sensitive health data, illustrating continued active federal Section 5 enforcement in the health-privacy space that forms part of the baseline regulatory backdrop applicable in Washington absent state-specific AG action in this window.
  • Washington State Attorney General — On Aug 14, 2026 the WA AG released the state's first-ever Data Privacy Report, noting 209 reported breaches in 2025 affecting more than 8 million residents (over 80% involving Social Security numbers), and recommending the Legislature enact a comprehensive consumer privacy statute, which WA currently lacks.
Category narrative 122 words

The My Health My Data Act's most consequential enforcement feature is its broad private right of action, enforceable under Washington's Consumer Protection Act, which dispenses with the CPA's usual burden of proving an unfair/deceptive act for MHMDA violations and allows treble damages upon proof of injury. Washington data-privacy litigation (including MHMDA-based claims) has grown amid a broader national surge in privacy class actions. No documented WA Attorney General enforcement actions or fines specifically under MHMDA were identified as of this research; federal FTC Section 5 enforcement in the health-privacy space (e.g., the July 2026 Hims & Hers suit, joined by Utah and California, not Washington) illustrates continued federal-baseline enforcement activity applicable nationally, including in Washington, absent state-specific AG action in this window.

Periodic update · new data 2026-11-08

Washington's enforcement machinery is uneven across its sectoral patchwork, and the sharpest point of that machinery sits with the My Health My Data Act. A violation of that Act is understood to function as a per se violation of the state's Consumer Protection Act, which in turn is reported to carry a private right of action: private plaintiffs may pursue treble damages, capped at $25,000, in addition to a separate track under which the Attorney General may pursue civil penalties of up to $7,500 per violation. That dual private-and-public enforcement structure gives consumer health data a considerably more aggressive enforcement profile than is typical for the state's other sectoral categories, and than is typical for consumer-privacy statutes generally, given how few state privacy laws carry a private right of action at all.

By contrast, Washington's biometric privacy law is reported to lack a private right of action comparable to Illinois's biometric statute, which would leave biometric-data enforcement resting more heavily on public enforcement alone; this specific point has not been independently verified against the statute's own text and should be read as reported rather than confirmed. On the general-agency side, the breach-notification duty under RCW 42.56.590 is a clearly defined administrative obligation rather than a private-enforcement mechanism: an agency must notify the Attorney General within 30 days of discovering a breach affecting more than 500 Washington residents, and must notify affected individuals without unreasonable delay and no more than 30 calendar days after discovery, subject to a law-enforcement-delay exception.

Outlook

The open question for this module is whether Washington's biometric statute in fact lacks a private right of action, a point that secondary sourcing asserts but that has not been checked against the statute's own text; resolving that question would materially change the enforcement-exposure comparison between the state's biometric and health-data regimes.

3 earlier distinct updates
Periodic update · new data 2026-11-04

General Motors has agreed to pay $220 million to resolve allegations that it illegally sold consumers' private driver behavior data and location information. The allegations, pursued by a coalition of 36 state attorneys general co-led by Washington and Oregon, center on General Motors' OnStar Smart Driver program, through which driver data collected between 2016 and 2024 was sold to data brokers who then resold it to insurers for use in rate-setting, without adequate disclosure or consent from the drivers whose data was at issue. Washington will receive approximately $12.3 million from the settlement, according to the Washington Attorney General's Office. The settlement also requires General Motors to obtain express consent from consumers before engaging in any future data collection of this kind.

This action is consistent with Washington's continued use of general consumer-protection authority, rather than a comprehensive privacy statute, to address large-scale commercial data-sale practices. The scale of the multistate coalition and the size of the recovery mark this as one of the more significant privacy-related enforcement outcomes involving Washington to date in the connected-vehicle and data-broker space.

Outlook

The settlement sets a marker for how Washington and its peer states are willing to use existing consumer-protection tools against data-broker arrangements involving connected products, even without a dedicated statutory data-sharing regime in place. Continued attention to connected-vehicle data practices and data-broker resale arrangements, including by insurers, is likely to follow from this outcome.

Periodic update · new data 2026-10-25

Washington's enforcement and redress picture is defined by two parallel channels rather than a single consolidated enforcement authority. First, the My Health My Data Act operates through a distinctive enforcement mechanism: a violation of the Act constitutes a per se violation of the Washington Consumer Protection Act, enforceable both by the Attorney General and through private action, with no additional proof of unfair or deceptive conduct required beyond the statutory violation itself. This per se mechanism has materially lowered the bar for private litigation, and it has driven pixel-tracking litigation against Washington businesses including Amazon and Uncle Ike's, reported at a level of confidence that remains uncertain pending confirmation of any associated formal Attorney General action. Second, the Attorney General published the state's first Data Privacy Report on 14 August 2026, which recorded 209 data breaches affecting more than eight million Washington residents during 2025 — a scale figure that illustrates the practical volume of incidents the state's sectoral enforcement apparatus is contending with, even without a comprehensive privacy statute in place.

Outlook

Whether the Attorney General has brought any formal enforcement action under the My Health My Data Act since August 2026 was not confirmed in the material reviewed; the private-litigation channel, via the Act's per se Consumer Protection Act mechanism, remains the most visible active enforcement vector in the interim. The next Data Privacy Report, if published on a similar annual cadence, would be the clearest future indicator of whether breach volumes affecting Washington residents are rising or falling.

Periodic update · new data 2026-10-18

Washington Attorney General Nick Brown has publicly characterised his office's posture toward enforcement of the My Health My Data Act (MHMDA) as deliberately restrained, stating that his office has been "thoughtful about enforcement because the law is still relatively new." This explanation addresses what is otherwise a notable absence: despite MHMDA's enforcement structure making a violation a per se violation of the state's Consumer Protection Act, with the Attorney General empowered to seek civil penalties up to $7,500 per violation, there have been few if any visible public AG enforcement actions under the statute to date.

That restraint stands in contrast to the private-litigation track, which has been considerably more active. A consumer class action against Amazon.com, Inc. and Amazon Advertising, LLC was filed 10 February 2026, joining at least one other active private MHMDA matter. Private plaintiffs under MHMDA may obtain injunctive relief, actual damages, attorney fees, and treble damages up to $25,000, a remedy structure that gives individual litigants and class plaintiffs a meaningfully different, and in some respects more aggressive, enforcement lever than the AG's own civil-penalty authority provides. The practical effect of the AG's stated restraint is that MHMDA's enforcement trajectory in Washington is currently being driven primarily by private litigation rather than by public agency action, even though the statute vests the Attorney General with its own independent enforcement authority.

The AG's explanation that restraint reflects the statute's relative novelty is a defensible regulatory posture in general terms: a newly enacted statute is commonly given a period of lower-intensity public enforcement while regulated entities adjust their practices, with private litigation filling part of the gap in the interim. Whether this restraint will persist, or whether a notable enforcement action, prompted perhaps by developments in the pending private litigation, will mark a shift toward more active public enforcement, is not addressed in the evidence available this cycle.

Outlook

The matter most likely to affect this domain's trajectory is the progress of the two active private MHMDA lawsuits, including the Amazon class action filed in February 2026; a ruling or settlement in either matter could influence whether the AG's office shifts from its currently stated restrained enforcement posture toward more visible public action. Absent such a development, MHMDA enforcement in Washington is likely to continue being shaped primarily by private litigation outcomes rather than AG-initiated proceedings for the near term.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (15)
  1. Probable IAPP — Violations of the My Health My Data Act are enforceable both by the Washington Attorney General and by private plaintiffs under the state's Consumer Protection Act, which for private MHMDA claims dispenses with the CPA's usual requirement that plaintiffs prove the violation is an unfair/deceptive act, since any MHMDA violation is deemed to satisfy those elements. observed
  2. Probable IAPP — Washington's My Health My Data Act is cited among the newer state privacy statutes, alongside the CCPA and New Jersey's Daniel's Law, that plaintiffs increasingly use as grounds for privacy class-action litigation amid an overall surge in U.S. data-privacy lawsuits. observed
  3. Probable IAPP — The My Health My Data Act contains a broad private right of action enforceable under Washington's Consumer Protection Act, authorizing consumers to sue for a violation of any provision of the Act without a mitigating cure period, with potential recovery of actual damages, litigation costs, attorney's fees, and treble damages upon proof of injury. observed
  4. Probable Federal Trade Commission — In July 2026, the FTC, joined by Utah and California, filed suit against telehealth provider Hims & Hers alleging deceptive and unlawful sharing of consumers' sensitive health data, illustrating continued active federal Section 5 enforcement in the health-privacy space that forms part of the baseline regulatory backdrop applicable in Washington absent state-specific AG action in this window. observed
  5. Probable Washington State Office of Attorney General — General Motors — GM $220M OnStar data-sale settlement; WA share ~$12.3M. observed
  6. Probable WilmerHale — Washington State Attorney General — On Aug 14, 2026 the WA AG released the state's first-ever Data Privacy Report, noting 209 reported breaches in 2025 affecting more than 8 million residents (over 80% involving Social Security numbers), and recommending the Legislature enact a comprehensive consumer privacy statute, which WA currently lacks. observed
  7. Probable VertiComply — My Health My Data Act (RCW 19.373) — A violation of MHMDA is a per se violation of the CPA; the AG may seek civil penalties up to $7,500 per violation, while private plaintiffs may obtain injunctive relief, actual damages, attorney fees, and treble damages up to $25,000. observed
  8. Probable MLex — Washington Attorney General Nick Brown — Brown's office has been 'thoughtful about enforcement because the law is still relatively new,' explaining the relative absence of public AG enforcement actions despite an active private-litigation pipeline including a Feb 10, 2026 consumer class action against Amazon.com, Inc. and Amazon Advertising, LLC. observed
  9. Probable Ashurst Perkins Coie — My Health My Data Act / Washington Consumer Protection Act — Violations of the My Health My Data Act are per se violations of the Washington Consumer Protection Act, enforceable by both the Attorney General and through private consumer actions. observed
  10. Uncertain RecordingLaw.com — MHMDA enforcement activity — The first businesses sued under MHMDA include a cannabis retailer and Amazon's advertising business, not hospitals, indicating enforcement is reaching adtech-adjacent rather than traditional healthcare defendants first. observed
  11. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/washington-data-privacy-laws/ — The My Health My Data Act gives Washington consumers a private right of action by making violations enforceable as per se violations of the Washington Consumer Protection Act.
  12. Uncertain Enzuzo — My Health My Data Act private right of action — Private pixel-tracking litigation against Washington businesses, including Amazon and Uncle Ike's. observed
  13. Probable Washington State Legislature — SB 6002 Senate Bill Report — My Health My Data Act (RCW 19.373) — A violation of MHMDA is a per se violation of the Washington Consumer Protection Act, enforceable by the Attorney General and through private action. observed
  14. Probable Washington State Office of Attorney General — General Motors — Agreed to pay $220 million to settle allegations by 36 state AGs (co-led by Washington and Oregon) that it sold OnStar Smart Driver connected-vehicle data (2016-2024) to data brokers who resold it to insurers for rate-setting without adequate disclosure or consent; Washington's share is approximately $12.3 million, and GM must obtain express consent before future comparable data collection. observed
  15. Probable PrivacyTerms.io — MHMDA violations are per se CPA violations carrying a private right of action with treble damages capped at $25,000, plus a separate AG civil-penalty track up to $7,500 per violation. 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, 57 sub-module(s), 55 claim(s) (55 category placement(s)), 43 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: upheld (2 confirmed against the cited source). An automated, adversarial test run by a second model; no person has assessed the result.

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

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (38 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 received
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. 81Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties