Data Protection Monitor
Global Privacy & Data Protection Intelligence

Colorado, USA Data Protection & Privacy Regulation

US-CO schema gdpri-v2 trajectory: not yet assessed hybrid regime overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 88 claims · 64 sources in the cumulative register

Colorado's SB 189, enacted in 2026, overhauls the state's AI Act by replacing its original risk-based duty-of-care framework with a disclosure and transparency model, and pushes back the law's principal effective date from June 30, 2026 to January 1, 2027.

Data collected Data published

AI-assembled from cited sources

Not covered: Cross-Border & Adequacy. Not fully checked this cycle: Children & Vulnerable Groups, Enforcement & Redress (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 11 binding instruments
Supervisory authorityColorado Attorney General
Next milestone
DEC312026
SB 24-041 minors'-provisions 60-day cure period sunset
Record & confidence mix87 claims · 47 sources · machine-compiled
7 Confirmed72 Probable1 Indicative7 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 Colorado, USA is covered once, on the United States page. This page covers Colorado, USA’s own layer: its own law, regulators and enforcement.

Jurisdiction brief

Latest update · 8 November 2026

Lead Signal

Colorado has enacted SB26-189, an Automated Decision-Making Technology law signed on 14 May 2026 that replaces the stalled Colorado AI Act (SB24-205) before that earlier statute ever took effect. The new law is understood to require developers and deployers of automated decision-making technology that materially influences a consequential decision to provide a thirty-day explanation of any adverse outcome, to offer the affected individual correction rights and human review, and to retain records for three years. Enforcement sits exclusively with the Colorado Attorney General, who is understood to be bound to a mandatory sixty-day cure period through 2030 unless a violation is knowing or repeated. The law is not yet in force: it is enacted but takes effect from 1 January 2027, giving covered developers and deployers a runway before the explanation, correction, and recordkeeping duties begin to bite.

Key regulatory facts for Colorado, USA
Key regulatory facts for Colorado, USA
Regulatory DimensionColorado, USA Standing Position
JurisdictionColorado, USA (US-CO)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 88 sourced findings)
Regulator & FrameworkMature, clearly-scoped statute with an active regulator and settled thresholds; no registration gap materially affects compliance certainty.
Lawful Processing & Special DataConsent and sensitive-data rules are well defined in statute and implementing rules (4 CCR 904-3).
Data Subject RightsRights and deadlines are clearly codified and operative since 2023.
Controller/Processor DutiesCore accountability, security, and breach duties are robust and in force, but the absence of DPO/ROPA-equivalent obligations creates a structural gap relative to GDPR-style regimes.
Primary Instruments CitedColorado, USA Official Instrument (coag.gov 2026-10-06-ADMT-Chatbot-Act-Rule), Colorado Department of Law, OneTrust DataGuidance, Usercentrics, Privacy Rights Clearinghouse
Last Confirmed / Updated (64 sources in cumulative register)

#

Mature, clearly-scoped statute with an active regulator and settled thresholds; no registration gap materially affects compliance certainty.

Primary frameworkColorado Privacy Act, Colo. Rev. Stat. §§ 6-1-1301 to 6-1-1313
Traffic-light rationale — GreenMature, clearly-scoped statute with an active regulator and settled thresholds; no registration gap materially affects compliance certainty.

Sub-modules (5)

Regulator and authorityGreen

The Colorado AG (Department of Law) is the primary CPA regulator; District Attorneys share enforcement authority.

Claims (5):

  • The Colorado Attorney General is the primary regulator and enforcement authority for the Colorado Privacy Act.
  • Colorado Privacy Act §6-1-1313 — Colorado Attorney General and district attorneys; no private right of action; mandatory cure period sunset 2025-01-01 except for minors'-protection violations (cured until 2026-12-31).
  • Colorado Department of Law — Began formal enforcement of the Colorado Privacy Act in July 2023; full enforcement discretion since the cure period's sunset on January 1, 2025.
  • Colorado Attorney General — The Colorado AG's Office and District Attorneys hold sole enforcement power under the CPA; no private right of action exists.
  • Colorado Privacy Act (CPA) — 2025-01-01 (general); minors'-data cure continues through 2026-12-31

Act and instrumentsGreen

Primary instrument is SB 21-190 (CPA), in force since July 1, 2023, subsequently amended by SB 24-041 and HB 24-1130.

Claims (6):

  • The Colorado Privacy Act (Senate Bill 21-190) was signed into law on July 7, 2021 and became effective July 1, 2023.
  • Colorado Department of Law held the formal public rulemaking hearing on its proposed ADMT and Chatbot Safety rules (4 CCR 904-6) on 2026-10-26.
  • The Colorado Department of Law released a revised interim draft of the Automated Decision-Making Technology & Conversational AI Service Rules (4 CCR 904-6) on 6 Oct 2026, ahead of a formal rulemaking hearing on 26 Oct 2026; written comments close that night at 11:59 p.m. Mountain Time.
  • Colorado AG held the formal ADMT/Chatbot Safety rulemaking hearing on 2026-10-26; no final rules adopted as of 2026-10-25.
  • Colorado Privacy Act (SB21-190) — Rights to access, delete, correct, and opt out of sale/targeted-advertising/profiling uses of personal data, effective July 1, 2023.
  • SB25-276, signed May 23, 2025, amends Part 13 of the CPA to add precise geolocation data as covered Sensitive Data.

Material scopeGreen

Applies to controllers meeting a 100,000-consumer threshold or a 25,000-consumer-plus-data-sale-revenue threshold, over personal data of Colorado residents.

Claims (1):

  • The CPA applies to controllers conducting business in or targeting Colorado residents that control or process the personal data of 100,000 or more consumers per calendar year, or that derive revenue from data sales and process the data of 25,000 or more consumers.

Territorial scopeGreen

Extraterritorial application to any controller conducting business in or targeting Colorado residents, irrespective of controller location.

Claims (1):

  • The CPA applies to any controller that conducts business in Colorado or produces/delivers commercial products or services intentionally targeted to Colorado residents, regardless of the controller's own location.

Regulator registration and filingAmber

No general controller registration or filing obligation exists under the CPA; the AG instead relies on rulemaking and complaint/enforcement mechanisms.

Category narrative 65 words

Colorado is governed by the Colorado Privacy Act (CPA), a comprehensive consumer-privacy statute enforced exclusively by the Colorado Attorney General (with District Attorney co-enforcement authority), layered over federal sectoral statutes (HIPAA, GLBA, COPPA, FCRA) that carve out entity- and data-level exemptions. The CPA applies extraterritorially to any controller targeting Colorado residents that meets defined processing-volume or data-sale-revenue thresholds; there is no separate controller registration/filing regime.

Periodic update · new data 2026-10-18

The Colorado Department of Law released a revised interim draft of the Automated Decision-Making Technology and Conversational AI Service Rules, codified at 4 CCR 904-6, on 6 October 2026. This revision precedes a formal rulemaking hearing scheduled for 26 October 2026, with written comments on the revised draft closing that same night at 11:59 p.m. Mountain Time. The rulemaking implements the Colorado ADMT Act (SB 26-189) and the Chatbot Safety Act (HB 26-1263), both of which take effect 1 January 2027, meaning the Department of Law is working against a fixed statutory deadline to finalize implementing rules.

The revised draft notably changes the threshold test for determining when automated decision-making technology 'materially influences' a consequential decision, a definition that governs the scope of the entire regulatory regime. Commentary describes the revision as moving closer to, though not identical to, the approach taken under California's CCPA ADMT regulation, including the addition of a rebuttable presumption; this represents a shift from the two competing standards that had been floated in an earlier 11 August 2026 notice of hearing. The definition remains unsettled pending the 26 October hearing, and the Department of Law's own framework document is the authoritative source for its current state.

Outlook

The 26 October 2026 hearing is the operative date for this module: whatever threshold definition emerges there will determine the practical scope of the entire ADMT and Chatbot Safety Act regime before its 1 January 2027 effective date. Stakeholders submitting comments must do so by 11:59 p.m. Mountain Time on 26 October 2026, the same day as the hearing.

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

The Colorado Privacy Act vests enforcement authority in the Colorado Attorney General and district attorneys; the statute provides no private right of action for consumers. The general mandatory cure-notice period, under which the Attorney General was required to offer businesses an opportunity to cure an alleged violation before pursuing enforcement, sunset on 1 January 2025. A narrower cure opportunity survives specifically for violations of the Act's minors'-protection provisions, and that cure opportunity is scheduled to end on 31 December 2026.

Outlook

From 1 January 2027, Colorado's enforcement architecture gains a second active statute: SB26-189's automated-decision-making-technology regime comes into effect, administered through the same Attorney General's office. The sunset of the minors'-protection cure period on 31 December 2026 falls just before that effective date, meaning the Attorney General's enforcement discretion over both regimes tightens within the same short window.

Sources and claims (13)
  1. Confirmed OneTrust DataGuidance — The Colorado Attorney General is the primary regulator and enforcement authority for the Colorado Privacy Act. observed
  2. Confirmed OneTrust DataGuidance — The Colorado Privacy Act (Senate Bill 21-190) was signed into law on July 7, 2021 and became effective July 1, 2023. observed
  3. Confirmed OneTrust DataGuidance — The CPA applies to controllers conducting business in or targeting Colorado residents that control or process the personal data of 100,000 or more consumers per calendar year, or that derive revenue from data sales and process the data of 25,000 or more consumers. observed
  4. Confirmed OneTrust DataGuidance — The CPA applies to any controller that conducts business in Colorado or produces/delivers commercial products or services intentionally targeted to Colorado residents, regardless of the controller's own location. observed
  5. Probable Usercentrics — Colorado Department of Law held the formal public rulemaking hearing on its proposed ADMT and Chatbot Safety rules (4 CCR 904-6) on 2026-10-26. observed
  6. Probable https://coag.gov/app/uploads/2026/10/2026.10.06-ADMT-Chatbot-Act-Rulemaking-Interim-Draft-Redline.pdf — The Colorado Department of Law released a revised interim draft of the Automated Decision-Making Technology & Conversational AI Service Rules (4 CCR 904-6) on 6 Oct 2026, ahead of a formal rulemaking hearing on 26 Oct 2026; written comments close that night at 11:59 p.m. Mountain Time.
  7. Probable Usercentrics — Colorado AG held the formal ADMT/Chatbot Safety rulemaking hearing on 2026-10-26; no final rules adopted as of 2026-10-25. observed
  8. Probable Privacy Rights Clearinghouse — Colorado Privacy Act §6-1-1313 — Colorado Attorney General and district attorneys; no private right of action; mandatory cure period sunset 2025-01-01 except for minors'-protection violations (cured until 2026-12-31). observed
  9. Confirmed Usercentrics — Colorado Department of Law — Began formal enforcement of the Colorado Privacy Act in July 2023; full enforcement discretion since the cure period's sunset on January 1, 2025. observed
  10. Confirmed FDATA — Colorado Privacy Act (SB21-190) — Rights to access, delete, correct, and opt out of sale/targeted-advertising/profiling uses of personal data, effective July 1, 2023. observed
  11. Probable Usercentrics — Colorado Attorney General — The Colorado AG's Office and District Attorneys hold sole enforcement power under the CPA; no private right of action exists. observed
  12. Probable Hunton Andrews Kurth — SB25-276, signed May 23, 2025, amends Part 13 of the CPA to add precise geolocation data as covered Sensitive Data. observed
  13. Probable Usercentrics — Colorado Privacy Act (CPA) — 2025-01-01 (general); minors'-data cure continues through 2026-12-31 observed

#

Consent and sensitive-data rules are well defined in statute and implementing rules (4 CCR 904-3).

Primary frameworkColorado Privacy Act, Colo. Rev. Stat. § 6-1-1303; CPA Rules 4 CCR 904-3
Traffic-light rationale — GreenConsent and sensitive-data rules are well defined in statute and implementing rules (4 CCR 904-3).

Sub-modules (4)

Lawful basesGreen

CPA uses an opt-out consent model for standard processing rather than enumerated lawful bases; opt-in consent is mandatory for sensitive data.

Claims (1):

  • Controllers are prohibited from processing sensitive data without first obtaining consumer consent, which must be freely given, specific, informed, and unambiguous.

Special categoriesGreen

Sensitive data categories include racial/ethnic origin, religious beliefs, mental/physical health, sexual orientation, citizenship status, genetic and biometric data, and neural data (post-HB24-1130).

Claims (5):

  • Colorado's definition of sensitive data includes racial and ethnic origin, religious beliefs, and genetic and biometric data, among other categories.
  • SB25-276 — Adds precise geolocation data as a category of CPA-sensitive data requiring prior opt-in consumer consent.
  • Colorado biometric data law — Colorado law prohibits collection of biometric identifiers unless the controller obtains consumer consent, and prohibits sale/lease/trade of biometric data.
  • Colorado SB25-276 — Adds precise geolocation data as covered Sensitive Data under CPA Part 13, requiring opt-in consumer consent before processing.
  • SB25-276 — sale of sensitive data

Pseudonymisation and anonymisationGreen

The CPA defines pseudonymous data as data that cannot be attributed to a specific individual absent separately-held additional information under technical/organizational safeguards; de-identified data is excluded from personal-data scope entirely.

Claims (1):

  • The CPA defines pseudonymous data as personal data that can no longer be attributed to a specific individual without additional information kept separately under technical and organizational safeguards.
Category narrative 57 words

The CPA does not use a GDPR-style enumerated lawful-basis model; instead it relies on an opt-out consent architecture supplemented by mandatory opt-in consent for sensitive/sensitive-inference data and for processing a known child's data. Sensitive categories include racial/ethnic origin, religious beliefs, mental/physical health, sex life/orientation, citizenship status, genetic and biometric data, and (as of HB 24-1130) neural data.

Periodic update · new data 2026-09-28

Colorado law prohibits collection of biometric identifiers unless the controller obtains consumer consent, and separately prohibits the sale, lease or trade of biometric data outright. These protections, effective July 1, 2025, establish biometric identifiers as a form of special-category data subject to heightened lawful-basis requirements beyond the general Colorado Privacy Act consent and notice framework. This creates a materially higher bar for any Colorado-facing business processing biometric identifiers, such as facial-recognition or fingerprint-based authentication systems, since consent must be affirmatively obtained before collection, and the data cannot enter commercial secondary markets through sale, lease or trade under any circumstance, regardless of consent status for that further transfer.

The consent requirement for biometric collection sits alongside Colorado's broader special-categories framework, which also separately designates precise geolocation data as covered Sensitive Data following SB25-276's May 2025 amendment to CPA Part 13, though that amendment is a stable, previously established baseline feature this cycle rather than a new development.

The biometric-consent finding here is corroborated at Tier-3 practitioner-analysis level and cross-referenced against the effective date of the underlying biometric statute (understood to be HB24-1130), giving it Confirmed-tier confidence despite the absence this cycle of a direct Tier-1 statutory text retrieval.

Outlook

Colorado-facing controllers processing biometric identifiers should ensure consent-capture mechanisms are in place ahead of any collection activity, and should audit any existing data-sharing arrangements involving biometric data to confirm none constitute a prohibited sale, lease or trade under the current framework.

1 earlier distinct update
Periodic update · new data 2026-09-05

Colorado's rules on sensitive and specially-regulated data categories expanded materially this cycle through two distinct amendments to the Colorado Privacy Act. SB25-276 added precise geolocation data as a category of sensitive data, meaning controllers must now obtain a consumer's prior opt-in consent before processing precise geolocation data, placing it alongside racial or ethnic origin, health data, and biometric data as categories requiring heightened consent under the Act. SB25-276 also clarifies that controllers may not sell precise geolocation data without that same prior opt-in consent, closing a potential gap where consent obtained for processing might otherwise have been read to extend to sale as a downstream use.

Separately, HB24-1130 imposes a distinct lawful-processing-adjacent duty specific to biometric identifiers and biometric data: controllers of such data must adopt a written policy that includes a retention schedule and a data-security-incident-response protocol, effective 2025-07-01. This obligation extends beyond the consumer context into the employment relationship, meaning Colorado employers that collect biometric identifiers, such as fingerprint or facial-recognition data used for workplace access control, fall within the statute's reach even though the underlying data may never be processed for a consumer-facing purpose.

The geolocation and biometric amendments also interact with the Colorado Privacy Act's existing data protection assessment requirement. Processing of sensitive data, including now precise geolocation data, already triggers the requirement to conduct a data protection assessment weighing the benefits of processing against the risks to consumers; controllers that begin treating geolocation data as sensitive under SB25-276 must fold that category into their existing data-protection-assessment practice. Biometric data was already treated as sensitive data under the Colorado Privacy Act prior to this cycle, so HB24-1130's contribution is to layer an additional, freestanding documentation duty on top of the assessment obligation that already applied.

Read together, these two amendments reflect a pattern of category-specific tightening rather than a wholesale rewrite of the Colorado Privacy Act's lawful-processing architecture: the Act's core lawful-basis structure remains unchanged, but the population of data categories requiring heightened consent, and the population of controllers subject to category-specific documentation duties, has both grown. For multistate controllers, the geolocation expansion is notable because it moves Colorado's sensitive-data definition further from a lowest-common-denominator baseline shared uniformly across US state privacy laws.

Outlook

Controllers should expect continued category-specific tightening of Colorado's sensitive-data regime as a plausible pattern going forward, given that this cycle's SB25-276 and HB24-1130 amendments both followed this template rather than reopening the Act's foundational lawful-processing structure. The practical compliance question for the coming cycle is whether the Attorney General's office treats the geolocation opt-in requirement and the biometric retention-and-incident-response policy as areas of active enforcement focus.

Sources and claims (8)
  1. Confirmed International Association of Privacy Professionals — Controllers are prohibited from processing sensitive data without first obtaining consumer consent, which must be freely given, specific, informed, and unambiguous. observed
  2. Confirmed OneTrust DataGuidance — Where personal data concerns a known child, controllers must obtain consent from the child's parent or lawful guardian before processing sensitive data. observed
  3. Confirmed OneTrust DataGuidance — Colorado's definition of sensitive data includes racial and ethnic origin, religious beliefs, and genetic and biometric data, among other categories. observed
  4. Confirmed OneTrust DataGuidance — The CPA defines pseudonymous data as personal data that can no longer be attributed to a specific individual without additional information kept separately under technical and organizational safeguards. observed
  5. High McDermott Will & Schulte — SB25-276 — Adds precise geolocation data as a category of CPA-sensitive data requiring prior opt-in consumer consent. observed
  6. Probable FDATA — Colorado biometric data law — Colorado law prohibits collection of biometric identifiers unless the controller obtains consumer consent, and prohibits sale/lease/trade of biometric data. observed
  7. Probable Hunton Andrews Kurth — Colorado SB25-276 — Adds precise geolocation data as covered Sensitive Data under CPA Part 13, requiring opt-in consumer consent before processing. observed
  8. Probable Hunton Andrews Kurth — SB25-276 — sale of sensitive data observed

#

Rights and deadlines are clearly codified and operative since 2023.

Primary frameworkColorado Privacy Act, Colo. Rev. Stat. § 6-1-1306
Traffic-light rationale — GreenRights and deadlines are clearly codified and operative since 2023.

Sub-modules (5)

Access rightGreen

Consumers have a statutory right to access personal data held by a controller.

Claims (1):

  • Colorado consumers have the right to access personal data processed about them by a controller.

Rectification and erasureGreen

Consumers may correct inaccuracies and request deletion of their personal data.

Claims (1):

  • Consumers have the right to correct inaccuracies in their personal data and to delete personal data held by a controller.

Restriction and objectionGreen

Consumers may object to/opt out of profiling used for decisions with legal or similarly significant effects, and may appeal a controller's denial of a rights request.

Claims (2):

  • Consumers may opt out of the processing of personal data for targeted advertising, sale, or profiling used for decisions that produce legal or similarly significant effects.
  • The CPA mandates that controllers provide a conspicuously available and easy-to-use appeal process when a consumer rights request is denied, and must inform the consumer of the ability to contact the Attorney General if the appeal is denied.

Data portabilityGreen

The CPA includes a right to obtain a portable copy of personal data in a readily usable format.

Claims (1):

  • The CPA provides consumers a right to obtain a portable copy of their personal data.

Deadlines and response windowsGreen

Controllers must respond to consumer requests within 45 days, extendable by an additional 45 days when reasonably necessary, with notice to the consumer within the initial period.

Claims (1):

  • A business must respond to a consumer rights request within 45 days of receipt and may extend that deadline by an additional 45 days when reasonably necessary, notifying the consumer within the initial 45-day period.
Category narrative 37 words

Colorado consumers hold access, correction, deletion, portability, and opt-out rights (targeted advertising, sale, and consequential-effect profiling), plus a mandatory appeal right against controller denials. Statutory response deadlines mirror the Virginia/Connecticut model (45 days, extendable by 45 days).

No periodic updates recorded in this cycle

Sources and claims (6)
  1. Confirmed OneTrust DataGuidance — Colorado consumers have the right to access personal data processed about them by a controller. observed
  2. Confirmed OneTrust DataGuidance — Consumers have the right to correct inaccuracies in their personal data and to delete personal data held by a controller. observed
  3. Confirmed OneTrust DataGuidance — Consumers may opt out of the processing of personal data for targeted advertising, sale, or profiling used for decisions that produce legal or similarly significant effects. observed
  4. Confirmed International Association of Privacy Professionals — The CPA mandates that controllers provide a conspicuously available and easy-to-use appeal process when a consumer rights request is denied, and must inform the consumer of the ability to contact the Attorney General if the appeal is denied. observed
  5. Confirmed OneTrust DataGuidance — The CPA provides consumers a right to obtain a portable copy of their personal data. observed
  6. Confirmed International Association of Privacy Professionals — A business must respond to a consumer rights request within 45 days of receipt and may extend that deadline by an additional 45 days when reasonably necessary, notifying the consumer within the initial 45-day period. observed

#

Core accountability, security, and breach duties are robust and in force, but the absence of DPO/ROPA-equivalent obligations creates a structural gap relative to GDPR-style regimes.

Primary frameworkColorado Privacy Act, Colo. Rev. Stat. §§ 6-1-1305, 6-1-1308; Colo. Rev. Stat. § 6-1-716 (breach notification); HB 24-1130
Traffic-light rationale — AmberCore accountability, security, and breach duties are robust and in force, but the absence of DPO/ROPA-equivalent obligations creates a structural gap relative to GDPR-style regimes.

Sub-modules (7)

Accountability & DPIAGreen

Controllers must conduct and document a data protection assessment before engaging in processing that presents a heightened risk of harm to consumers.

Claims (2):

  • Controllers may not process personal data in a manner presenting a heightened risk of harm to a consumer without conducting and documenting a data protection assessment of that processing activity.
  • 4 CCR 904-6 interim draft rules — A deployer may withhold information that would otherwise compromise cybersecurity, fraud-prevention, AML, counter-terrorist-financing, or economic-sanctions compliance programs.

DPO requirementsRed

No GDPR-style DPO appointment or independence mandate was identified in the CPA, CPA Rules, or secondary commentary.

Ropa requirementsAmber

No standalone, continuous records-of-processing-activities obligation analogous to GDPR Art. 30 was identified; the per-activity data protection assessment is the closest functional analog.

Joint controller arrangementsGreen

Processing by a processor on behalf of a controller must be governed by a contract specifying processing instructions, nature, type of data, and duration.

Claims (1):

  • Processing by a processor must be governed by a contract between the controller and processor establishing processing instructions, the nature and type of personal data, and the duration of processing.

Security measuresGreen

Controllers must take security precautions appropriate to the volume, scope, and nature of the personal data processed (duty of care).

Claims (1):

  • The CPA imposes a duty of care requiring controllers to take security precautions appropriate to the volume, scope, and nature of the personal data processed.

Breach notificationGreen

Colorado's breach law requires notice to affected residents without unreasonable delay and no later than 30 days after confirming a breach, plus AG notice within 30 days where 500+ residents are affected.

Claims (1):

  • Colorado law requires notice to affected residents in the most expedient way and without unreasonable delay, but not later than 30 days after confirming a breach, and requires notice to the Colorado Attorney General within 30 days where the breach is reasonably believed to affect 500 or more residents.

Retention and disposalGreen

HB 24-1130 requires controllers to adopt a written biometric-data retention schedule and to permanently destroy biometric identifiers within 45 days of the retention purpose being satisfied.

Claims (1):

  • HB 24-1130 requires controllers to adopt a written policy establishing a retention schedule and destruction guidelines for biometric identifiers, extending the destruction period to 45 days.
Category narrative 87 words

Controllers must conduct and document data protection assessments (DPAs) for heightened-risk processing, exercise a duty of care over security proportionate to the volume/scope/nature of data, and govern processor relationships by contract. Colorado's breach-notification law (independent of the CPA) requires consumer notice within 30 days and AG notice within 30 days for breaches affecting 500+ residents. HB 24-1130 layers biometric-specific retention/destruction duties (45-day destruction window). The CPA has no standalone DPO-appointment mandate or continuous ROPA obligation analogous to GDPR Arts. 30/37-39; the DPA functions as the closest analog.

Periodic update · new data 2026-10-25

The interim draft rules under 4 CCR 904-6 introduce a controller-duty carve-out with direct relevance to firms using automated decision-making technology for fraud and compliance screening. The provision permits a deployer to withhold information that would otherwise need to be disclosed under the ADMT framework's transparency requirements where disclosure would compromise a cybersecurity program, a fraud-prevention program, or an anti-money-laundering, counter-terrorist-financing, or economic-sanctions compliance program. This creates a defined boundary between a deployer's general transparency and documentation duties toward data subjects and the confidentiality needs of its separate financial-crime and security compliance functions.

The carve-out is framed within the same interim draft rules that establish the rebuttable-presumption standard for consequential-decision influence, meaning that a deployer relying on this withholding provision must do so within a broader rule structure that is itself still subject to revision ahead of the 26 October 2026 formal rulemaking hearing and the 1 January 2027 finalisation deadline. As drafted, the carve-out is not limited to any single sector, but its practical relevance is greatest for institutions — banks, payment companies, and other regulated financial entities — that operate ADMT-based fraud-detection or sanctions-screening systems where disclosure of underlying decision logic could itself create a circumvention risk.

Outlook

Whether this carve-out survives in its current form through to the finalised rule is an open question tied to the same 26 October 2026 hearing and 1 January 2027 deadline governing the rest of the interim draft. Firms relying on ADMT for financial-crime compliance screening in Colorado should treat the carve-out's current scope as provisional rather than settled until the rule is finalised.

1 earlier distinct update
Periodic update · new data 2026-09-05

Colorado added a new, category-specific controller duty this cycle through HB24-1130, effective 2025-07-01. Controllers of biometric identifiers and biometric data must adopt a written policy that includes a retention schedule and a data-security-incident-response protocol. This is a documentation-and-governance duty distinct from the Colorado Privacy Act's general controller obligations: it requires an affirmative, written artifact specific to biometric data, rather than a generalized practice or policy covering personal data as a whole.

The retention-schedule component requires controllers to specify a defined period for which biometric identifiers and biometric data will be retained, rather than relying on an open-ended or purpose-based retention standard. The incident-response-protocol component requires controllers to have a defined process for responding to a data-security incident involving biometric data specifically, which may need to be integrated with, but is not necessarily identical to, a controller's general data-security-incident-response plan.

Notably, this duty extends into the employment relationship: Colorado employers collecting biometric identifiers from employees, for example for workplace access-control systems using fingerprint or facial-recognition technology, are captured by this obligation even where the employer's broader Colorado Privacy Act exposure is otherwise limited to consumer-facing processing. This development should also be read alongside the broader tightening pattern evident across this cycle's Colorado privacy amendments: HB24-1130's controller-duty addition arrives in the same legislative and enforcement environment as SB25-276's sensitive-data expansion and the Attorney General's active post-cure-period enforcement posture.

Outlook

The near-term compliance question for controllers is whether existing biometric-data-handling practices, if any, already satisfy the written-policy, retention-schedule, and incident-response-protocol requirements, or whether a freestanding policy document must now be created. Employers using biometric access-control systems in Colorado are a population particularly likely to face this compliance question for the first time.

Sources and claims (6)
  1. Confirmed International Association of Privacy Professionals — Controllers may not process personal data in a manner presenting a heightened risk of harm to a consumer without conducting and documenting a data protection assessment of that processing activity. observed
  2. Confirmed International Association of Privacy Professionals — Processing by a processor must be governed by a contract between the controller and processor establishing processing instructions, the nature and type of personal data, and the duration of processing. observed
  3. Confirmed International Association of Privacy Professionals — The CPA imposes a duty of care requiring controllers to take security precautions appropriate to the volume, scope, and nature of the personal data processed. observed
  4. Confirmed International Association of Privacy Professionals — Colorado law requires notice to affected residents in the most expedient way and without unreasonable delay, but not later than 30 days after confirming a breach, and requires notice to the Colorado Attorney General within 30 days where the breach is reasonably believed to affect 500 or more residents. observed
  5. Confirmed OneTrust DataGuidance — HB 24-1130 requires controllers to adopt a written policy establishing a retention schedule and destruction guidelines for biometric identifiers, extending the destruction period to 45 days. observed
  6. Probable FDATA — 4 CCR 904-6 interim draft rules — A deployer may withhold information that would otherwise compromise cybersecurity, fraud-prevention, AML, counter-terrorist-financing, or economic-sanctions compliance programs. observed

#

No comprehensive cross-border transfer regime exists at the US-CO state level; this is a legitimate structural gap, not a research omission.

Traffic-light rationale — RedNo comprehensive cross-border transfer regime exists at the US-CO state level; this is a legitimate structural gap, not a research omission.

Sub-modules (6)

Transfer mechanismsRed

No CPA-specific transfer mechanism exists.

Claims (1):

  • Colorado has no state-level cross-border data-transfer mechanism distinct from federal adequacy/DPF frameworks; this module is not materially researchable at the state level.

Adequacy receivedRed

Not applicable; Colorado does not participate in a national/international adequacy framework.

Adequacy grantedRed

Not applicable.

SCCs and BCRsRed

No SCC/BCR concept exists under the CPA.

Transfer impact assessmentRed

No TIA requirement exists under the CPA; the general data protection assessment does not extend to cross-border transfer risk analysis.

Data localisationRed

No data localisation mandate exists under Colorado law.

Category narrative 47 words

The Colorado Privacy Act is a US state consumer-privacy statute and contains no international-transfer mechanism, adequacy-decision framework, SCC/BCR regime, transfer-impact-assessment requirement, or data-localisation mandate. Cross-border data flows are governed, if at all, by federal law (e.g., GLBA, HIPAA) or general contract law, not by the CPA itself.

Sources and claims (1)
  1. Uncertain Primary statutory record — Colorado has no state-level cross-border data-transfer mechanism distinct from federal adequacy/DPF frameworks; this module is not materially researchable at the state level.

#

Financial, health, and employment carve-outs are clear, but telecoms/ePrivacy, credit-scoring, and education overlays are not separately codified, leaving coverage partial.

Primary frameworkColorado Privacy Act (exemptions); Restrict Insurers' Use of External Consumer Data Act, SB 21-169
Traffic-light rationale — AmberFinancial, health, and employment carve-outs are clear, but telecoms/ePrivacy, credit-scoring, and education overlays are not separately codified, leaving coverage partial.

Sub-modules (7)

Financial sector overlayGreen

Entities regulated by the Gramm-Leach-Bliley Act are exempt at the entity level from CPA obligations.

Claims (1):

  • Entities regulated by the Gramm-Leach-Bliley Act are exempt at the entity level from Colorado Privacy Act obligations.

Health sector overlayGreen

Protected health information collected/processed by HIPAA-covered entities or business associates is exempt from the CPA.

Claims (1):

  • Protected health information collected, stored, and processed by HIPAA-covered entities or their business associates is exempt from the Colorado Privacy Act.

Telecoms and eprivacyAmber

No dedicated Colorado telecoms/ePrivacy overlay distinct from the CPA's general cookie/UOOM rules was identified.

Employment dataGreen

The CPA's definition of 'consumer' excludes individuals acting in a commercial or employment context, including job applicants and employment-context beneficiaries.

Claims (1):

  • The CPA's definition of 'consumer' excludes an individual acting in a commercial or employment context, as a job applicant, or as a beneficiary of someone acting in an employment context.

Credit and scoringAmber

No Colorado-specific credit-scoring overlay beyond federal FCRA exemption was identified.

educationAmber

No dedicated Colorado education-sector data-privacy overlay distinct from federal FERPA/COPPA was identified in this research pass.

insuranceAmber

Colorado's Restrict Insurers' Use of External Consumer Data Act (SB 21-169) restricts insurers' use of external consumer data and algorithms that could produce unfair discrimination.

Claims (1):

  • Colorado enacted the Restrict Insurers' Use of External Consumer Data Act (SB 21-169), restricting insurers' use of external consumer data and algorithms in ways that could result in unfair discrimination.
Category narrative 69 words

The CPA carves out entity-level exemptions for GLBA-regulated financial institutions and data-level exemptions for HIPAA-covered PHI, COPPA-regulated data, and employment-context data (the CPA's 'consumer' definition excludes employees, job applicants, and employment beneficiaries). Colorado separately regulates insurers' use of external consumer data and algorithms via the Restrict Insurers' Use of External Consumer Data Act (SB 21-169). No dedicated telecoms/ePrivacy, credit-scoring, or education-sector overlay distinct from the CPA/federal baseline was identified.

No periodic updates recorded in this cycle

Sources and claims (4)
  1. Confirmed International Association of Privacy Professionals — Entities regulated by the Gramm-Leach-Bliley Act are exempt at the entity level from Colorado Privacy Act obligations. observed
  2. Confirmed OneTrust DataGuidance — Protected health information collected, stored, and processed by HIPAA-covered entities or their business associates is exempt from the Colorado Privacy Act. observed
  3. Confirmed OneTrust DataGuidance — The CPA's definition of 'consumer' excludes an individual acting in a commercial or employment context, as a job applicant, or as a beneficiary of someone acting in an employment context. observed
  4. Uncertain Federal Trade Commission — Colorado enacted the Restrict Insurers' Use of External Consumer Data Act (SB 21-169), restricting insurers' use of external consumer data and algorithms in ways that could result in unfair discrimination. observed

#

UOOM and dark-pattern rules are operative and well documented; gaps exist only in emerging areas like clean rooms.

Primary frameworkColorado Privacy Act Rules, 4 CCR 904-3, Part 5
Traffic-light rationale — GreenUOOM and dark-pattern rules are operative and well documented; gaps exist only in emerging areas like clean rooms.

Sub-modules (6)

Cookies and trackersAmber

The CPA governs tracking primarily through its sale/targeted-advertising opt-out and UOOM regime rather than a dedicated cookie-consent-banner law.

Dark patternsGreen

CPA Rules provide that any agreement obtained through dark patterns is not valid consent.

Claims (1):

  • Under CPA Rules, any agreement obtained through dark patterns is not valid consent.

Opt out signalsGreen

From July 1, 2024, controllers must honor a user-selected universal opt-out mechanism meeting AG technical specifications; Colorado currently recognizes GPC as the only valid UOOM, and the AG publishes a public UOOM list (initial list by April 1, 2024).

Claims (4):

  • From July 1, 2024, data controllers must allow consumers to exercise opt-out rights for targeted advertising or sale of personal data through a user-selected universal opt-out mechanism meeting AG technical specifications.
  • Colorado currently considers the Global Privacy Control to be the only recognized valid universal opt-out mechanism under the CPA.
  • The Colorado Department of Law maintains and publishes a public list of recognized universal opt-out mechanisms, with the initial list published no later than April 1, 2024.
  • Colorado, Connecticut and California Attorneys General — Joint investigative sweep sending letters to businesses not processing GPC opt-out-of-sale signals, announced 2025-09-09.

Clean rooms and dcrRed

No clean-room or data-collaboration-room-specific provisions were identified under the CPA.

Cross context advertisingAmber

The CPA's 'sale' definition (exchange of data for monetary or other valuable consideration) and targeted-advertising opt-out function as Colorado's analog to CPRA-style cross-context advertising restrictions.

Direct marketingAmber

No CPA provision specifically dedicated to direct-marketing suppression lists was identified beyond the general targeted-advertising opt-out.

Category narrative 57 words

Colorado requires recognition of a universal opt-out mechanism (UOOM) for targeted-advertising and sale opt-outs since July 1, 2024, and currently recognizes the Global Privacy Control (GPC) as the sole valid UOOM signal. The AG maintains and publishes a public list of recognized UOOMs. CPA Rules invalidate consent obtained through dark patterns. No dedicated clean-room/data-collaboration-room regime was identified.

Periodic update · new data 2026-10-11

Colorado's Attorney General joined counterparts in Connecticut and California in a joint investigative sweep, announced 9 September 2025, sending letters to businesses identified as not processing Global Privacy Control opt-out-of-sale signals. Building on that sweep, an AdTech company is reported to have paid a penalty of approximately two hundred fifty thousand dollars for ignoring Global Privacy Control opt-out signals from more than five hundred thousand Colorado users; this is described as the first enforcement action brought after the relevant Colorado Privacy Act cure period lapsed. The primary Attorney General source confirming this reported action has not been independently retrieved, and the named target of the action is not established in the record.

Outlook

The joint multistate sweep and the reported AdTech settlement together indicate an escalating enforcement posture around Global Privacy Control compliance. Confirmation of the reported settlement's target and terms against a primary Attorney General source remains outstanding.

1 earlier distinct update
Periodic update · new data 2026-09-05

Colorado's adtech enforcement posture became concrete this cycle with the disclosure of the Attorney General's first reported Colorado Privacy Act enforcement action following the cure period's sunset. The Attorney General publicly disclosed a 250,000 dollar penalty against an adtech company in April 2025, arising from compliance sweeps focused on universal opt-out mechanisms and Global Privacy Control compliance. This is reported to be the first disclosed enforcement action taken without the 60-day cure opportunity that characterized the law's earlier enforcement years, and it specifically targets a compliance failure, non-recognition or non-honoring of opt-out signals, that sits at the center of the Colorado Privacy Act's commercial-privacy and targeted-advertising provisions.

The action signals that Colorado's Attorney General is treating universal opt-out and Global Privacy Control compliance as an active enforcement priority for adtech and commercial-privacy practices, rather than a technical requirement enforced only reactively. For adtech companies and any controller relying on third-party advertising technology, the practical implication is that opt-out-signal recognition, and the ability to demonstrate that recognition operationally, is now understood to carry direct financial-penalty risk. Commercial-privacy stakeholders should also note that this action arrives amid a broader tightening of Colorado's sensitive-data and enforcement architecture this cycle, suggesting that adtech-focused enforcement is one strand of a wider regulatory tightening rather than an isolated sectoral action.

Outlook

Given that this is reported as the first disclosed post-cure-period action, further adtech-sector enforcement activity focused on opt-out-signal compliance is a plausible near-term development, though no specific additional action has been identified this cycle. Sourcing note: the 250,000 dollar figure relies on secondary reporting rather than an independently retrieved primary enforcement order this cycle, a gap worth tracking as the underlying enforcement-posture shift is otherwise treated as reliably established.

Sources and claims (5)
  1. Confirmed Colorado Department of Law — Under CPA Rules, any agreement obtained through dark patterns is not valid consent. observed
  2. Confirmed OneTrust DataGuidance — From July 1, 2024, data controllers must allow consumers to exercise opt-out rights for targeted advertising or sale of personal data through a user-selected universal opt-out mechanism meeting AG technical specifications. observed
  3. Probable International Association of Privacy Professionals — Colorado currently considers the Global Privacy Control to be the only recognized valid universal opt-out mechanism under the CPA. observed
  4. Confirmed OneTrust DataGuidance — The Colorado Department of Law maintains and publishes a public list of recognized universal opt-out mechanisms, with the initial list published no later than April 1, 2024. observed
  5. Probable Wikipedia — Colorado, Connecticut and California Attorneys General — Joint investigative sweep sending letters to businesses not processing GPC opt-out-of-sale signals, announced 2025-09-09. observed

#

Biometric and profiling rules are settled, but the AI Act framework remains in active flux (major 2026 amendments, delayed effective date, pending litigation), creating material regulatory uncertainty.

Primary frameworkColorado Privacy Act Rules, 4 CCR 904-3; Colorado Artificial Intelligence Act, SB 24-205 (as amended by SB 189, 2026)
Traffic-light rationale — AmberBiometric and profiling rules are settled, but the AI Act framework remains in active flux (major 2026 amendments, delayed effective date, pending litigation), creating material regulatory uncertainty.

Sub-modules (6)

Profiling restrictionsGreen

Consumers may opt out of profiling used for decisions producing legal or similarly significant effects.

Claims (2):

  • Consumers may opt out of profiling in furtherance of decisions that produce legal or similarly significant effects concerning the consumer.
  • xAI v. Colorado — A federal magistrate judge blocked state enforcement of the original SB 24-205 framework on April 27, 2026, after xAI sued on constitutional grounds with DOJ intervention supporting xAI, prior to the law's statutory repeal.

Automated decision making transparencyAmber

Under SB 189, deployers must provide consumers explicit disclosures on intended/harmful uses of ADMT, training-data categories, and deployer oversight instructions when the AI Act takes effect January 1, 2027.

Claims (10):

  • Under Senate Bill 189, deployers of covered AI systems must provide consumers with explicit disclosures regarding intended and harmful uses of automated decision-making technology, training-data categories, and deployer oversight instructions.
  • Colorado Department of Law ADMT/Chatbot Safety draft rules — October revision narrows the ADMT-use disclosure requirement to centre on the specific decision and the technology's role in it.
  • FDATA's comment letter disputes the fraud-prevention/identity-verification exclusion boundary for payment risk scores.
  • FDATA's comment letter argues the ADMT draft rules leave the fraud-prevention/identity-verification exclusion boundary unclear, specifically for payment risk scores.
  • Colorado SB26-189 (ADMT Act) — Notice, 30-day adverse-outcome disclosure, correction, and human-review duties on developers/deployers of automated decision-making technology used in consequential decisions, enforced by the AG as a deceptive trade practice.
  • Colorado's October ADMT draft narrows the disclosure requirement to the specific decision and the technology's role in it, following over sixty public comments.
  • Colorado Dept. of Law (4 CCR 904-6 interim draft rules) — A rebuttable presumption that certain ADMT outputs 'materially influence' a consequential decision, revised multiparty-arrangement responsibility, and removal of the Aug. 11 draft's requirement to stay an adverse outcome pending correction/human review; formal rulemaking hearing Oct. 26, 2026, with written comments closing that night, and finalisation required by Jan. 1, 2027.
  • 4 CCR 904-6 Rule 7 requires a Covered-ADMT deployer's adverse-outcome disclosure to provide a unified method for a consumer to exercise rights and request additional information, and to accurately explain the principal reason(s) a Covered ADMT materially influenced a consequential decision resulting in an adverse outcome.
  • 4 CCR 904-6 — The 6 Oct 2026 revised interim draft rules changed the threshold test for 'materially influence'/de minimis from the two competing standards floated in the 11 Aug 2026 notice of hearing, moving closer to (with differences, including a rebuttable presumption) the CCPA ADMT regulation standard; the definition remained unsettled as of this run, pending the 26 Oct 2026 hearing.
  • SB26-189, signed 2026-05-14, replaces the Colorado AI Act with an ADMT law applicable from 2027-01-01.

AI risk assessmentsAmber

SB 189 (2026) replaces the AI Act's original duty-of-care/risk-management-program/impact-assessment obligations with a disclosure-based framework and delays the principal effective date to January 1, 2027.

Claims (6):

  • Senate Bill 189 (2026) replaces the Colorado AI Act's original risk-based framework with disclosure and transparency requirements, removing the duty-of-care, risk-management-program, and impact-assessment obligations that had applied to deployers.
  • SB 189 moves the Colorado AI Act's principal effective date to January 1, 2027, superseding the prior June 30, 2026 date.
  • Colorado Attorney General — Will not enforce SB24-205 (predecessor AI Act) or its replacement SB26-189 until the associated rulemaking process concludes, following a federal court injunction in xAI v. Weiser.
  • SB24-205 (Colorado AI Act, 2024) — Repealed and replaced by SB26-189 on 2026-05-14 before ever taking effect; duty-of-care, impact-assessment and risk-management-program obligations never came into force.
  • SB 26-189 (ADMT Act) — SB 26-189 (2026), which repealed and replaced the original Colorado AI Act (SB 24-205, signed 17 May 2024), dropped the impact-assessment, risk-management-program and duty-of-reasonable-care obligations that made SB 24-205 controversial; enforcement is solely by the Colorado Attorney General under the Colorado Consumer Protection Act (deceptive trade practice), with a 60-day notice-and-cure period generally required before 1 Jan 2030, and no private right of action.
  • Colorado ADMT Act (SB 26-189) — SB 26-189 (signed May 14, 2026) repeals and reenacts SB 24-205's provisions as the ADMT Act; operative developer-documentation duties and the Attorney General's rulemaking deadline take effect Jan. 1, 2027.

Biometric regimeGreen

CPA Rules define 'Biometric Identifiers' and 'Biometric Data'; HB 24-1130 mandates disclosure and consent before collection, retention scheduling, and 45-day destruction timelines.

Claims (1):

  • HB 24-1130 requires controllers to disclose and obtain consent before collecting biometric data and defines 'Biometric Identifiers' as data generated by technological processing of an individual's biological, physical, or behavioral characteristics.

Genetic dataAmber

HB 24-1130 expanded CPA sensitive-data protections to cover neural data alongside biometric identifiers; no separate freestanding genetic-data statute was identified.

Claims (1):

  • HB 24-1130 expanded the Colorado Privacy Act's scope to protect neural data in addition to biometric identifiers.

State surveillance carveoutsRed

No Colorado-specific state-surveillance carve-out or national-security exemption analysis distinct from general law-enforcement exceptions was identified in this research pass.

Category narrative 39 words

Colorado repealed and replaced its 2024 AI Act (SB24-205) with SB26-189, the Automated Decision-Making Technology Act, signed May 14, 2026, effective January 1, 2027. SB26-189 shifts the framework from broad algorithmic-discrimination risk governance to transparency, notice, and consumer-recourse duties.

Periodic update · new data 2026-11-08

Colorado has enacted SB26-189, an Automated Decision-Making Technology law that requires developers and deployers of automated decision-making technology materially influencing a consequential decision to provide a thirty-day explanation of any adverse outcome. Under the statute, affected individuals are understood to receive correction rights and human review, with covered organizations retaining records for three years. The Colorado Attorney General enforces the law exclusively, and is understood to be bound to a mandatory sixty-day cure period running through 2030 absent a knowing or repeated violation, which gives covered organizations a defined grace window during the law's early enforcement life.

SB26-189 was signed on 14 May 2026 and takes effect from 1 January 2027. It stands in place of the Colorado AI Act (SB24-205), which had stalled before reaching its own effective date; SB26-189 is the vehicle that now carries forward the state's intent to regulate consequential algorithmic decision-making, with a materially different set of obligations around explanation, correction, human review, and recordkeeping than its predecessor would have imposed. This marks a direct substitution of regulatory vehicle rather than a withdrawal of regulatory intent: Colorado continues to move toward binding obligations on automated decision-making, now through a different statutory instrument and a different effective date than had previously been anticipated.

Outlook

Between now and 1 January 2027, developers and deployers of automated decision-making technology operating in Colorado have a defined runway to build the processes SB26-189 requires: a mechanism for issuing thirty-day adverse-outcome explanations, a correction and human-review pathway, and three-year recordkeeping. Once the law takes effect, the Attorney General's exclusive enforcement authority engages, though the mandatory sixty-day cure period running through 2030 means that early non-compliance identified by the Attorney General is expected to be met with an opportunity to cure rather than immediate penalty, except where a violation is knowing or repeated.

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

Colorado's rulemaking on automated decision-making technology and chatbot safety has reached a formal hearing stage. The Colorado Department of Law is understood to have held the public rulemaking hearing on its proposed rules (4 CCR 904-6) on 26 October 2026, at 1300 Broadway, Room 1D, Denver, with written comments accepted until 11:59 PM MST that day. As of 25 October 2026, no final rules had been adopted, though the Attorney General is under a statutory obligation to adopt implementing rules by 1 January 2027.

The substance of the draft has moved since an earlier August version. After more than sixty public comments, the October revision narrows the disclosure requirement for automated decisions so that it focuses on the specific decision at hand and the automated tool's role in reaching it, rather than requiring a more generalised disclosure. This is a meaningful tightening of scope in how the obligation is framed, even though the underlying requirement to disclose automated-decision use is not new.

The principal point of continuing contest is the boundary of the statutory exclusion for fraud prevention and identity verification. FDATA's comment letter, dated 26 October 2026, argues that the draft rules remain unclear about where that exclusion ends, and asks that payment risk scores be excluded from coverage entirely and that principal-factor disclosure obligations be removed for both developers and deployers of the technology. This dispute sits squarely at the intersection of consumer-protection disclosure rules and the operational use of automated scoring tools in financial and payment-adjacent services, and it is the live question the Department will need to resolve before finalising the rule.

Outlook

The statutory deadline for final rules is 1 January 2027. Whether the Attorney General preserves the narrower October disclosure framing and how the fraud-prevention and identity-verification exclusion is ultimately drawn, particularly as it bears on payment risk scoring, remain open questions that the final rule text will settle.

Periodic update · new data 2026-10-25

Colorado's ADMT framework underwent a structural replacement this period. SB 26-189, signed 14 May 2026, repeals and reenacts the provisions of SB 24-205 as the ADMT Act. SB 24-205 itself never took effect: a federal magistrate judge blocked state enforcement of that original framework on 27 April 2026, following a constitutional challenge brought by xAI in which the Department of Justice intervened in support of xAI's position. The reenacted ADMT Act replaces SB 24-205's risk-tier framing with a framework built around the defined concept of automated decision-making technology. The operative developer-documentation duties under the reenacted Act, together with the Attorney General's deadline for finalising implementing rules, take effect 1 January 2027.

The implementing rules themselves are at an active, pre-final stage. The Colorado Department of Law's interim draft rules, filed under 4 CCR 904-6, establish a rebuttable presumption that certain ADMT outputs "materially influence" a consequential decision — placing the burden on a deployer to rebut that presumption once the relevant output criteria are met. The interim draft also revises how responsibility for compliance is allocated when multiple parties participate in an ADMT arrangement, and it removes a provision that appeared in an earlier, 11 August draft requiring a deployer to stay an adverse outcome pending correction or human review. A formal rulemaking hearing on these interim draft rules was scheduled for 26 October 2026, with the written comment period closing that same night. The Attorney General must finalise the rule by 1 January 2027, aligning the rulemaking deadline precisely with the ADMT Act's own effective date.

Outlook

The period between the 26 October 2026 hearing and the 1 January 2027 finalisation deadline is the live window in which the interim draft's rebuttable-presumption standard, its multiparty-responsibility allocation, and the removed stay-pending-review requirement remain open to further revision. Whether the final rule preserves, narrows, or reintroduces elements of the 11 August draft will determine the practical compliance burden facing ADMT deployers in Colorado from 1 January 2027 onward.

Periodic update · new data 2026-10-18

Colorado's algorithmic-governance regime is converging toward finalization. The revised interim draft of 4 CCR 904-6, released 6 October 2026, changes the threshold test for when automated decision-making technology 'materially influences' a consequential decision, moving toward, with differences including a rebuttable presumption, the standard used in California's CCPA ADMT regulation; this definition remains unsettled pending the 26 October 2026 hearing. Rule 7 of the revised draft requires a Covered-ADMT deployer's adverse-outcome disclosure to provide a unified method for a consumer to exercise rights and request additional information, and to accurately explain the principal reason or reasons a Covered ADMT materially influenced a consequential decision resulting in an adverse outcome.

This rulemaking sits beneath SB 26-189, the ADMT Act, which repealed and replaced the original Colorado AI Act, SB 24-205, signed 17 May 2024. The replacement dropped the impact-assessment, risk-management-program and duty-of-reasonable-care obligations that had made SB 24-205 controversial, narrowing the statute's substantive demands even as the disclosure and threshold mechanics are worked out at the rule level. Both the ADMT Act and the companion Chatbot Safety Act, HB 26-1263, take effect 1 January 2027, and the 4 CCR 904-6 rules are the vehicle through which the Department of Law intends to operationalize those statutes' consequential-decision and disclosure requirements.

Outlook

The final materially-influence and de minimis threshold, to be set after the 26 October 2026 hearing, is the single most consequential open variable in this module: it will determine how many automated-decision systems fall within scope of the adverse-outcome disclosure duty under Rule 7. Pending litigation involving xAI in the U.S. District Court for the District of Colorado may also bear on whether the 1 January 2027 effective date holds, though the nature of that litigation's effect has not been established this cycle.

Periodic update · new data 2026-10-11

Colorado's algorithmic-governance framework underwent a substantive repeal-and-reenactment in 2026. The Colorado AI Act, SB24-205, enacted in 2024, was repealed and replaced by Senate Bill 26-189 on 14 May 2026, before SB24-205's duty-of-care, impact-assessment and risk-management-program obligations ever came into force. In place of that framework, SB26-189 reenacts a narrower automated-decision-making-technology disclosure-and-governance regime, effective 1 January 2027. The Colorado Attorney General filed proposed rules implementing the ADMT and chatbot-safety provisions on 11 August 2026, with the public comment period running to 26 October 2026. Whether the Attorney General has undertaken rulemaking activity beyond the stated comment windows has not been established as of this record.

Outlook

The comment period closing 26 October 2026 is the next dated step toward finalisation of the ADMT and chatbot-safety rules ahead of the 1 January 2027 effective date. Because SB24-205's obligations never took effect, operators in Colorado face no transition from an operative risk-management-program regime; the ADMT disclosure-and-governance framework under SB26-189 will instead be the first algorithmic-governance regime to actually apply in the state.

Periodic update · new data 2026-09-28

Colorado enacted SB26-189, which repeals and replaces the original Colorado AI Act (SB24-205) with a new Automated Decision-Making Technology (ADMT) framework, effective January 1, 2027. The new law requires deployers of covered ADMT to provide pre-use disclosures to affected consumers, to explain adverse outcomes within 30 days of a request, and to offer a path for meaningful human review of automated decisions. This is a structural realignment of Colorado's algorithmic-governance approach: the original AI Act had centered on a duty-of-care standard implemented through risk-management programs and pre-deployment impact assessments, whereas SB26-189 shifts the regulatory center of gravity to individual-facing transparency, disclosure and a consumer right to contest or seek review of an automated outcome.

This is an enacted-but-not-yet-effective instrument: SB26-189 has passed but its substantive obligations do not bind deployers until January 1, 2027, giving covered entities a defined runway to build the required disclosure, adverse-outcome-explanation and human-review infrastructure. The repeal-and-replace nature of this legislation means that entities that had begun building compliance programs around the original AI Act's risk-management and impact-assessment model will need to reorient toward the new transparency-and-disclosure model rather than simply continuing prior compliance work.

The practical effect for ADMT deployers operating in or serving Colorado consumers is a shift in compliance architecture: rather than documenting internal risk assessments primarily for regulator-facing accountability, deployers will need consumer-facing disclosure content, a working adverse-outcome explanation process capable of responding within a 30-day window, and an operational human-review pathway that a consumer can actually invoke.

Outlook

The SB26-189 framework takes effect January 1, 2027. Whether the Colorado Attorney General issues implementing guidance or rules ahead of that date, and whether any enforcement action or interpretive opinion emerges regarding the scope of covered ADMT prior to the effective date, are the key items to watch in the run-up to implementation.

Periodic update · new data 2026-09-05

Colorado undertook a significant restructuring of its algorithmic-governance framework this cycle. SB26-189, signed 2026-05-14, repeals and reenacts Colorado's 2024 high-risk-AI provisions as an Automated Decision-Making Technology law. The new framework imposes ADMT-specific duties for consequential decisions, including a developer-documentation obligation, with these duties taking effect 2027-01-01. This is a repeal-and-reenactment rather than an amendment: the prior 2024 high-risk-AI framework is replaced wholesale by the new ADMT structure rather than modified in place, which is itself a significant governance signal, indicating that the legislature judged the original 2024 framework to require structural replacement rather than incremental correction.

The distinction between enacted and in-force status is important here: SB26-189 is enacted law as of its 2026-05-14 signature, but its consequential-decision and developer-documentation duties are not yet in force, with an effective date of 2027-01-01. This gives covered developers and deployers of automated decision-making technology a defined compliance runway before the substantive duties become enforceable, and it also means that any implementing guidance issued in the interim would be addressing an enacted-but-not-yet-effective framework rather than a currently binding one.

Outlook

The 2027-01-01 effective date is the single most consequential date on Colorado's algorithmic-governance horizon. Developers and deployers of automated decision-making technology operating in Colorado should treat the intervening period as the primary window for compliance-program development. Whether implementing rules or guidance will further clarify the scope of consequential decision or the specific content of the developer-documentation obligation ahead of that date remains an open question this cycle.

Sources and claims (21)
  1. Confirmed OneTrust DataGuidance — Consumers may opt out of profiling in furtherance of decisions that produce legal or similarly significant effects concerning the consumer. observed
  2. Confirmed International Association of Privacy Professionals — Under Senate Bill 189, deployers of covered AI systems must provide consumers with explicit disclosures regarding intended and harmful uses of automated decision-making technology, training-data categories, and deployer oversight instructions. observed
  3. Confirmed International Association of Privacy Professionals — Senate Bill 189 (2026) replaces the Colorado AI Act's original risk-based framework with disclosure and transparency requirements, removing the duty-of-care, risk-management-program, and impact-assessment obligations that had applied to deployers. observed
  4. Confirmed International Association of Privacy Professionals — SB 189 moves the Colorado AI Act's principal effective date to January 1, 2027, superseding the prior June 30, 2026 date. observed
  5. Confirmed OneTrust DataGuidance — HB 24-1130 requires controllers to disclose and obtain consent before collecting biometric data and defines 'Biometric Identifiers' as data generated by technological processing of an individual's biological, physical, or behavioral characteristics. observed
  6. Probable OneTrust DataGuidance — HB 24-1130 expanded the Colorado Privacy Act's scope to protect neural data in addition to biometric identifiers. observed
  7. Probable Hunton Andrews Kurth — Colorado Department of Law ADMT/Chatbot Safety draft rules — October revision narrows the ADMT-use disclosure requirement to centre on the specific decision and the technology's role in it. observed
  8. Probable FDATA — FDATA's comment letter disputes the fraud-prevention/identity-verification exclusion boundary for payment risk scores. observed
  9. Probable artificialintelligenceregulations.com — SB26-189 (2026) — Repeals SB24-205's substantive provisions and reenacts an ADMT disclosure-and-governance framework, effective 2027-01-01; AG filed proposed ADMT/chatbot rules 2026-08-11, comments to 2026-10-26. observed
  10. Probable McDermott Will & Emery — xAI v. Colorado — A federal magistrate judge blocked state enforcement of the original SB 24-205 framework on April 27, 2026, after xAI sued on constitutional grounds with DOJ intervention supporting xAI, prior to the law's statutory repeal. observed
  11. Probable FDATA — FDATA's comment letter argues the ADMT draft rules leave the fraud-prevention/identity-verification exclusion boundary unclear, specifically for payment risk scores. observed
  12. Confirmed McDermott Will & Emery — Colorado SB26-189 (ADMT Act) — Notice, 30-day adverse-outcome disclosure, correction, and human-review duties on developers/deployers of automated decision-making technology used in consequential decisions, enforced by the AG as a deceptive trade practice. observed
  13. Probable Hunton Andrews Kurth — Colorado's October ADMT draft narrows the disclosure requirement to the specific decision and the technology's role in it, following over sixty public comments. observed
  14. Confirmed Buchalter — Colorado Attorney General — Will not enforce SB24-205 (predecessor AI Act) or its replacement SB26-189 until the associated rulemaking process concludes, following a federal court injunction in xAI v. Weiser. observed
  15. Probable Legal 500 — Colorado Dept. of Law (4 CCR 904-6 interim draft rules) — A rebuttable presumption that certain ADMT outputs 'materially influence' a consequential decision, revised multiparty-arrangement responsibility, and removal of the Aug. 11 draft's requirement to stay an adverse outcome pending correction/human review; formal rulemaking hearing Oct. 26, 2026, with written comments closing that night, and finalisation required by Jan. 1, 2027. observed
  16. Probable Primary statutory record — SB24-205 (Colorado AI Act, 2024) — Repealed and replaced by SB26-189 on 2026-05-14 before ever taking effect; duty-of-care, impact-assessment and risk-management-program obligations never came into force.
  17. Probable Colorado Department of Law — 4 CCR 904-6 Rule 7 requires a Covered-ADMT deployer's adverse-outcome disclosure to provide a unified method for a consumer to exercise rights and request additional information, and to accurately explain the principal reason(s) a Covered ADMT materially influenced a consequential decision resulting in an adverse outcome. observed
  18. Probable Ballard Spahr LLP — 4 CCR 904-6 — The 6 Oct 2026 revised interim draft rules changed the threshold test for 'materially influence'/de minimis from the two competing standards floated in the 11 Aug 2026 notice of hearing, moving closer to (with differences, including a rebuttable presumption) the CCPA ADMT regulation standard; the definition remained unsettled as of this run, pending the 26 Oct 2026 hearing. observed
  19. Probable Secure Privacy — SB 26-189 (ADMT Act) — SB 26-189 (2026), which repealed and replaced the original Colorado AI Act (SB 24-205, signed 17 May 2024), dropped the impact-assessment, risk-management-program and duty-of-reasonable-care obligations that made SB 24-205 controversial; enforcement is solely by the Colorado Attorney General under the Colorado Consumer Protection Act (deceptive trade practice), with a 60-day notice-and-cure period generally required before 1 Jan 2030, and no private right of action. observed
  20. Probable Security Boulevard — Colorado ADMT Act (SB 26-189) — SB 26-189 (signed May 14, 2026) repeals and reenacts SB 24-205's provisions as the ADMT Act; operative developer-documentation duties and the Attorney General's rulemaking deadline take effect Jan. 1, 2027. observed
  21. Probable Security Boulevard — SB26-189, signed 2026-05-14, replaces the Colorado AI Act with an ADMT law applicable from 2027-01-01. observed

#

Minors' protections are now in force with clear obligations; only the pending age-attestation bill and dependent-adult gap temper the rating.

Primary frameworkColorado Privacy Act as amended by SB 24-041
Traffic-light rationale — GreenMinors' protections are now in force with clear obligations; only the pending age-attestation bill and dependent-adult gap temper the rating.

Sub-modules (5)

Age verificationAmber

Senate Bill 26-051 would establish an age-attestation framework for computing devices with non-compliance penalties, but remained a pending bill as of this research pass.

Claims (1):

  • Senate Bill 26-051 aims to establish a framework for age attestation on computing devices in Colorado, with penalties for non-compliance, but remains a pending bill as of this research pass.

Minor profiling bansGreen

SB 24-041 prohibits processing a minor's personal data for targeted advertising absent consent.

Claims (4):

  • SB 24-041 prohibits processing a minor's personal data for purposes of targeted advertising without consent.
  • SB24-041 amends the CPA to add enhanced protections when a minor's data is processed and there is a heightened risk of harm to minors, effective October 1, 2025.
  • Colorado SB24-041 — Adds enhanced protections when a minor's data is processed and there is heightened risk of harm to minors, effective October 1, 2025.
  • Colorado SB24-041 notice-and-cure mechanism — The notice-and-60-day-cure mechanism attached to SB24-041's minor-data requirements sunsets on December 31, 2026.

Education settingsAmber

No education-setting-specific minors' data provisions distinct from SB 24-041's general minors' framework were identified.

Dependent adultsRed

No dependent-adult (elderly/incapacitated) data-protection provisions were identified under the CPA.

Category narrative 80 words

SB 24-041, effective October 1, 2025, amended the CPA to prohibit processing minors' data for targeted advertising without consent, require reasonable care to avoid risks to minors, and mandate data protection impact assessments for services posing heightened risk to minors, with a 60-day cure period preserved through the end of 2026 specifically for minors' provisions. Senate Bill 26-051, proposing an age-attestation framework for computing devices, remains a pending bill as of this research pass. No dedicated dependent-adult protections were identified.

Periodic update · new data 2026-11-08

Colorado's protections for minors rest on two layers that have developed at different speeds. SB24-041 has required, since 1 October 2025, parental or guardian consent before a controller processes a minor under thirteen's personal data in a manner that presents a heightened risk of harm. Notably, this obligation reaches any controller doing business in or targeting Colorado regardless of the controller's revenue, meaning the duty is not confined to large-scale processors and instead applies on the basis of conduct and targeting rather than size.

A second, newer layer remains in motion rather than settled. Rule amendments addressing minors' use of addictive design features were adopted by the Department of Law on 8 October 2025, but the amendments await Attorney General approval and publication in the Colorado Register, with effect expected thirty days after publication. Whether that publication step has since occurred has not been independently confirmed against the Register, so the precise date on which these addictive-design protections will bind remains open. The direction of travel, however, is clear: Colorado is building out minors'-specific obligations in a layered fashion, first through the heightened-risk-of-harm consent requirement already in force, and now through a second rule-based layer targeting specific design practices understood to affect children's engagement with digital products.

Outlook

The heightened-risk-of-harm consent duty under SB24-041 is settled law and will continue to apply without change. The addictive-design rule amendments are the element to watch: once Attorney General approval and Register publication occur, a thirty-day countdown to effect will begin, and organizations whose products or services reach Colorado minors should expect that this second layer of obligation will crystallize on a defined but not yet fixed date.

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

Colorado joined a nationwide multistate settlement with Meta Platforms, announced 26 August 2026, under which Meta is required to pay more than seventeen billion dollars and to implement child-safety reforms on Instagram and Facebook. Separately, the Colorado Privacy Act retains a mandatory cure-notice opportunity specifically for minors'-protection violations, running until 31 December 2026, even though the Act's general cure period for other violation types sunset on 1 January 2025.

Outlook

The minors'-protection cure period's end on 31 December 2026 marks the point at which the Colorado Attorney General gains the ability to pursue enforcement for violations affecting minors without first offering businesses an opportunity to cure, aligning the children's-data enforcement posture with the general CPA enforcement standard already in effect for other provisions.

Periodic update · new data 2026-09-28

SB24-041 amends the Colorado Privacy Act to add enhanced protections applicable when a minor's data is processed and there is a heightened risk of harm to minors, effective October 1, 2025. This heightened-risk-of-harm standard establishes a distinct, more protective processing tier for minors' data beyond the CPA's general consumer-data framework, though the specific substantive obligations that attach once the heightened-risk threshold is met sit within the broader CPA amendment rather than being enumerated as a standalone claim this cycle.

A notice-and-cure period applicable to enforcement of the minors' and biometric-data provisions is scheduled to sunset December 31, 2026. During the current cure period, the Colorado Attorney General's Office must generally afford a 60-day opportunity to cure before pursuing enforcement for violations of these specific provisions; after the sunset date, that mandatory cure opportunity will no longer apply, materially increasing the immediate enforcement exposure for non-compliant processing of minors' data.

This represents a tightening trajectory: the combination of the heightened-risk-of-harm standard taking effect in October 2025 and the cure-period protection lapsing at the end of 2026 means that the practical compliance runway for minors'-data processors to identify and remediate non-compliant practices without facing direct enforcement is time-limited and closing.

Outlook

Controllers processing minors' data in a manner that could trigger the heightened-risk-of-harm standard should treat the December 31, 2026 cure-period sunset as a hard compliance deadline: remediation identified after that date will not benefit from the current 60-day cure opportunity, and enforcement exposure increases correspondingly.

Periodic update · new data 2026-09-05

Colorado expanded its protections for minors under the Colorado Privacy Act this cycle through SB24-041, effective 2025-10-01. The statute requires controllers to use reasonable care to avoid heightened risks of harm to minors, and to conduct data protection assessments for online services, products, or features used by minors. This is a population-based trigger for the data-protection-assessment requirement, distinct from the Act's more familiar processing-based triggers, such as processing of sensitive data or use of personal data for targeted advertising, profiling, or sale.

The reasonable-care-to-avoid-heightened-risk-of-harm standard introduces a duty-of-care concept into Colorado's privacy framework specifically in relation to minors, which is analytically distinct from the Act's general lawful-processing and controller-obligation architecture: it is a harm-avoidance standard rather than a consent-or-lawful-basis standard, meaning a controller could in principle satisfy the Act's general consent and lawful-processing requirements while still falling short of the heightened-care standard specifically owed to minors.

Outlook

Whether the Colorado Department of Law finalized proposed Colorado Privacy Act rule amendments addressing minors' protections ahead of an anticipated 2026-07-01 effective date, without material change from the proposed text, remains unconfirmed this cycle and is a gap worth tracking. Controllers operating online services, products, or features reasonably likely to be accessed by minors should treat the data-protection-assessment requirement introduced by SB24-041 as a standing, population-based compliance obligation distinct from their existing sensitive-data and targeted-advertising assessment triggers.

Sources and claims (9)
  1. Speculative OneTrust DataGuidance — Senate Bill 26-051 aims to establish a framework for age attestation on computing devices in Colorado, with penalties for non-compliance, but remains a pending bill as of this research pass. observed
  2. Confirmed OneTrust DataGuidance — SB 24-041 amends the Colorado Privacy Act to include heightened protections for minors' online activity, effective October 1, 2025, mandating data controllers to exercise reasonable care to avoid risks to minors and to conduct data protection impact assessments for services posing heightened risk to minors. observed
  3. Confirmed OneTrust DataGuidance — SB 24-041 preserves a 60-day cure period specifically for violations of the minors' protection provisions through the end of 2026. observed
  4. Confirmed OneTrust DataGuidance — SB 24-041 prohibits processing a minor's personal data for purposes of targeted advertising without consent. observed
  5. Confirmed McDermott Will & Emery — SB24-041 amends the CPA to add enhanced protections when a minor's data is processed and there is a heightened risk of harm to minors, effective October 1, 2025. observed
  6. Confirmed Security Boulevard — Colorado SB24-041 — Adds enhanced protections when a minor's data is processed and there is heightened risk of harm to minors, effective October 1, 2025. observed
  7. Confirmed McDermott Will & Schulte — Colorado SB24-041 notice-and-cure mechanism — The notice-and-60-day-cure mechanism attached to SB24-041's minor-data requirements sunsets on December 31, 2026. observed
  8. Confirmed FDATA — SB24-041 — heightened-risk-of-harm processing requires parent/guardian consent for under-13s observed
  9. Uncertain McDermott Will & Schulte — CPA rule amendments (minors' addictive design features) — adopted by Department of Law 2025-10-08, awaiting AG approval and Register publication observed

#

Enforcement authority and general mechanics are clear, but the absence of a private right of action, unresolved penalty-figure conflicts, and active AI Act litigation introduce material uncertainty.

Primary frameworkColorado Privacy Act, Colo. Rev. Stat. § 6-1-1311; Colorado Consumer Protection Act, Colo. Rev. Stat. Title 6, Article 1
Traffic-light rationale — AmberEnforcement authority and general mechanics are clear, but the absence of a private right of action, unresolved penalty-figure conflicts, and active AI Act litigation introduce material uncertainty.

Sub-modules (6)

Regulator powers and penaltiesAmber

The AG and DAs may investigate and bring enforcement actions treating CPA violations as deceptive trade practices; maximum-penalty figures reported in secondary sources conflict and require primary-source confirmation.

Claims (6):

  • The CPA assigns enforcement authority to the Colorado Attorney General and District Attorneys, who may investigate and bring actions treating CPA violations as deceptive trade practices under the Colorado Consumer Protection Act.
  • Civil penalties for CPA violations may reach up to $2,000 per violation, subject to a total maximum penalty of $500,000 for a related series of violations.
  • An alternative secondary-source figure reports CPA noncompliance penalties of up to $20,000 per violation under the Colorado Consumer Protection Act; this figure conflicts with the $2,000/$500,000 figure reported elsewhere and requires primary statutory confirmation.
  • Colorado Privacy Act (via Colorado Consumer Protection Act) — Per-violation penalties of up to $20,000, or up to $50,000 where the conduct also constitutes a deceptive trade practice.
  • ADMT Act (SB 26-189) — Only the Colorado Attorney General may enforce the ADMT Act, treating violations as deceptive trade practices under the Colorado Consumer Protection Act; before 1 Jan 2030 the AG must generally give 60 days' notice and an opportunity to cure where a cure is possible.
  • Colorado Consumer Protection Act — $20,000 per violation ($50,000 for violations against elderly persons)

Enforcement activity indexAmber

The AG's initial CPA enforcement posture (from July 2023) was educational/letter-based rather than punitive; no independently verified list of subsequent CPA-specific monetary penalties was located in this research pass.

Claims (3):

  • The Colorado Attorney General began CPA enforcement on July 12, 2023 with educational outreach letters focused on informing businesses of their obligations rather than immediate penalties.
  • Meta Platforms, Inc. — Colorado joined a nationwide multistate settlement requiring Meta to pay over $17 billion and implement child-safety reforms on Instagram and Facebook, announced 2026-08-26.
  • Colorado Attorney General CPA enforcement — $250,000 against an AdTech company for disregarding GPC signals from over 500,000 CO users

Regulator funding and capacityRed

No specific budget/headcount data for the Colorado AG's privacy enforcement unit was identified.

Collective redress and class actionsRed

No CPA-specific collective-redress or class-action mechanism distinct from general Colorado civil procedure was identified.

Private right of actionAmber

The CPA does not grant consumers a private right of action; enforcement is confined to the AG and District Attorneys.

Claims (3):

  • The Colorado Privacy Act does not provide consumers with a private right of action for violations.
  • Colorado Privacy Act — Does not establish a private right of action; the Attorney General and District Attorneys hold exclusive enforcement authority.
  • Colorado Privacy Act — Private citizens are not entitled to file lawsuits or enforce legal rights directly under the CPA.

Recent developments 180dAmber

Within the past 180 days: the AG solicited public comment on ADMT/chatbot-safety rulemaking (through July 13, 2026); SB 189 substantially overhauled the AI Act's framework and delayed its effective date to January 1, 2027; and xAI and the U.S. DOJ initiated litigation to block AI Act enforcement.

Claims (3):

  • The Colorado Attorney General's office is soliciting public comments on automated-decision-making-technology and chatbot-safety rulemaking through July 13, 2026.
  • xAI and the U.S. Department of Justice are litigating to block enforcement of the Colorado AI Act on constitutional grounds.
  • Unnamed AdTech company — Reported ~$250,000 penalty for ignoring GPC opt-out signals from 500,000+ Colorado users, as the first post-cure-period CPA enforcement action.
Category narrative 35 words

CPA penalties can reach $20,000 per violation. The notice-and-60-day-cure requirement for newly-added minors'/biometric provisions sunsets December 31, 2026; after that date the AG may proceed to enforcement without a mandatory cure opportunity for those provisions.

Periodic update · new data 2026-10-18

The ADMT Act's enforcement architecture is confirmed as narrow and centralized: only the Colorado Attorney General may enforce the statute, and a violation is treated as a deceptive trade practice under the Colorado Consumer Protection Act rather than as a standalone privacy-law violation. Before 1 January 2030, the Attorney General must generally give 60 days' notice and an opportunity to cure where a cure is possible; after that date, the notice-and-cure requirement no longer applies. The statute carries no private right of action, meaning individuals harmed by non-compliant automated decision-making cannot bring their own claims under the ADMT Act itself.

This enforcement model attaches from the Act's 1 January 2027 effective date, the same date on which the companion Chatbot Safety Act, HB 26-1263, also takes effect. The Colorado Consumer Protection Act's existing enforcement powers, which the ADMT Act borrows rather than duplicates, are themselves unchanged this cycle. The practical effect is that Colorado's AI-governance enforcement sits entirely within the Attorney General's existing deceptive-trade-practices authority rather than within any dedicated privacy or AI regulator.

Outlook

The notice-and-cure window narrows the Attorney General's early enforcement posture by design, giving deployers until 1 January 2030 to correct violations before facing enforcement without a cure opportunity. Whether the Attorney General brings any action under this framework before the 1 January 2027 effective date is not yet determinable; the more immediate question is whether the 26 October 2026 rulemaking hearing settles the 'materially influence' threshold that will define what counts as a violation in the first place.

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

Colorado's enforcement activity in 2026 spans three distinct strands. First, the Attorney General joined the nationwide multistate settlement with Meta Platforms, announced 26 August 2026, requiring payment of more than seventeen billion dollars and child-safety reforms on Instagram and Facebook. Second, an AdTech company is reported to have paid approximately two hundred fifty thousand dollars for ignoring Global Privacy Control opt-out signals from more than five hundred thousand Colorado users, reportedly the first enforcement action taken after the applicable Colorado Privacy Act cure period lapsed; the primary Attorney General source has not been independently confirmed. Third, the joint multistate sweep of 9 September 2025 with Connecticut and California, sending letters to non-compliant businesses regarding Global Privacy Control signals, set the investigative groundwork from which the reported settlement followed. The Colorado Privacy Act itself vests enforcement in the Attorney General and district attorneys, with no private right of action, and its general cure-notice period sunset on 1 January 2025, while a narrower cure opportunity for minors'-protection violations runs to 31 December 2026.

Outlook

Enforcement exposure in Colorado is on an escalating trajectory across both Global Privacy Control compliance and the broader multistate settlement track. Confirmation of the reported AdTech settlement's primary source, and clarity on enforcement practice following the 31 December 2026 sunset of the minors'-protection cure period, are the two items most likely to sharpen this picture going forward.

Periodic update · new data 2026-09-28

Enforcement of the Colorado Privacy Act rests exclusively with the Colorado Attorney General's Office and District Attorneys; no private right of action exists under the CPA, meaning individual consumers cannot bring their own lawsuits to enforce CPA rights directly. This centralized public-enforcement model is a stable, standing feature of Colorado's privacy-enforcement architecture and was not a new development this cycle, but it is the essential backdrop against which this cycle's enforcement-relevant development should be read.

That development is the scheduled sunset, on December 31, 2026, of the mandatory 60-day notice-and-cure period that currently applies to enforcement of the minors'- and biometric-data provisions. Under the current cure-period protection, the Attorney General's Office must generally provide covered entities a 60-day window to remediate a violation before pursuing enforcement action in these specific categories. Once that cure period sunsets, the Attorney General would be positioned to pursue enforcement action for minors'- and biometric-data violations without first affording that remediation opportunity, representing a genuine escalation in enforcement exposure for entities processing these data categories, distinct from any change to the underlying substantive obligations themselves.

Whether the Attorney General has issued any enforcement action or opinion letter regarding the forthcoming SB26-189 ADMT framework ahead of its January 1, 2027 effective date remains unresolved and was not established this cycle.

Outlook

The December 31, 2026 cure-period sunset is the key near-term date for enforcement exposure: entities processing minors' or biometric data should treat any known compliance gaps as urgent to remediate before that date, since the current 60-day cure protection will no longer be available in these categories thereafter.

Periodic update · new data 2026-09-05

The most structurally significant enforcement development in Colorado's privacy regime this cycle is one of standing posture rather than a single new action: the Colorado Privacy Act's original 60-day cure period sunset on 2025-01-01, after which the Colorado Attorney General has full discretion to enforce the Act without offering a cure opportunity to violators. Per-violation penalties under this enforcement authority can reach 20,000 dollars. This structural shift is the backdrop against which the Attorney General's disclosed 250,000 dollar penalty against an adtech company, arising from an April 2025 universal-opt-out and Global Privacy Control compliance sweep, should be read: it is understood to be the first disclosed Colorado Privacy Act enforcement action taken after the cure period's sunset.

The removal of the cure-period requirement is significant because it changes the practical risk calculus for controllers and processors: prior to 2025-01-01, a violation identified by the Attorney General's office would typically first generate a cure notice, giving the violator 60 days to correct the deficiency before facing a penalty; after the sunset, the office may proceed directly to enforcement and penalty assessment, without that intervening correction opportunity, for at least some class of violations.

Outlook

Given the disclosed adtech action and the removal of the cure-period backstop, continued and potentially expanding enforcement activity is a plausible trajectory for Colorado's privacy regime going forward, though the evidence available this cycle does not identify any further specific enforcement action beyond the disclosed adtech penalty. A sourcing gap exists around the specific penalty figures: no Tier 1 source was independently retrieved this cycle confirming the 250,000 dollar penalty or the 20,000-dollar-per-violation ceiling; both rely on secondary reporting, a point worth flagging even as the underlying enforcement-posture shift is otherwise treated as reliably established.

Sources and claims (15)
  1. Confirmed OneTrust DataGuidance — The CPA assigns enforcement authority to the Colorado Attorney General and District Attorneys, who may investigate and bring actions treating CPA violations as deceptive trade practices under the Colorado Consumer Protection Act. observed
  2. Probable OneTrust DataGuidance — Civil penalties for CPA violations may reach up to $2,000 per violation, subject to a total maximum penalty of $500,000 for a related series of violations. observed
  3. Uncertain International Association of Privacy Professionals — An alternative secondary-source figure reports CPA noncompliance penalties of up to $20,000 per violation under the Colorado Consumer Protection Act; this figure conflicts with the $2,000/$500,000 figure reported elsewhere and requires primary statutory confirmation. observed
  4. Confirmed OneTrust DataGuidance — The Colorado Attorney General began CPA enforcement on July 12, 2023 with educational outreach letters focused on informing businesses of their obligations rather than immediate penalties. observed
  5. Confirmed International Association of Privacy Professionals — The Colorado Privacy Act does not provide consumers with a private right of action for violations. observed
  6. Confirmed OneTrust DataGuidance — The Colorado Attorney General's office is soliciting public comments on automated-decision-making-technology and chatbot-safety rulemaking through July 13, 2026. observed
  7. Probable OneTrust DataGuidance — xAI and the U.S. Department of Justice are litigating to block enforcement of the Colorado AI Act on constitutional grounds. observed
  8. Probable Colorado Attorney General — Meta Platforms, Inc. — Colorado joined a nationwide multistate settlement requiring Meta to pay over $17 billion and implement child-safety reforms on Instagram and Facebook, announced 2026-08-26. observed
  9. Probable PrivacyLawMap — Colorado Privacy Act (via Colorado Consumer Protection Act) — Per-violation penalties of up to $20,000, or up to $50,000 where the conduct also constitutes a deceptive trade practice. observed
  10. Confirmed Usercentrics — Colorado Privacy Act — Does not establish a private right of action; the Attorney General and District Attorneys hold exclusive enforcement authority. observed
  11. Probable Usercentrics — Colorado Privacy Act — Private citizens are not entitled to file lawsuits or enforce legal rights directly under the CPA. observed
  12. Uncertain Primary statutory record — Unnamed AdTech company — Reported ~$250,000 penalty for ignoring GPC opt-out signals from 500,000+ Colorado users, as the first post-cure-period CPA enforcement action.
  13. Probable Secure Privacy — ADMT Act (SB 26-189) — Only the Colorado Attorney General may enforce the ADMT Act, treating violations as deceptive trade practices under the Colorado Consumer Protection Act; before 1 Jan 2030 the AG must generally give 60 days' notice and an opportunity to cure where a cure is possible. observed
  14. Probable Usercentrics — Colorado Consumer Protection Act — $20,000 per violation ($50,000 for violations against elderly persons) observed
  15. Uncertain McDermott Will & Emery — Colorado Attorney General CPA enforcement — $250,000 against an AdTech company for disregarding GPC signals from over 500,000 CO users 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), 88 claim(s) (88 category placement(s)), 64 source(s) in the cumulative register.

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

GDPR article map

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

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