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.

Oklahoma, USA Data Protection & Privacy Regulation

US-OK schema gdpri-v2 trajectory: not yet assessed in transition overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 78 claims · 45 sources in the cumulative register

Oklahoma enacted its first comprehensive consumer data privacy statute this cycle.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Cross-Border & Adequacy (1 open gap).

Framework & posture10 of 10 modules active
10 active · 10 binding instruments
Supervisory authorityOklahoma Attorney General
Next milestone
JAN12027
Oklahoma Consumer Data Privacy Act in force
Record & confidence mix78 claims · 34 sources · machine-compiled
58 Probable1 Indicative19 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 Oklahoma, USA is covered once, on the United States page. This page covers Oklahoma, USA’s own layer: its own law, regulators and enforcement.

Jurisdiction brief

Latest update · 18 October 2026

Lead Signal

Oklahoma has moved from a state with no comprehensive consumer-privacy statute to one with an enacted, not-yet-effective framework. Governor Kevin Stitt signed Senate Bill 546 into law on 20 March 2026, creating the Oklahoma Consumer Data Privacy Act (OCDPA), which is understood to take effect on 1 January 2027. Separately, the Oklahoma Security Breach Notification Act has been amended by Senate Bill 626, in force since 1 January 2026, adding an Attorney General notification duty and broadening the definition of personal information.

Key regulatory facts for Oklahoma, USA
Key regulatory facts for Oklahoma, USA
Regulatory DimensionOklahoma, USA Standing Position
JurisdictionOklahoma, USA (US-OK)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 78 sourced findings)
Regulator & FrameworkRegime is mid-transition: sectoral-only today, comprehensive omnibus law enacted but not yet effective (2027-01-01).
Lawful Processing & Special DataNo in-force general lawful-basis regime; forthcoming SB 546 provisions in this area are analogized from the Virginia model rather than confirmed against OK bill text.
Data Subject RightsRights confirmed to exist in principle for 2027 commencement; procedural specifics not independently verified.
Controller/Processor DutiesDPIA obligation confirmed for 2027; DPO/ROPA/retention requirements not identified; sectoral security/breach duties (GLBA, HIPAA) are robustly in force today.
Primary Instruments CitedFederal Trade Commission, IAPP, DataGuidance, WilmerHale, Sheppard Mullin
Last Confirmed / Updated (45 sources in cumulative register)

#

Regime is mid-transition: sectoral-only today, comprehensive omnibus law enacted but not yet effective (2027-01-01).

Primary frameworkFTC Act Section 5 (in force) + Oklahoma Security Breach Notification Act (in force) + Senate Bill 546 comprehensive consumer data privacy law (enacted, effective 2027-01-01)
Supervisory authorityOklahoma Attorney General
Traffic-light rationale — AmberRegime is mid-transition: sectoral-only today, comprehensive omnibus law enacted but not yet effective (2027-01-01).

Sub-modules (5)

Regulator and authorityAmber

The Oklahoma Attorney General (currently Gentner Drummond) is the designated state enforcement authority for consumer protection and will hold exclusive enforcement authority under SB 546 once effective. The FTC is the concurrent federal enforcement authority under Section 5.

Claims (5):

  • The current Oklahoma Attorney General, Gentner Drummond, was sworn in on 9 January 2023 and serves as the state's chief legal officer with consumer-protection enforcement authority.
  • Oklahoma Consumer Data Privacy Act (SB 546) — Signed by Governor Kevin Stitt on 2026-03-20, creating the OCDPA, enforceable solely by the Oklahoma Attorney General with a permanent cure period before enforcement action.
  • Both the Security Breach Notification Act (as amended by SB 626) and the OKCDPA (SB 546) are enforced exclusively by the Oklahoma Attorney General; neither statute creates a private right of action.
  • Oklahoma Attorney General — OCDPA; no private right of action; 30-day cure period
  • Oklahoma Attorney General — OCDPA; no private right of action; 30-day non-sunsetting right-to-cure period required before enforcement

Act and instrumentsAmber

Current in-force instruments: FTC Act Section 5; Oklahoma Security Breach Notification Act (breach notice only). Enacted-not-yet-effective instrument: SB 546.

Claims (10):

  • The FTC Act prohibits companies and individuals from engaging in unfair or deceptive acts or practices in or affecting commerce, and constitutes the operative general federal privacy-enforcement baseline applicable to Oklahoma businesses absent a state omnibus law.
  • The Oklahoma Legislature enacted a comprehensive consumer data privacy law, Senate Bill 546, which passed the House on final passage 84-4 on 19 February 2026 and was substituted on the House floor with a compromise text aligning mostly with the Virginia Consumer Data Protection Act framework.
  • SB 546 was reported signed into law in March 2026 by the Oklahoma Governor; this is based on a secondary-source headline and was not corroborated against the primary enrolled-bill or Secretary of State record in this research pass.
  • Oklahoma Consumer Data Privacy Act (SB 546) — 2027-01-01
  • Oklahoma Security Breach Notification Act (SB 626) — Substantially amended, effective 2026-01-01, adding a state Attorney General notification duty, broadening the definition of personal information to include government-issued ID numbers and biometric identifiers, and introducing a reasonable-safeguards affirmative defense.
  • Oklahoma Consumer Data Privacy Act (SB 546) — effective_date: 2027-01-01
  • Security Breach Notification Act (SB 626) — Substantially amended, effective 2026-01-01, the first amendment since 2008 enactment.
  • Security Breach Notification Act (SB 626 amendment) — SB 626 amends the Security Breach Notification Act (24 O.S. §§161-166), effective January 1, 2026, expanding the definition of 'personal information' to include biometric identifiers and government-issued ID numbers, and adding an Attorney General notification requirement for breaches affecting 500 or more residents within 60 days of resident notification.
  • Senate Bill 546 (Oklahoma Consumer Data Privacy Act) — Approved by Governor 2026-03-20
  • Senate Bill 546 (Oklahoma Consumer Data Privacy Act) — Approved by the Governor on 2026-03-20, enacting Oklahoma's first comprehensive consumer data-privacy statute

Material scopeAmber

SB 546 will apply to businesses controlling/processing personal data of at least 100,000 Oklahomans, or 25,000 consumers combined with deriving at least 50% of gross revenue from data sales.

Claims (5):

  • SB 546 covers businesses that control or process the personal data of at least 100,000 Oklahomans, or the data of at least 25,000 consumers while deriving at least 50% of gross revenue from data sales.
  • Oklahoma Consumer Data Privacy Act (SB 546) — SB 546, signed March 20, 2026 and effective January 1, 2027, applies to a controller or processor conducting business in Oklahoma or targeting Oklahoma residents that, in a calendar year, controls/processes personal data of at least 100,000 consumers, or of at least 25,000 consumers while deriving over 50% of gross revenue from the sale of personal data.
  • Oklahoma Consumer Data Privacy Act (SB 546) — threshold: 100000 or 25000+50pct_revenue
  • Oklahoma Consumer Data Privacy Act (SB 546) — Controllers processing personal data of 100,000+ OK consumers annually, or 25,000+ where over 50% of gross revenue derives from sale of personal data.
  • Oklahoma Consumer Data Privacy Act (SB 546) — Applies only to Oklahoma consumers acting in an individual or household context, excluding employment and commercial/B2B contexts, and exempts entities/data subject to GLBA and HIPAA, nonprofits, and higher-education institutions.

Territorial scopeAmber

FTC Section 5 authority is not geographically limited within the US and reaches any entity engaged in commerce affecting Oklahoma consumers. SB 546's precise territorial-scope language (e.g., conducting business in the state or targeting state residents, per the typical Virginia-model formulation) was not independently verified against primary bill text in this research pass.

Claims (1):

  • FTC Act Section 5 unfair/deceptive-practices authority applies to conduct affecting commerce nationally, including transactions with Oklahoma consumers, regardless of where the responsible entity is established.

Regulator registration and filingRed

No general controller/processor registration or filing regime currently exists in Oklahoma, and none was identified as part of SB 546 in the secondary sources reviewed.

Category narrative 125 words

As of the 2026-08-06 dispatch date, Oklahoma has no comprehensive consumer-privacy statute IN FORCE. The operative regime is sectoral/reactive: the federal FTC Act Section 5 unfair/deceptive-practices authority, applicable federal sectoral statutes (HIPAA, GLBA, COPPA), and the state's breach-notification-only statute. CRITICALLY, this materially updates the injected seed disambiguation: the Oklahoma Legislature has since ENACTED a comprehensive consumer data privacy law, Senate Bill 546 (SB 546), which passed the House 84-4 on 19 Feb 2026 and was reported signed into law in March 2026; it takes effect 1 Jan 2027 on a Virginia CDPA-modeled framework. Until that date the seed's 'no comprehensive statute' characterization remains technically accurate for the CURRENT in-force position, but is about to become obsolete and must not be treated as a durable finding.

Periodic update · new data 2026-11-08

Oklahoma is understood to have enacted its first comprehensive consumer data-privacy statute. The Oklahoma Consumer Data Privacy Act, carried as Senate Bill 546, is reported to have been approved by the Governor on 20 March 2026, modeled on the Virginia Consumer Data Protection Act's framework of controller and processor obligations. This moves Oklahoma from having no comprehensive privacy statute to having one on the books, though the law has not yet taken effect.

The effective date carries some residual uncertainty. Converging secondary commentary points to 1 January 2027 as the date the Act becomes operative, but earlier drafts of the bill carried different effective-date clauses as the legislation moved through introduction and engrossment, and the enrolled session-law text was not directly confirmed. Until that text is checked against the final clause, the January 2027 date should be read as the best-supported estimate rather than a settled fact.

Enforcement of the Act is understood to sit exclusively with the Oklahoma Attorney General. There is no private right of action, so individuals will not be able to bring their own claims under the statute; any action proceeds through the Attorney General's office. The Act is also reported to require a thirty-day cure period before an enforcement action can be brought, and this cure right does not sunset - meaning it remains available to controllers and processors indefinitely rather than expiring after an initial window, which marks a lenient enforcement on-ramp relative to statutes that eventually withdraw the cure right. Controllers and processors meeting the Act's applicability thresholds are the obliged parties under the framework, consistent with the Virginia-style comprehensive model.

Outlook

The period leading into the Act's expected commencement is likely to centre on confirming the enrolled effective date and on controllers and processors assessing whether they meet the statute's applicability thresholds ahead of a Virginia-style compliance programme. Given the Attorney General's exclusive enforcement role and the standing cure period, the earliest phase of the regime is likely to emphasise correction over penalty.

2 earlier distinct updates
Periodic update · new data 2026-10-18

Oklahoma's comprehensive privacy landscape has changed materially. Governor Kevin Stitt signed Senate Bill 546 into law on 20 March 2026, creating the Oklahoma Consumer Data Privacy Act (OCDPA), understood to take effect on 1 January 2027, with enforcement reserved solely to the Oklahoma Attorney General and a permanent cure period preceding any enforcement action. This corrects an earlier position that treated Oklahoma as lacking a comprehensive consumer-privacy statute. The primary enrolled-bill text has not yet been independently opened and quoted, so the characterisation above rests on secondary commercial legal-sector sources.

Alongside the OCDPA, the pre-existing Oklahoma Security Breach Notification Act has been substantially amended by Senate Bill 626, in force since 1 January 2026. The amendment adds a state Attorney General notification duty, broadens the statutory definition of personal information to include government-issued identification numbers and biometric identifiers, and introduces a reasonable-safeguards affirmative defense, addressing what commentary describes as gaps in the state's prior cybersecurity framework.

The OCDPA's material scope, as reported, covers only Oklahoma consumers acting in an individual or household context, expressly excluding employment and commercial/business-to-business relationships. Entities and data already subject to the Gramm-Leach-Bliley Act or HIPAA are exempted, as are nonprofit organisations and higher-education institutions, placing Oklahoma's statute toward the narrower end of comprehensive state privacy laws by scope.

Outlook

The OCDPA's 1 January 2027 effective date is the key date to track; until then the statute is enacted but not yet operative, and its reported entity exemptions and consumer-individual-context limitation determine which Oklahoma businesses it will eventually reach. The Security Breach Notification Act amendments are already in force and are being applied now.

Periodic update · new data 2026-10-11

Oklahoma's data protection regulatory framework has moved from a status of no comprehensive statute to an enacted-but-not-yet-effective statute this cycle. The Oklahoma Consumer Data Privacy Act (SB 546) was signed into law on March 20, 2026 and takes effect January 1, 2027, with no phased rollout and no small-business grace period built into its commencement. The Act's material scope is bounded: it applies to persons that control or process personal data of at least 100,000 Oklahoma consumers, or at least 25,000 consumers while deriving more than 50% of gross revenue from the sale of personal data, and its application is confined to individual and household contexts, expressly excluding employment and commercial contexts. Enforcement authority under the Act is centralized: 75A O.S. §311 requires the Oklahoma Attorney General to publish information about the Act and maintain an online consumer-complaint mechanism, and gives the Attorney General exclusive authority to enforce it, meaning there is no private enforcement track and no role for a dedicated data protection authority distinct from the Attorney General's office.

Outlook

The framework remains inert as a practical matter until January 1, 2027. Whether the Attorney General's office stands up the required complaint mechanism and publishes compliance guidance ahead of that date is the development most likely to signal how actively the office intends to exercise its exclusive enforcement authority once the Act takes effect.

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

Sources and claims (21)
  1. Probable NAAG — The current Oklahoma Attorney General, Gentner Drummond, was sworn in on 9 January 2023 and serves as the state's chief legal officer with consumer-protection enforcement authority. observed
  2. Probable Federal Trade Commission — The FTC Act prohibits companies and individuals from engaging in unfair or deceptive acts or practices in or affecting commerce, and constitutes the operative general federal privacy-enforcement baseline applicable to Oklahoma businesses absent a state omnibus law. observed
  3. Probable IAPP — The Oklahoma Legislature enacted a comprehensive consumer data privacy law, Senate Bill 546, which passed the House on final passage 84-4 on 19 February 2026 and was substituted on the House floor with a compromise text aligning mostly with the Virginia Consumer Data Protection Act framework. observed
  4. Probable DataGuidance — SB 546 was reported signed into law in March 2026 by the Oklahoma Governor; this is based on a secondary-source headline and was not corroborated against the primary enrolled-bill or Secretary of State record in this research pass. observed
  5. Probable IAPP — SB 546 covers businesses that control or process the personal data of at least 100,000 Oklahomans, or the data of at least 25,000 consumers while deriving at least 50% of gross revenue from data sales. observed
  6. Probable Federal Trade Commission — FTC Act Section 5 unfair/deceptive-practices authority applies to conduct affecting commerce nationally, including transactions with Oklahoma consumers, regardless of where the responsible entity is established. observed
  7. Probable Oklahoma Legislature — Oklahoma Consumer Data Privacy Act (SB 546) — 2027-01-01 observed
  8. Probable Oklahoma Legislature — Oklahoma Consumer Data Privacy Act (SB 546) — Signed by Governor Kevin Stitt on 2026-03-20, creating the OCDPA, enforceable solely by the Oklahoma Attorney General with a permanent cure period before enforcement action. observed
  9. Probable LegiScan — Oklahoma Security Breach Notification Act (SB 626) — Substantially amended, effective 2026-01-01, adding a state Attorney General notification duty, broadening the definition of personal information to include government-issued ID numbers and biometric identifiers, and introducing a reasonable-safeguards affirmative defense. observed
  10. Probable Troutman Pepper Privacy Blog — Oklahoma Consumer Data Privacy Act (SB 546) — SB 546, signed March 20, 2026 and effective January 1, 2027, applies to a controller or processor conducting business in Oklahoma or targeting Oklahoma residents that, in a calendar year, controls/processes personal data of at least 100,000 consumers, or of at least 25,000 consumers while deriving over 50% of gross revenue from the sale of personal data. observed
  11. Probable Oklahoma Legislature — Oklahoma Consumer Data Privacy Act (SB 546) — Effective date: 2027-01-01 observed
  12. Probable LegiScan — Oklahoma Consumer Data Privacy Act (SB 546) — threshold: 100000 or 25000+50pct_revenue observed
  13. Probable LegiScan — Oklahoma Consumer Data Privacy Act (SB 546) — Controllers processing personal data of 100,000+ OK consumers annually, or 25,000+ where over 50% of gross revenue derives from sale of personal data. observed
  14. Probable Troutman Pepper Privacy Blog — Security Breach Notification Act (SB 626) — Substantially amended, effective 2026-01-01, the first amendment since 2008 enactment. observed
  15. Probable Troutman Pepper Privacy Blog — Oklahoma Consumer Data Privacy Act (SB 546) — Applies only to Oklahoma consumers acting in an individual or household context, excluding employment and commercial/B2B contexts, and exempts entities/data subject to GLBA and HIPAA, nonprofits, and higher-education institutions. observed
  16. Probable Oklahoma Legislature — Both the Security Breach Notification Act (as amended by SB 626) and the OKCDPA (SB 546) are enforced exclusively by the Oklahoma Attorney General; neither statute creates a private right of action. observed
  17. Probable LegiScan — Security Breach Notification Act (SB 626 amendment) — SB 626 amends the Security Breach Notification Act (24 O.S. §§161-166), effective January 1, 2026, expanding the definition of 'personal information' to include biometric identifiers and government-issued ID numbers, and adding an Attorney General notification requirement for breaches affecting 500 or more residents within 60 days of resident notification. observed
  18. Probable Oklahoma Legislature — Oklahoma Attorney General — OCDPA; no private right of action; 30-day cure period observed
  19. Probable LegiScan — Senate Bill 546 (Oklahoma Consumer Data Privacy Act) — Approved by Governor 2026-03-20 observed
  20. Probable Oklahoma Legislature — Oklahoma Attorney General — OCDPA; no private right of action; 30-day non-sunsetting right-to-cure period required before enforcement observed
  21. Probable LegiScan — Senate Bill 546 (Oklahoma Consumer Data Privacy Act) — Approved by the Governor on 2026-03-20, enacting Oklahoma's first comprehensive consumer data-privacy statute observed

#

No in-force general lawful-basis regime; forthcoming SB 546 provisions in this area are analogized from the Virginia model rather than confirmed against OK bill text.

Primary frameworkNone in force; SB 546 (Virginia-CDPA-modeled) from 2027-01-01
Supervisory authorityOklahoma Attorney General
Traffic-light rationale — RedNo in-force general lawful-basis regime; forthcoming SB 546 provisions in this area are analogized from the Virginia model rather than confirmed against OK bill text.

Sub-modules (4)

Lawful basesRed

No GDPR-style enumerated lawful-bases regime exists or is confirmed for SB 546; Virginia-model laws generally use a general opt-out processing standard rather than an enumerated lawful-basis list.

Claims (1):

  • Oklahoma Consumer Data Privacy Act (SB 546) — Uses an opt-out model under which businesses may collect and process personal data without prior consent, provided consumers have a clear means to opt out of targeted advertising, data sales, and profiling producing legal or similarly significant effects.

Special categoriesAmber

Sensitive-data category definitions for SB 546 were not independently retrieved; Virginia-model laws typically include health, genetic, biometric, ethnicity/race, religion, sexual orientation/status, citizenship/immigration status, and precise geolocation as sensitive categories.

Claims (2):

  • SB 546's definition of sensitive/special-category personal data was not independently retrieved; a Virginia-CDPA-analogous definition (health, genetic, biometric, racial/ethnic origin, religion, sexual orientation, citizenship/immigration status, precise geolocation, data of known minors) is presumed but unconfirmed.
  • Oklahoma Consumer Data Privacy Act (SB 546) — OKCDPA prohibits processing of 'sensitive data' — defined to include racial/ethnic origin, religious belief, mental/physical health diagnosis, sexual orientation, citizenship/immigration status, uniquely-identifying genetic/biometric data, known-child data, and precise geolocation data — without the consumer's consent.

Pseudonymisation and anonymisationRed

No Oklahoma-specific pseudonymisation/anonymisation safe-harbour provision was identified in this research pass.

Category narrative 62 words

No general enumerated lawful-basis or consent-threshold framework is currently in force in Oklahoma. SB 546 (effective 2027-01-01) is modeled on the Virginia CDPA, which uses an opt-out (not opt-in) general processing model with opt-in consent required specifically for processing 'sensitive data' categories; however, OK-specific bill-text language on consent thresholds and special-category definitions was not independently verified against primary sources in this pass.

Periodic update · new data 2026-11-08

Reports suggest the Oklahoma Consumer Data Privacy Act will require consent before sensitive data can be processed once the statute takes effect. This tracks the pattern of other comprehensive state privacy laws, which generally gate processing of sensitive categories behind an affirmative consent requirement. However, the sourcing behind this specific claim is thinner than for the Act's enactment and enforcement provisions: it rests on a single secondary commentary source and has not been independently corroborated, so the consent mechanics described here should be treated as a developing picture rather than a confirmed feature of the statute.

One detail worth flagging on that basis: the same reporting indicates no stated right of revocation once consent to process sensitive data has been given. If that holds up against the enrolled text, it would be a notable design choice relative to peer statutes, many of which build in a right to withdraw consent. Because this rests on an uncertain reading, it is best treated as a point to watch rather than a settled obligation at this stage.

Outlook

Confirmation of the consent mechanics for sensitive data - including whether a revocation right exists elsewhere in the statute or in forthcoming guidance - is likely to depend on a direct read of the enrolled text rather than continued reliance on secondary commentary.

1 earlier distinct update
Periodic update · new data 2026-10-18

The OCDPA is understood to adopt an opt-out default model for ordinary personal-data processing: businesses may collect and process personal data without obtaining prior consent, provided consumers are given a clear mechanism to opt out of targeted advertising, data sales, and profiling that produces legal or similarly significant effects. This positions Oklahoma's lawful-basis architecture closer to the opt-out family of US state privacy statutes rather than a GDPR-style opt-in-by-default model.

For sensitive personal data, the statute is reported to reverse this default: affirmative, opt-in consent is required before processing biometric data, precise geolocation data, and the personal data of known children under 13. This dual-track structure, opt-out for general processing and opt-in for defined sensitive categories, mirrors the architecture found in several other recent US state comprehensive privacy laws.

Outlook

Once the OCDPA takes effect on 1 January 2027, Oklahoma businesses processing biometric data, precise geolocation, or children's data will need an opt-in consent pathway in place, while general processing can continue to rely on a disclosed opt-out mechanism. The precise boundaries of what the statute treats as triggering 'significant effects' profiling have not been independently verified against primary statutory text.

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

Sources and claims (6)
  1. Uncertain IAPP — SB 546 is modeled mostly on the original framework of Virginia's Consumer Data Protection Act, which conditions processing of sensitive personal data on prior opt-in consent; the presence of an equivalent OK-specific opt-in requirement was not independently confirmed against SB 546 bill text. observed
  2. Speculative IAPP — SB 546's definition of sensitive/special-category personal data was not independently retrieved; a Virginia-CDPA-analogous definition (health, genetic, biometric, racial/ethnic origin, religion, sexual orientation, citizenship/immigration status, precise geolocation, data of known minors) is presumed but unconfirmed. observed
  3. Probable Oklahoma Legislature — Oklahoma Consumer Data Privacy Act (SB 546) — Uses an opt-out model under which businesses may collect and process personal data without prior consent, provided consumers have a clear means to opt out of targeted advertising, data sales, and profiling producing legal or similarly significant effects. observed
  4. Probable Oklahoma Legislature — Oklahoma Consumer Data Privacy Act (SB 546) — Affirmative (opt-in) consent is required before processing sensitive personal data, including biometric data, precise geolocation, and data belonging to known children under 13. observed
  5. Probable Oklahoma Legislature — Oklahoma Consumer Data Privacy Act (SB 546) — OKCDPA prohibits processing of 'sensitive data' — defined to include racial/ethnic origin, religious belief, mental/physical health diagnosis, sexual orientation, citizenship/immigration status, uniquely-identifying genetic/biometric data, known-child data, and precise geolocation data — without the consumer's consent. observed
  6. Uncertain Troutman Pepper Privacy Blog — Oklahoma Consumer Data Privacy Act (SB 546, 2026) — Processing of sensitive data, with no stated right of revocation once consent is given observed

#

Rights confirmed to exist in principle for 2027 commencement; procedural specifics not independently verified.

Primary frameworkSB 546 (effective 2027-01-01)
Supervisory authorityOklahoma Attorney General
Traffic-light rationale — AmberRights confirmed to exist in principle for 2027 commencement; procedural specifics not independently verified.

Sub-modules (5)

Access rightAmber

SB 546 contains standard data subject access rights as part of its rights package.

Claims (2):

  • SB 546 contains standard data subject access rights as part of the consumer rights package taking effect 1 January 2027.
  • Oklahoma Consumer Data Privacy Act (SB 546) — Grants Oklahoma consumers the rights to confirm processing and access, correct, delete, obtain a portable copy of, and opt out of targeted advertising/sale/significant-effect profiling regarding their personal data, effective 2027-01-01.

Rectification and erasureAmber

Correction and deletion rights are presumed included within the 'standard data subject access rights' described for SB 546, consistent with the Virginia-model rights package, but explicit bill-text confirmation was not obtained.

Claims (1):

  • Correction and deletion rights are presumed part of SB 546's standard consumer rights package but were not itemized separately in the secondary sources reviewed.

Restriction and objectionAmber

SB 546 explicitly provides opt-outs for targeted advertising and sale of personal data.

Claims (1):

  • SB 546 contains standard data subject access rights, including opt-outs for targeted advertising and data sales as defined under the bill.

Data portabilityAmber

Portability is presumed part of the 'standard' rights package referenced for SB 546 but not independently itemized in sources reviewed.

Claims (1):

  • A data-portability right is presumed included in SB 546's standard rights package but was not independently itemized in sources reviewed.

Deadlines and response windowsRed

No OK-specific statutory response-window (e.g., 45-day) figure was independently confirmed for SB 546 in this research pass.

Claims (2):

  • Oklahoma Consumer Data Privacy Act (SB 546) — Controllers must respond to authenticated consumer rights requests under OKCDPA within 45 days of receipt, free of charge, with one permissible 45-day extension where reasonably necessary.
  • Oklahoma Consumer Data Privacy Act (SB 546) — A controller must respond to an authenticated consumer rights request no later than 45 days after receipt, extendable once by an additional 45 days when reasonably necessary.
Category narrative 54 words

No enforceable consumer data-subject-rights framework currently exists in Oklahoma outside limited breach-notification entitlements. SB 546 will introduce standard rights (access, correction/deletion, portability, and opt-outs for targeted advertising and sale of personal data) modeled on other Virginia-style state laws, effective 1 Jan 2027, though granular procedural detail (response windows, appeal mechanisms) was not independently confirmed.

Periodic update · new data 2026-10-18

The OCDPA is reported to grant Oklahoma consumers a standard set of data-subject rights from its 1 January 2027 effective date: the right to confirm whether a controller is processing their personal data and to access it, the right to correct inaccuracies, the right to deletion, the right to a portable copy of personal data, and the right to opt out of targeted advertising, sale of personal data, and profiling that produces legal or similarly significant effects.

This rights package is consistent in shape with the access, correction, deletion, portability, and opt-out bundle found across the broader wave of US state comprehensive privacy statutes, though the precise mechanics, response timelines, and any appeal process for rights requests have not been independently confirmed against the primary enrolled-bill text.

Outlook

These rights do not become exercisable until the OCDPA's 1 January 2027 effective date; Oklahoma consumers currently have no statutory access, correction, deletion, or portability right under state law outside of this pending framework.

1 earlier distinct update
Periodic update · new data 2026-10-11

The Oklahoma Consumer Data Privacy Act establishes a defined set of consumer rights, though none are yet exercisable. The Act grants Oklahoma consumers the rights to access, correct, delete, and obtain a portable copy of their personal data. Alongside these, it grants a right to opt out of processing for three specific purposes: targeted advertising, sale of personal data, and profiling in furtherance of decisions that produce legal or similarly significant effects on the consumer. These rights follow the now-familiar opt-out model used across several other US state privacy statutes rather than an opt-in or consent-based model for ordinary processing. Because the Act's effective date is January 1, 2027, no consumer can presently exercise any of these rights, and no controller is yet obligated to build a rights-request intake process, though covered entities will need such mechanisms in place by the effective date given the Act's lack of a phased rollout.

Outlook

Whether OCDPA recognizes a universal opt-out signal, such as Global Privacy Control, for exercising the opt-out rights has not been confirmed from primary bill text this cycle and remains an open question that will materially affect how controllers are expected to implement opt-out compliance ahead of the 2027 effective date.

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

Sources and claims (7)
  1. Probable IAPP — SB 546 contains standard data subject access rights as part of the consumer rights package taking effect 1 January 2027. observed
  2. Uncertain IAPP — Correction and deletion rights are presumed part of SB 546's standard consumer rights package but were not itemized separately in the secondary sources reviewed. observed
  3. Probable IAPP — SB 546 contains standard data subject access rights, including opt-outs for targeted advertising and data sales as defined under the bill. observed
  4. Uncertain IAPP — A data-portability right is presumed included in SB 546's standard rights package but was not independently itemized in sources reviewed. observed
  5. Probable Riddle Compliance — Oklahoma Consumer Data Privacy Act (SB 546) — Grants Oklahoma consumers the rights to confirm processing and access, correct, delete, obtain a portable copy of, and opt out of targeted advertising/sale/significant-effect profiling regarding their personal data, effective 2027-01-01. observed
  6. Probable Troutman Pepper Privacy Blog — Oklahoma Consumer Data Privacy Act (SB 546) — Controllers must respond to authenticated consumer rights requests under OKCDPA within 45 days of receipt, free of charge, with one permissible 45-day extension where reasonably necessary. observed
  7. Probable Oklahoma Legislature — Oklahoma Consumer Data Privacy Act (SB 546) — A controller must respond to an authenticated consumer rights request no later than 45 days after receipt, extendable once by an additional 45 days when reasonably necessary. observed

#

DPIA obligation confirmed for 2027; DPO/ROPA/retention requirements not identified; sectoral security/breach duties (GLBA, HIPAA) are robustly in force today.

Primary frameworkGLBA Safeguards Rule + HIPAA Security Rule (in force) + SB 546 DPIA requirement (effective 2027-01-01)
Supervisory authorityOklahoma Attorney General
Traffic-light rationale — AmberDPIA obligation confirmed for 2027; DPO/ROPA/retention requirements not identified; sectoral security/breach duties (GLBA, HIPAA) are robustly in force today.

Sub-modules (7)

Accountability & DPIAAmber

SB 546 requires data protection assessments for a range of processing activities.

Claims (2):

  • SB 546 requires controllers to conduct data protection assessments for a range of processing activities, effective 1 January 2027.
  • Oklahoma Consumer Data Privacy Act (SB 546) — OKCDPA requires controllers to conduct data protection assessments for processing that presents a heightened risk of harm, including targeted-advertising profiling with legal or similarly significant effects and processing of sensitive data.

DPO requirementsRed

No DPO-appointment threshold was identified for SB 546 or any current OK statute in this research pass.

Ropa requirementsRed

No records-of-processing (ROPA) obligation was identified for SB 546 in this research pass.

Joint controller arrangementsRed

No Oklahoma-specific joint-controller provision was identified; Virginia-model laws typically use standard controller/processor contract-clause requirements, but this was not independently confirmed for SB 546.

Security measuresGreen

The GLBA Safeguards Rule requires covered financial institutions to maintain a written information-security program with administrative, technical and physical safeguards.

Claims (4):

  • The FTC Safeguards Rule requires covered financial institutions to develop, implement, and maintain an information security program with administrative, technical, and physical safeguards designed to protect customer information.
  • Oklahoma Security Breach Notification Act (SB 626) — Introduces a 'reasonable safeguards' affirmative defense rewarding entities that implement proactive cybersecurity investments, and provides an individual-notice exemption for entities complying with the Oklahoma Hospital Cybersecurity Protection Act of 2023 or HIPAA, provided the Attorney General still receives notice.
  • Security Breach Notification Act (SB 626) — penalty_cap_usd: 75000_or_150000
  • Security Breach Notification Act (SB 626) — Reasonable-safeguards affirmative defense caps civil penalties at $75,000/breach versus $150,000 without safeguards/timely notice.

Breach notificationAmber

Oklahoma's general Security Breach Notification Act requires notification of affected residents following a breach of computerized personal information; sector-specific breach rules (HIPAA Breach Notification Rule, GLBA Safeguards Rule notification-event requirement) also apply. Precise OK statutory citation/timelines were not independently re-verified against primary text in this pass.

Claims (6):

  • Financial institutions subject to the FTC Safeguards Rule must notify the FTC as soon as possible, and no later than 30 days after discovery, of a notification event involving unauthorized acquisition of at least 500 consumers' unencrypted information.
  • Oklahoma maintains a general Security Breach Notification Act requiring notice to affected residents following a breach of computerized personal information; the precise statutory citation and notification timeline were not independently re-verified against primary statutory text in this research pass.
  • Security Breach Notification Act (SB 626) — AG notification within 60 days of individual notice for breaches of 500+ Oklahoma residents (1,000+ for credit-bureau breaches).
  • Oklahoma Security Breach Notification Act (24 O.S. §§161-166) — An entity notifying 500 or more affected Oklahoma residents of a security breach must also notify the Attorney General without unreasonable delay and no later than 60 days after notifying residents; entities affecting 1,000+ residents must also notify consumer reporting agencies.
  • Security Breach Notification Act (SB 626) — threshold_residents: 500
  • Security Breach Notification Act (SB 626 amendment) — Under the Security Breach Notification Act as amended by SB 626, a covered entity must notify affected Oklahoma residents of a breach without unreasonable delay, and must separately notify the Attorney General no later than 60 days after resident notification where 500 or more residents are affected; breaches affecting fewer than 500 residents (or fewer than 1,000 for credit unions) are exempt from the AG-notice requirement.

Retention and disposalRed

No general Oklahoma data-retention-limit or disposal-duty statute was identified in this research pass.

Category narrative 63 words

SB 546 will require data protection assessments (DPIAs) for a range of processing activities from 2027. Current in-force accountability obligations are sectoral: GLBA Safeguards Rule imposes security-program duties on financial institutions; HIPAA imposes security/breach duties on healthcare covered entities/business associates; the Oklahoma Security Breach Notification Act imposes breach-notice duties generally. No general DPO-appointment threshold, ROPA requirement, or retention-limit regime was identified for Oklahoma.

Periodic update · new data 2026-11-03

The clearest controller-duty development in Oklahoma sits in the amended Security Breach Notification Act (SB 626), in force since 1 January 2026. An entity that must notify 500 or more affected Oklahoma residents of a security breach must now also notify the Attorney General without unreasonable delay and no later than 60 days after notifying residents; entities whose breach affects 1,000 or more residents must additionally notify consumer reporting agencies. The amendment also broadens the statutory definition of personal information to include government-issued identification numbers and biometric identifiers, widening the range of incidents that trigger notification duties.

The amendments introduce a reasonable-safeguards affirmative defense that rewards entities able to show proactive cybersecurity investment, and they provide an exemption from individual-notice obligations for entities already complying with the Oklahoma Hospital Cybersecurity Protection Act of 2023 or HIPAA, provided the Attorney General is still notified.

Outlook

The breach-notification regime is live now, not pending: Oklahoma entities handling the newly broadened categories of personal information, including biometric identifiers, should expect the current 60-day Attorney General notification clock to apply to qualifying incidents. Once the OCDPA takes effect in 2027, a further layer of controller obligations tied to the comprehensive privacy statute is expected to apply alongside this breach regime, though those obligations beyond breach notification were not separately detailed in the sources reviewed.

2 earlier distinct updates
Periodic update · new data 2026-10-18

The clearest controller-duty development in Oklahoma this cycle sits in the amended Security Breach Notification Act (SB 626), in force since 1 January 2026. An entity that must notify 500 or more affected Oklahoma residents of a security breach must now also notify the Attorney General without unreasonable delay and no later than 60 days after notifying residents; entities whose breach affects 1,000 or more residents must additionally notify consumer reporting agencies. The amendment also broadens the statutory definition of personal information to include government-issued identification numbers and biometric identifiers, widening the range of incidents that trigger notification duties.

The amendments introduce a reasonable-safeguards affirmative defense that rewards entities able to show proactive cybersecurity investment, and they provide an exemption from individual-notice obligations for entities already complying with the Oklahoma Hospital Cybersecurity Protection Act of 2023 or HIPAA, provided the Attorney General is still notified.

Outlook

The breach-notification regime is live now, not pending: Oklahoma entities handling the newly broadened categories of personal information, including biometric identifiers, should expect the current 60-day Attorney General notification clock to apply to qualifying incidents. Once the OCDPA takes effect in 2027, a further layer of controller obligations tied to the comprehensive privacy statute is expected to apply alongside this breach regime, though those obligations beyond breach notification were not separately detailed in the sources reviewed this cycle.

Periodic update · new data 2026-10-11

Controllers and processors in Oklahoma face obligations moving on two separate timelines. Under the enacted-but-not-yet-effective OCDPA, controllers will be subject to data protection assessment obligations, though the specific list of processing activities that trigger a mandatory assessment has not been independently confirmed from the primary enrolled bill text this cycle. Separately, and already in force since January 1, 2026, Senate Bill 626 substantially amended the Oklahoma Security Breach Notification Act, the first amendment to that Act since its original 2008 enactment. Under the amended Act, where a breach affects 500 or more Oklahoma residents, or 1,000 or more for credit reporting agencies specifically, the affected entity must notify the Oklahoma Attorney General within 60 days of providing notice to affected residents, with specified content requirements for that notification. An entity that employed reasonable safeguards and provided notice in accordance with the statute has an affirmative defense against civil penalties; where a penalty does apply, the maximum civil penalty is $150,000 per breach or series of similar breaches discovered in a single investigation.

Outlook

The breach-notification duties under SB 626 are already live and operative obligations for any entity holding Oklahoma residents' data; the OCDPA's separate assessment duty will not bite until January 1, 2027, and its precise triggering criteria remain to be confirmed against primary bill text.

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

Sources and claims (12)
  1. Probable IAPP — SB 546 requires controllers to conduct data protection assessments for a range of processing activities, effective 1 January 2027. observed
  2. Probable Federal Trade Commission — The FTC Safeguards Rule requires covered financial institutions to develop, implement, and maintain an information security program with administrative, technical, and physical safeguards designed to protect customer information. observed
  3. Probable Federal Trade Commission — Financial institutions subject to the FTC Safeguards Rule must notify the FTC as soon as possible, and no later than 30 days after discovery, of a notification event involving unauthorized acquisition of at least 500 consumers' unencrypted information. observed
  4. Probable IAPP — Oklahoma maintains a general Security Breach Notification Act requiring notice to affected residents following a breach of computerized personal information; the precise statutory citation and notification timeline were not independently re-verified against primary statutory text in this research pass. observed
  5. Probable Oklahoma Legislature — Security Breach Notification Act (SB 626) — AG notification within 60 days of individual notice for breaches of 500+ Oklahoma residents (1,000+ for credit-bureau breaches). observed
  6. Probable WilmerHale — Oklahoma Security Breach Notification Act (SB 626) — Introduces a 'reasonable safeguards' affirmative defense rewarding entities that implement proactive cybersecurity investments, and provides an individual-notice exemption for entities complying with the Oklahoma Hospital Cybersecurity Protection Act of 2023 or HIPAA, provided the Attorney General still receives notice. observed
  7. Probable LegiScan — Oklahoma Security Breach Notification Act (24 O.S. §§161-166) — An entity notifying 500 or more affected Oklahoma residents of a security breach must also notify the Attorney General without unreasonable delay and no later than 60 days after notifying residents; entities affecting 1,000+ residents must also notify consumer reporting agencies. observed
  8. Probable Oklahoma Legislature — Security Breach Notification Act (SB 626) — Threshold residents: 500 observed
  9. Probable Riddle Compliance — Security Breach Notification Act (SB 626) — Penalty cap usd: 75000_or_150000 observed
  10. Probable Riddle Compliance — Security Breach Notification Act (SB 626) — Reasonable-safeguards affirmative defense caps civil penalties at $75,000/breach versus $150,000 without safeguards/timely notice. observed
  11. Uncertain Riddle Compliance — Oklahoma Consumer Data Privacy Act (SB 546) — OKCDPA requires controllers to conduct data protection assessments for processing that presents a heightened risk of harm, including targeted-advertising profiling with legal or similarly significant effects and processing of sensitive data. observed
  12. Probable LegiScan — Security Breach Notification Act (SB 626 amendment) — Under the Security Breach Notification Act as amended by SB 626, a covered entity must notify affected Oklahoma residents of a breach without unreasonable delay, and must separately notify the Attorney General no later than 60 days after resident notification where 500 or more residents are affected; breaches affecting fewer than 500 residents (or fewer than 1,000 for credit unions) are exempt from the AG-notice requirement. observed

#

No comprehensive cross-border transfer/adequacy regime exists at the US-OK level; this is a genuine regulatory gap, not an omission.

Traffic-light rationale — RedNo comprehensive cross-border transfer/adequacy regime exists at the US-OK level; this is a genuine regulatory gap, not an omission.

Sub-modules (6)

Transfer mechanismsRed

No formal transfer-mechanism regime (adequacy/SCCs/BCRs/derogations) applies to Oklahoma as a matter of state or applicable federal general-commercial-data law.

Claims (3):

  • The United States, including Oklahoma, has no GDPR-style cross-border transfer mechanism regime (adequacy, SCCs, BCRs) applicable to general commercial personal data.
  • Oklahoma cross-border data transfer regime — No Oklahoma state-level cross-border data-transfer mechanism, adequacy regime, or data-localisation rule exists.
  • Oklahoma (state-level data protection) — Oklahoma has no state-level cross-border data-transfer restriction, adequacy mechanism, or data-localisation requirement; this module has no jurisdictional analog at the state level.

Adequacy receivedRed

Not applicable; the US does not operate an adequacy-reception framework.

Adequacy grantedRed

Not applicable; the US does not issue GDPR-style adequacy determinations.

SCCs and BCRsRed

No SCC/BCR-equivalent regime exists at Oklahoma state level; use of EU-style SCCs by OK-based entities would arise only as counterparties to EU GDPR-regulated transfers, outside this JID's own instrument.

Transfer impact assessmentRed

No TIA requirement exists under Oklahoma or applicable federal general-commercial-data law.

Data localisationRed

No general data-localisation mandate applies to commercial personal data in Oklahoma.

Claims (1):

  • No data-localisation mandate applies to general commercial personal data processed by Oklahoma-based or Oklahoma-serving entities.
Category narrative 52 words

The United States has no GDPR-style cross-border transfer/adequacy framework, and Oklahoma has no state-level data-localisation mandate or transfer-impact-assessment requirement for general commercial personal data. No adequacy decisions have been received from or granted to other regimes at the US-OK level (adequacy is not a concept used in the US federal/state privacy architecture).

Sources and claims (4)
  1. Probable Federal Trade Commission — The United States, including Oklahoma, has no GDPR-style cross-border transfer mechanism regime (adequacy, SCCs, BCRs) applicable to general commercial personal data. observed
  2. Probable Federal Trade Commission — No data-localisation mandate applies to general commercial personal data processed by Oklahoma-based or Oklahoma-serving entities. observed
  3. Probable Oklahoma Legislature — Oklahoma cross-border data transfer regime — No Oklahoma state-level cross-border data-transfer mechanism, adequacy regime, or data-localisation rule exists. observed
  4. Uncertain Oklahoma Legislature — Oklahoma (state-level data protection) — Oklahoma has no state-level cross-border data-transfer restriction, adequacy mechanism, or data-localisation requirement; this module has no jurisdictional analog at the state level. observed

#

Federal sectoral overlays (HIPAA, GLBA, COPPA) are well-established, robustly sourced (T1), and in force.

Primary frameworkHIPAA + GLBA + COPPA (federal sectoral overlays, in force)
Supervisory authorityFederal Trade Commission
Traffic-light rationale — GreenFederal sectoral overlays (HIPAA, GLBA, COPPA) are well-established, robustly sourced (T1), and in force.

Sub-modules (7)

Financial sector overlayGreen

GLBA requires financial institutions to explain information-sharing practices and safeguard sensitive data; the FTC Safeguards Rule imposes information-security-program obligations.

Claims (2):

  • The Gramm-Leach-Bliley Act requires financial institutions to explain their information-sharing practices to customers and to safeguard sensitive data, applicable to covered Oklahoma-based financial institutions.
  • Oklahoma Consumer Data Privacy Act (SB 546) — OKCDPA exempts, at the entity level, financial institutions subject to GLBA and HIPAA-covered entities/business associates, as well as state agencies, nonprofits, and higher-education institutions, and excludes individuals acting in a commercial or employment context from the 'consumer' definition.

Health sector overlayGreen

HIPAA Privacy, Security, and Breach Notification Rules govern covered entities and business associates handling protected health information; the FTC Act and FTC Health Breach Notification Rule fill gaps for non-HIPAA-covered health data (e.g., health apps).

Claims (2):

  • The HIPAA Privacy Rule sets limits and conditions on uses and disclosures of protected health information by covered entities and business associates and provides individuals with rights regarding their health information.
  • The FTC Act's obligations apply to HIPAA-covered entities and business associates, as well as to companies that collect, use, or share health information that are not required to comply with HIPAA, filling coverage gaps for non-HIPAA health data.

Telecoms and eprivacyRed

No Oklahoma-specific telecoms/eprivacy overlay (cookie-consent-style regime) was identified; federal TCPA-type protections were not independently re-verified in this pass.

Employment dataRed

No Oklahoma-specific employment-data privacy statute was identified in this research pass.

Credit and scoringAmber

The federal Fair Credit Reporting Act (FCRA) applies nationally including Oklahoma, but a dedicated verification pass on FCRA text/enforcement for this run was not performed.

educationAmber

The federal Family Educational Rights and Privacy Act (FERPA) applies nationally including Oklahoma; no OK-specific education-sector privacy overlay was identified.

insuranceRed

No Oklahoma-specific insurance-sector data-privacy overlay (e.g., genetic-information-and-insurance statute) was identified in this research pass; a search for an Oklahoma Genetic Information Privacy Act returned no confirming results.

Category narrative 59 words

Federal sectoral overlays are the dominant operative source of data-protection obligation for Oklahoma entities today: HIPAA governs health-care covered entities/business associates; GLBA (Privacy Rule + Safeguards Rule) governs financial institutions; COPPA governs operators collecting data from children under 13. No Oklahoma-specific sectoral overlays (telecoms/eprivacy, employment data, credit-scoring, education, insurance) beyond these federal baselines were identified in this research pass.

Periodic update · new data 2026-10-11

Oklahoma's breach-notification regime carries a sector-specific carve-out for health-sector entities that avoids layering duplicate notification obligations on top of existing frameworks. Entities that comply with notification requirements under the Oklahoma Hospital Cybersecurity Protection Act of 2023, or under HIPAA, and that provide the required notice to the Oklahoma Attorney General, are exempted from the individual breach-notification obligations that Senate Bill 626 otherwise imposes under the amended Security Breach Notification Act. This structure recognizes that health-sector entities already operate under sector-specific breach-notification regimes and avoids requiring parallel compliance with a second, general-purpose state notification standard when the sector-specific path is followed and the Attorney General is still informed.

Outlook

No other sector-specific carve-out or overlay was identified this cycle. Whether the Oklahoma Consumer Data Privacy Act, once effective January 1, 2027, introduces any sector-specific exemptions beyond its general employment and commercial-context exclusions has not been confirmed and would be a relevant item to track ahead of that date.

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

Sources and claims (5)
  1. Probable Federal Trade Commission — The Gramm-Leach-Bliley Act requires financial institutions to explain their information-sharing practices to customers and to safeguard sensitive data, applicable to covered Oklahoma-based financial institutions. observed
  2. Probable Federal Trade Commission — The HIPAA Privacy Rule sets limits and conditions on uses and disclosures of protected health information by covered entities and business associates and provides individuals with rights regarding their health information. observed
  3. Probable Federal Trade Commission — The FTC Act's obligations apply to HIPAA-covered entities and business associates, as well as to companies that collect, use, or share health information that are not required to comply with HIPAA, filling coverage gaps for non-HIPAA health data. observed
  4. Probable Oklahoma Legislature — EU Data Act (Regulation (EU) 2023/2854) — No Oklahoma or US-state analog comparable to the EU Data Act's smart-data, connected-product access, or cloud-switching provisions was identified. observed
  5. Probable WilmerHale — Oklahoma Consumer Data Privacy Act (SB 546) — OKCDPA exempts, at the entity level, financial institutions subject to GLBA and HIPAA-covered entities/business associates, as well as state agencies, nonprofits, and higher-education institutions, and excludes individuals acting in a commercial or employment context from the 'consumer' definition. observed

#

Targeted-advertising/sale opt-out confirmed for 2027; universal opt-out signal recognition explicitly absent; cookie law and dark-patterns provisions unconfirmed.

Primary frameworkSB 546 (effective 2027-01-01)
Supervisory authorityOklahoma Attorney General
Traffic-light rationale — AmberTargeted-advertising/sale opt-out confirmed for 2027; universal opt-out signal recognition explicitly absent; cookie law and dark-patterns provisions unconfirmed.

Sub-modules (6)

Cookies and trackersRed

No Oklahoma-specific cookie/tracker consent law was identified.

Dark patternsRed

Dark-pattern prohibitions were proposed in earlier Oklahoma privacy bill drafts (2021-era HB 1602 lineage) but confirmation of an equivalent provision surviving into enacted SB 546 was not obtained.

Opt out signalsAmber

SB 546 omits recognition of universal opt-out mechanisms.

Claims (2):

  • SB 546 omits some of the more common provisions passed by other states in recent years, including recognition of universal opt-out mechanisms and enhanced children's privacy protections.
  • Oklahoma Consumer Data Privacy Act (SB 546) — Unlike California and Colorado, OCDPA does not require businesses to honor browser-based universal opt-out signals such as Global Privacy Control; opt-out mechanisms must be disclosed in the privacy notice but signal recognition is not mandated.

Clean rooms and dcrRed

No clean-room/data-collaboration-room rule was identified for Oklahoma.

Cross context advertisingAmber

SB 546 provides opt-outs for targeted advertising and data sales as defined under the bill.

Claims (2):

  • SB 546 provides consumer opt-outs for targeted advertising and data sales as defined under the bill, effective 1 January 2027.
  • Oklahoma Consumer Data Privacy Act (SB 546) — OKCDPA defines 'sale of personal data' narrowly as the exchange of personal data for monetary consideration, and requires controllers that sell personal data or process it for targeted advertising to clearly and conspicuously disclose the opt-out process.

Direct marketingRed

No Oklahoma-specific direct-marketing consent/suppression regime beyond general federal FTC Act oversight was identified in this research pass.

Claims (2):

  • Oklahoma electronic-marketing enforcement — No Oklahoma-specific electronic-marketing enforcement statute distinct from federal TCPA/CAN-SPAM and general FTC Act Section 5 authority was located this cycle.
  • Oklahoma Telephone Solicitation Act of 2022 (OTSA) — Bars automated commercial telephonic sales calls and marketing texts without prior express written consent; sets calling-hour/frequency limits; creates a private right of action with statutory damages of $500 per violation ($1,500 if willful).
Category narrative 42 words

No Oklahoma cookie-consent law, dark-patterns prohibition, or clean-room regulation currently exists. SB 546 will introduce an opt-out right for targeted advertising and sale of personal data from 1 Jan 2027, but explicitly omits recognition of universal opt-out signals (e.g., Global Privacy Control).

Periodic update · new data 2026-11-03

The OCDPA is reported to give Oklahoma consumers an opt-out right against targeted advertising and the sale of personal data, consistent with the statute's general opt-out architecture for ordinary processing. However, one secondary source states that, unlike California and Colorado, Oklahoma's statute does not require businesses to honor browser-based universal opt-out signals such as the Global Privacy Control; this has not been independently re-verified against the primary statutory text and is treated here with corresponding caution. If accurate, this would mean Oklahoma businesses could satisfy the opt-out requirement through disclosed, site-specific mechanisms without needing to build universal-signal recognition into their consent infrastructure, a meaningful divergence from the Colorado and California model.

No Oklahoma-specific electronic-marketing enforcement statute distinct from the federal TCPA, CAN-SPAM, or general FTC Act Section 5 authority was located, suggesting direct-marketing practices in Oklahoma continue to be governed primarily by federal frameworks rather than a state-specific overlay.

Outlook

Whether Oklahoma ultimately diverges from the Colorado/California universal-opt-out-signal requirement remains to be confirmed against the OCDPA's primary text before the 2027 effective date; this is a point worth revisiting once the enrolled-bill language can be checked directly.

1 earlier distinct update
Periodic update · new data 2026-10-18

The OCDPA is reported to give Oklahoma consumers an opt-out right against targeted advertising and the sale of personal data, consistent with the statute's general opt-out architecture for ordinary processing. However, one secondary source states that, unlike California and Colorado, Oklahoma's statute does not require businesses to honor browser-based universal opt-out signals such as the Global Privacy Control; this has not been independently re-verified against the primary statutory text and is treated here with corresponding caution. If accurate, this would mean Oklahoma businesses could satisfy the opt-out requirement through disclosed, site-specific mechanisms without needing to build universal-signal recognition into their consent infrastructure, a meaningful divergence from the Colorado and California model.

No Oklahoma-specific electronic-marketing enforcement statute distinct from the federal TCPA, CAN-SPAM, or general FTC Act Section 5 authority was located this cycle, suggesting direct-marketing practices in Oklahoma continue to be governed primarily by federal frameworks rather than a state-specific overlay.

Outlook

Whether Oklahoma ultimately diverges from the Colorado/California universal-opt-out-signal requirement remains to be confirmed against the OCDPA's primary text before the 2027 effective date; this is a point worth revisiting once the enrolled-bill language can be checked directly.

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

Sources and claims (6)
  1. Probable IAPP — SB 546 omits some of the more common provisions passed by other states in recent years, including recognition of universal opt-out mechanisms and enhanced children's privacy protections. observed
  2. Probable IAPP — SB 546 provides consumer opt-outs for targeted advertising and data sales as defined under the bill, effective 1 January 2027. observed
  3. Uncertain Sheppard Mullin — Oklahoma Consumer Data Privacy Act (SB 546) — Unlike California and Colorado, OCDPA does not require businesses to honor browser-based universal opt-out signals such as Global Privacy Control; opt-out mechanisms must be disclosed in the privacy notice but signal recognition is not mandated. observed
  4. Uncertain Oklahoma Legislature — Oklahoma electronic-marketing enforcement — No Oklahoma-specific electronic-marketing enforcement statute distinct from federal TCPA/CAN-SPAM and general FTC Act Section 5 authority was located this cycle. observed
  5. Probable Sheppard Mullin — Oklahoma Consumer Data Privacy Act (SB 546) — OKCDPA defines 'sale of personal data' narrowly as the exchange of personal data for monetary consideration, and requires controllers that sell personal data or process it for targeted advertising to clearly and conspicuously disclose the opt-out process. observed
  6. Probable Legal 500 — Oklahoma Telephone Solicitation Act of 2022 (OTSA) — Bars automated commercial telephonic sales calls and marketing texts without prior express written consent; sets calling-hour/frequency limits; creates a private right of action with statutory damages of $500 per violation ($1,500 if willful). observed

#

No confirmed Oklahoma-specific regime in this domain; evidence is thin to absent across all sub-modules.

Traffic-light rationale — RedNo confirmed Oklahoma-specific regime in this domain; evidence is thin to absent across all sub-modules.

Sub-modules (6)

Profiling restrictionsAmber

A profiling opt-out is plausible by analogy to the Virginia-model framework underlying SB 546, but was not independently confirmed in the sources reviewed.

Claims (1):

  • SB 546's Virginia-CDPA-modeled framework may include a profiling opt-out right consistent with other Virginia-model state laws, but an OK-specific profiling-restriction clause was not independently confirmed in the sources reviewed.

Automated decision making transparencyRed

No ADM transparency/explanation-right provision was confirmed for SB 546.

AI risk assessmentsRed

No Oklahoma AI-specific risk-assessment statute was identified.

Biometric regimeRed

No Oklahoma biometric-data statute analogous to Illinois BIPA was identified.

Claims (2):

  • Security Breach Notification Act (SB 626) — effective_date: 2026-01-01
  • Security Breach Notification Act (SB 626) — Includes government-issued ID numbers, unique electronic identifiers and biometric identifiers (fingerprints, iris scans), effective 2026-01-01.

Genetic dataRed

A search for an Oklahoma Genetic Information Privacy Act returned no Oklahoma-specific results (only other-state examples such as Maryland).

State surveillance carveoutsRed

No Oklahoma-specific state-surveillance carveout provision was researched in this pass.

Category narrative 42 words

No Oklahoma-specific biometric-privacy statute (analogous to Illinois BIPA), genetic-data statute, AI-risk-assessment law, or ADM-transparency regime was identified in this research pass. Profiling-related opt-outs may exist within SB 546's rights package by analogy to the Virginia model, but this was not independently confirmed.

Periodic update · new data 2026-10-18

The OCDPA is understood to require affirmative opt-in consent before a business may process biometric data, placing biometric identifiers within the sensitive-data tier alongside precise geolocation and known children's data. Separately, the amended Security Breach Notification Act (SB 626) now includes biometric identifiers within its broadened definition of personal information, meaning a breach involving biometric data would trigger the same resident- and Attorney-General-notification duties described above.

On automated decision-making, the OCDPA's consumer opt-out right is reported to extend to profiling that produces legal or similarly significant effects, giving Oklahoma consumers a mechanism to decline such processing. No dedicated Oklahoma statute establishing algorithmic-risk-assessment or audit obligations for automated decision systems was identified.

Outlook

Biometric data sits at the intersection of two Oklahoma instruments once the OCDPA takes effect in 2027: opt-in consent duties under the comprehensive privacy statute, and expanded breach-notification duties already in force under SB 626. Businesses processing biometric identifiers in Oklahoma are therefore already within the amended breach regime even before the OCDPA's consent requirements become operative.

1 earlier distinct update
Periodic update · new data 2026-10-11

Oklahoma's governance of biometric data advanced this cycle through an expansion of the breach-notification statute rather than through a dedicated biometric-privacy law. Senate Bill 626, effective January 1, 2026, broadened the definition of personal information under the Oklahoma Security Breach Notification Act to include government-issued identification numbers, unique electronic identifiers, and biometric data such as fingerprints and iris scans. The practical effect is that a breach exposing these newly covered categories now triggers the same notification duties, including the Attorney General notification requirement for breaches affecting 500 or more residents, as a breach exposing more traditional categories of personal information such as Social Security numbers or financial account details. Oklahoma does not have a dedicated biometric-information-privacy statute comparable to a standalone biometric-privacy act; this expansion operates entirely within the breach-notification framework rather than establishing collection-consent or retention-limitation rules for biometric data outside the breach context.

Outlook

Whether Oklahoma will move toward a dedicated biometric-collection-and-consent regime, as distinct from the breach-notification expansion already in force, has not been signaled this cycle and remains an open structural gap relative to states with standalone biometric privacy statutes.

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

Sources and claims (3)
  1. Uncertain IAPP — SB 546's Virginia-CDPA-modeled framework may include a profiling opt-out right consistent with other Virginia-model state laws, but an OK-specific profiling-restriction clause was not independently confirmed in the sources reviewed. observed
  2. Probable Sheppard Mullin — Security Breach Notification Act (SB 626) — Effective date: 2026-01-01 observed
  3. Probable Sheppard Mullin — Security Breach Notification Act (SB 626) — Includes government-issued ID numbers, unique electronic identifiers and biometric identifiers (fingerprints, iris scans), effective 2026-01-01. observed

#

COPPA federal baseline robustly confirmed; SB 546 explicitly omits enhanced children's protections; other sub-modules largely unconfirmed/absent.

Primary frameworkCOPPA (federal, in force)
Supervisory authorityFederal Trade Commission
Traffic-light rationale — AmberCOPPA federal baseline robustly confirmed; SB 546 explicitly omits enhanced children's protections; other sub-modules largely unconfirmed/absent.

Sub-modules (5)

Age verificationRed

No Oklahoma-specific age-verification statute (e.g., social-media age-verification law) was identified in this research pass.

Minor profiling bansAmber

SB 546 explicitly omits enhanced children's privacy protections found in some other state comprehensive privacy laws.

Claims (1):

  • SB 546 omits enhanced children's privacy protections found in some other states' comprehensive privacy laws, leaving COPPA as the primary child-data safeguard in Oklahoma.

Education settingsAmber

The federal FERPA regime applies nationally including Oklahoma; no OK-specific education-settings privacy rule was identified in this research pass.

Dependent adultsRed

No Oklahoma-specific dependent-adults data-protection provision was identified in this research pass.

Category narrative 45 words

The federal COPPA regime applies nationally including Oklahoma, requiring parental consent for collection of personal information from children under 13. SB 546 explicitly does NOT add enhanced children's-privacy provisions beyond this federal baseline. No Oklahoma-specific age-verification, minor-profiling ban, education-settings rule, or dependent-adults protection was identified.

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

Sources and claims (2)
  1. Probable Federal Trade Commission — The Children's Online Privacy Protection Act (COPPA) gives parents control over what information websites can collect from their children, applicable to covered Oklahoma-serving operators. observed
  2. Probable IAPP — SB 546 omits enhanced children's privacy protections found in some other states' comprehensive privacy laws, leaving COPPA as the primary child-data safeguard in Oklahoma. observed

#

Enforcement architecture for the 2027 regime is well-characterized (exclusive AG enforcement, cure period, no private right of action); current enforcement-activity and regulator-capacity data are thin.

Primary frameworkSB 546 (effective 2027-01-01) + FTC Act Section 5 (in force)
Supervisory authorityOklahoma Attorney General
Traffic-light rationale — AmberEnforcement architecture for the 2027 regime is well-characterized (exclusive AG enforcement, cure period, no private right of action); current enforcement-activity and regulator-capacity data are thin.

Sub-modules (6)

Regulator powers and penaltiesAmber

SB 546 grants the Oklahoma Attorney General exclusive enforcement authority with a non-sunsetting 30-day cure provision.

Claims (8):

  • SB 546 will take force 1 January 2027 and offers a 30-day cure provision under exclusive Attorney General enforcement that does not sunset.
  • Oklahoma Consumer Data Privacy Act (SB 546) — Enforced exclusively by the Oklahoma Attorney General; one secondary source states a penalty figure of $7,500 per violation and notes the law carries a permanent cure period before enforcement, higher applicability thresholds, and broad entity-level exemptions compared to peer states.
  • Oklahoma Consumer Data Privacy Act (SB 546) — penalty_cap_usd: 7500
  • Oklahoma Consumer Data Privacy Act (SB 546) — AG-exclusive enforcement, 30-day cure period, civil penalties up to $7,500/violation.
  • Oklahoma Consumer Data Privacy Act (SB 546) — OKCDPA enforcement rests exclusively with the Oklahoma Attorney General; there is no private right of action; violators receive a permanent (non-sunsetting) 30-day cure period before penalties may be imposed, and the maximum civil penalty is $7,500 per violation.
  • Oklahoma Consumer Data Privacy Act (SB 546, 2026) — $7,500 per violation, AG-exclusive, 30-day cure
  • Oklahoma Consumer Data Privacy Act (SB 546, 2026) — $7,500 per violation, recoverable solely by the Attorney General together with reasonable attorney's fees and investigative expenses; mandatory 30-day non-sunsetting cure period precedes any enforcement action
  • Oklahoma Security Breach Notification Act, as amended by SB 626 — AG must be notified of breaches affecting 500+ residents generally (1,000+ for credit bureaus); civil penalty up to $150,000; credit-bureau notification required at 1,000+ residents notified.

Enforcement activity indexRed

No Oklahoma-specific privacy-enforcement action tally (breach-notification enforcement or FTC actions specifically targeting OK entities) was identified in this research pass.

Regulator funding and capacityRed

No specific funding or headcount data for the Oklahoma AG's Consumer Protection Unit relevant to privacy enforcement was researched in this pass.

Collective redress and class actionsAmber

SB 546's exclusive AG enforcement model implies no collective/class-action mechanism for consumers under the Act itself.

Claims (1):

  • Because SB 546 vests exclusive enforcement in the Attorney General, no consumer collective-redress or class-action mechanism is created directly by the Act.

Private right of actionAmber

SB 546 provides exclusive Attorney General enforcement, precluding a private right of action under the Act; whether the existing breach-notification statute separately allows a private right of action was not independently confirmed.

Claims (2):

  • SB 546 does not create a private right of action, enforcement being exclusive to the Oklahoma Attorney General under a non-sunsetting 30-day cure provision.
  • Oklahoma Consumer Data Privacy Act (SB 546) and Security Breach Notification Act — No private right of action exists under OCDPA or the Security Breach Notification Act; enforcement is reserved exclusively to the Oklahoma Attorney General.

Recent developments 180dAmber

Within the 180 days preceding the dispatch date (2026-08-06), Oklahoma's House gave final passage to SB 546 on 19 February 2026 (84-4 vote), and the bill was reported signed into law in March 2026 — the single most material recent development for this JID.

Claims (1):

  • On 19 February 2026, the Oklahoma House approved final passage of Senate Bill 546 on an 84-4 vote, sending the state's first comprehensive consumer data privacy law toward enactment.
Category narrative 59 words

Under SB 546, enforcement will be exclusive to the Oklahoma Attorney General, with a non-sunsetting 30-day cure period and no private right of action. Current in-force enforcement relies on FTC Section 5 authority and AG breach-notification enforcement. This is a recent development (SB 546 legislative passage and reported signature occurred within the last ~180 days of the dispatch date).

Periodic update · new data 2026-11-08

The Oklahoma Consumer Data Privacy Act is understood to cap civil penalties at $7,500 per violation. These penalties are recoverable solely by the Attorney General, consistent with the Act's exclusive-enforcement structure, and the Attorney General may also recover reasonable attorney's fees and investigative expenses alongside the capped penalty. There is no private right of action under the statute, so affected individuals cannot pursue their own civil claims for a violation.

Before any enforcement action can be brought, the controller or processor alleged to be in violation is understood to be entitled to a thirty-day period in which to cure the violation. Unlike some comparable state statutes, this cure right is reported to be non-sunsetting - it does not expire after an initial grace window but remains available on an ongoing basis. That design meaningfully softens the practical bite of the penalty cap, since a corrected violation within the cure window is understood to avoid penalty exposure altogether regardless of when the Act has been in force.

Outlook

Once the statute takes effect, the Attorney General's approach to use of the cure period in practice - and whether guidance is issued narrowing what qualifies as a timely cure - will be the main indicator of how the enforcement provisions are intended to function in practice.

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

Both the OCDPA and the Security Breach Notification Act are enforced exclusively by the Oklahoma Attorney General; neither statute creates a private right of action for affected consumers. The OCDPA is reported to carry a permanent cure period before the Attorney General may bring an enforcement action, together with comparatively high applicability thresholds and broad entity-level exemptions relative to peer states, a combination that would make Oklahoma one of the more enforcement-light comprehensive privacy regimes among enacted US state laws if these reported features hold up against the primary text. One secondary source states a penalty figure of $7,500 per violation, though this has not been independently corroborated and is treated with caution pending confirmation.

No Oklahoma Attorney General enforcement actions brought under the state's pre-existing general consumer-protection authority were reviewed, so this assessment speaks only to the statutory enforcement architecture rather than to any track record of its use.

Outlook

Enforcement exposure under the OCDPA will only begin to materialise after the 1 January 2027 effective date, and even then the permanent cure period means the Attorney General must afford businesses an opportunity to remedy violations before pursuing action. The reported $7,500 penalty figure and the precise cure-period mechanics are worth confirming directly against the enrolled bill as the effective date approaches.

Periodic update · new data 2026-10-18

Both the OCDPA and the Security Breach Notification Act are enforced exclusively by the Oklahoma Attorney General; neither statute creates a private right of action for affected consumers. The OCDPA is reported to carry a permanent cure period before the Attorney General may bring an enforcement action, together with comparatively high applicability thresholds and broad entity-level exemptions relative to peer states, a combination that would make Oklahoma one of the more enforcement-light comprehensive privacy regimes among enacted US state laws if these reported features hold up against the primary text. One secondary source states a penalty figure of $7,500 per violation, though this has not been independently corroborated and is treated with caution pending confirmation.

No Oklahoma Attorney General enforcement actions brought under the state's pre-existing general consumer-protection authority were reviewed this cycle, so this assessment speaks only to the statutory enforcement architecture rather than to any track record of its use.

Outlook

Enforcement exposure under the OCDPA will only begin to materialise after the 1 January 2027 effective date, and even then the permanent cure period means the Attorney General must afford businesses an opportunity to remedy violations before pursuing action. The reported $7,500 penalty figure and the precise cure-period mechanics are worth confirming directly against the enrolled bill as the effective date approaches.

Periodic update · new data 2026-10-11

Oklahoma's enforcement architecture for data protection is set on two separate statutory tracks with different timelines and different penalty structures. Under the enacted-but-not-yet-effective OCDPA, 75A O.S. §312 requires the Attorney General to give a controller or processor written notice and a permanent 30-day opportunity to cure before bringing an enforcement action; under §313, an uncured violation is subject to a civil penalty not to exceed $7,500 per violation, and the Act creates no private right of action, meaning consumers cannot sue directly for a violation. This cure-period and penalty-cap structure will not become operative until January 1, 2027. Separately, and already in force, the amended Security Breach Notification Act carries its own penalty structure: civil penalties up to $150,000 per breach or series of related breaches, subject to the affirmative-defense carve-out for entities that employed reasonable safeguards and gave compliant notice, and certain breach-notification violations under 21 O.S. §20M carry criminal penalties of a fine of not less than $5,000 and not more than $100,000, imprisonment, or both.

Outlook

The breach-notification enforcement track, including its criminal exposure, is live today; the OCDPA's Attorney-General-only enforcement track, with its mandatory cure period, activates January 1, 2027. No findings this cycle rest on a primary legislature.gov or Attorney General source fetched directly; all are secondary commentary, a gap worth closing before the OCDPA's effective date approaches.

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

Sources and claims (12)
  1. Probable IAPP — SB 546 will take force 1 January 2027 and offers a 30-day cure provision under exclusive Attorney General enforcement that does not sunset. observed
  2. Probable IAPP — Because SB 546 vests exclusive enforcement in the Attorney General, no consumer collective-redress or class-action mechanism is created directly by the Act. observed
  3. Probable IAPP — SB 546 does not create a private right of action, enforcement being exclusive to the Oklahoma Attorney General under a non-sunsetting 30-day cure provision. observed
  4. Probable IAPP — On 19 February 2026, the Oklahoma House approved final passage of Senate Bill 546 on an 84-4 vote, sending the state's first comprehensive consumer data privacy law toward enactment. observed
  5. Uncertain PrivacyLawMap — Oklahoma Consumer Data Privacy Act (SB 546) — Enforced exclusively by the Oklahoma Attorney General; one secondary source states a penalty figure of $7,500 per violation and notes the law carries a permanent cure period before enforcement, higher applicability thresholds, and broad entity-level exemptions compared to peer states. observed
  6. Probable Oklahoma Legislature — Oklahoma Consumer Data Privacy Act (SB 546) and Security Breach Notification Act — No private right of action exists under OCDPA or the Security Breach Notification Act; enforcement is reserved exclusively to the Oklahoma Attorney General. observed
  7. Probable WilmerHale — Oklahoma Consumer Data Privacy Act (SB 546) — Penalty cap usd: 7500 observed
  8. Probable WilmerHale — Oklahoma Consumer Data Privacy Act (SB 546) — AG-exclusive enforcement, 30-day cure period, civil penalties up to $7,500/violation. observed
  9. Uncertain PrivacyLawMap — Oklahoma Consumer Data Privacy Act (SB 546) — OKCDPA enforcement rests exclusively with the Oklahoma Attorney General; there is no private right of action; violators receive a permanent (non-sunsetting) 30-day cure period before penalties may be imposed, and the maximum civil penalty is $7,500 per violation. observed
  10. Probable Oklahoma Legislature — Oklahoma Consumer Data Privacy Act (SB 546, 2026) — $7,500 per violation, AG-exclusive, 30-day cure observed
  11. Probable Oklahoma Legislature — Oklahoma Consumer Data Privacy Act (SB 546, 2026) — $7,500 per violation, recoverable solely by the Attorney General together with reasonable attorney's fees and investigative expenses; mandatory 30-day non-sunsetting cure period precedes any enforcement action observed
  12. Probable Constangy, Brooks, Smith & Prophete LLP — Oklahoma Security Breach Notification Act, as amended by SB 626 — AG must be notified of breaches affecting 500+ residents generally (1,000+ for credit bureaus); civil penalty up to $150,000; credit-bureau notification required at 1,000+ residents notified. 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), 78 claim(s) (78 category placement(s)), 45 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: upheld (8 confirmed against the cited source; 4 could not be checked). 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 Rightsrestriction and objection
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 & Redressregulator powers and penalties
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