CertifiedData.io

Colorado SB 26-189 · ADMT in consequential decisions

Developer vs. deployer obligations under SB 26-189

Under Colorado SB 26-189, developers of covered ADMT must give deployers documentation and update notices and keep records for at least three years (C.R.S. 6-1-1702). Deployers must keep records, give consumers a notice before use, send a disclosure within 30 days after an adverse outcome, and honor correction and human-review rights (6-1-1703 to 6-1-1705). The Attorney General enforces the law exclusively (6-1-1706).

Last reviewed: November 13, 2026 · Published

Not legal advice. This page is general information about Colorado SB 26-189 for engineering, product, and governance teams. It is not legal advice and does not create an attorney-client relationship. CertifiedData supports evidence for record keeping and disclosures; it does not determine whether a system is covered by the law and does not make any organization compliant. Confirm your obligations with qualified Colorado counsel.

Attorney General rule text referenced on this page is a proposed interim draft (released October 6, 2026) for 4 CCR 904-6 and is subject to change. As of November 13, 2026 no adopted final rule was shown on the Attorney General's rulemaking page.

Developer obligations (C.R.S. 6-1-1702)

On and after January 1, 2027, a developer must make the following available to each deployer of a covered ADMT it developed, in a form reasonably understandable to a deployer and in a way that protects trade secrets or information protected from disclosure by law (6-1-1702(1)):

  • (a) A general statement describing intended uses and known harmful or inappropriate uses.
  • (b) A description of the categories of data, including personal data, used to train the covered ADMT, to the extent known.
  • (c) Known limitations, including known risks and circumstances in which the covered ADMT should not be used.
  • (d) Instructions for the deployer's appropriate use, monitoring, and meaningful human review, where applicable.
  • (e) Information reasonably necessary for the deployer to comply with 6-1-1704. If information is withheld, the developer must notify the deployer.

Under 6-1-1702(2)(a), a developer must give each deployer notice of material updates, intentional and substantial modifications, and changes to intended use, limitations, or risk mitigation within a reasonable time. Under (2)(b), public release notes can satisfy this if the developer also gives each deployer direct notice of the public release.

Scope is limited by 6-1-1702(3): the disclosure duties apply only to a deployer's use of a covered ADMT that was marketed, advertised, configured, contracted, sold, or licensed to be used to materially influence a consequential decision. Under (5), the section applies when a developer creates a covered ADMT intended, documented, marketed, advertised, configured, or contracted for consequential decisions, or when the developer becomes aware it is being used that way consistent with intended and contracted uses.

Retention (6-1-1702(4)): keep records reasonably necessary to demonstrate compliance for not less than three years after the record is created, or longer if other state or federal law requires. Records include system version identifiers, changelogs, and documentation and notices of material updates provided to deployers.

Deployer obligations (C.R.S. 6-1-1703 to 6-1-1705)

  • Record keeping (6-1-1703): retain records reasonably necessary to demonstrate compliance for not less than three years after the date of a consequential decision, or longer if other law requires. Records may include covered ADMT version identifiers, changelogs, and documentation of material mitigation changes.
  • Pre-use notice (6-1-1704(1)-(2)): before using a covered ADMT to materially influence a consequential decision, give the consumer a clear and conspicuous notice that a covered ADMT was or will be used, with instructions on obtaining additional information. A prominent public notice reasonably accessible at points of consumer interaction, including a link or posting reasonably proximate to the interaction, satisfies this.
  • Post-adverse-outcome disclosure (6-1-1704(3)): within 30 days after the decision, give a plain-language description of the decision and the ADMT's role, instructions and a simple process to request more information (ADMT name, version number if applicable, developer, and types, categories, and sources of personal data used, to the extent the deployer receives the information from the developer), and an explanation of the 6-1-1705 rights.
  • Trade secrets (6-1-1704(5)): a deployer need not disclose a trade secret or legally protected information, but if it withholds information it must notify the consumer.
  • Consumer rights (6-1-1705(1)): on request after an adverse outcome, provide instructions for requesting personal data and correcting factually incorrect or materially inaccurate personal data used in the decision, and an opportunity for meaningful human review and reconsideration to the extent commercially reasonable. Correction does not extend to opinions, predictions, scores, or protected evaluations (6-1-1705(1)(c)).
  • Accessibility (6-1-1704(8)): developers and deployers must provide required notices and disclosures in a manner reasonably accessible to consumers with disabilities and limited English proficiency, consistent with applicable law.

Side-by-side comparison

TopicDeveloperDeployer
DocumentationProvide intended uses, training data categories, limitations, use/monitoring/human-review instructions, and disclosure-support information to deployers (6-1-1702(1))Receives developer documentation; uses it to build disclosures (6-1-1704(3)(b))
Change noticesNotice of material updates, substantial modifications, and changes to use/limitations/mitigation (6-1-1702(2))No equivalent duty; may keep records of material mitigation changes (6-1-1703)
Consumer-facing noticeNone directlyPre-use notice or public posting (6-1-1704(1)-(2))
Adverse outcomeNone directlyDisclosure within 30 days (6-1-1704(3))
Consumer rightsNone directlyCorrection and human review (6-1-1705)
RetentionAt least 3 years after record creation (6-1-1702(4))At least 3 years after the decision (6-1-1703)
Accessibility6-1-1704(8)6-1-1704(8)

Liability allocation and enforcement

Section 6-1-1707 provides that a developer or deployer may be held liable in an unlawful-discrimination action under state anti-discrimination law arising from a consequential decision materially influenced by a covered ADMT, with fault allocated by relative fault and no joint and several liability beyond what existing law permits. A developer is liable only to the extent its ADMT was used as intended, documented, marketed, advertised, configured, or contracted, and materially influenced the decision. Under 6-1-1707(7)(a), a contract provision that indemnifies, defends, or holds harmless a party against liability from its own acts or omissions in violation of the Colorado Anti-Discrimination Act or other Colorado anti-discrimination law is contrary to public policy and void.

Under 6-1-1706, the Attorney General enforces part 17 through the Colorado Consumer Protection Act, a violation is a deceptive trade practice, and enforcement of 6-1-1702 through 6-1-1705 is exclusive to the Attorney General. Before enforcement, the Attorney General must issue a notice of violation if a cure is deemed possible, with 60 days to cure; no cure period is required for knowing or repeated violations. That cure provision is repealed effective January 1, 2030. Part 17 creates no new private right of action (6-1-1706(4), 6-1-1709(1)).

How CertifiedData supports evidence

CertifiedData helps both sides produce records. Developers can anchor version identifiers and update notices in Decision Ledger records, which are canonicalized with RFC 8785 JCS, SHA-256 hashed, Ed25519 signed, and hash-chained so modification is detectable. Audit bundle export produces a ZIP with the certificate, transparency log entry, public key, and verification instructions, and anyone can check material at /verify.

For deployers, the Colorado ADMT evidence pack (/compliance/colorado-sb-26-189/evidence-pack) is an authenticated export that packages ADMT name, version, and developer, covered domain, adverse-outcome flag, pre-use notice reference, disclosure timestamp and 30-day deadline check, data categories, trade-secret flag, consumer correction and human-review requests, and a retention-until date (decision date plus three years), together with verification material. It records what the deployer supplies; it does not decide whether a disclosure was adequate.

Frequently asked questions

How long must developers and deployers keep records?

At least three years: developers from creation of the record (C.R.S. 6-1-1702(4)), deployers from the date of the consequential decision (6-1-1703), or longer if other law requires.

Can a developer use public release notes to notify deployers of updates?

Yes, if the notes contain the information required by 6-1-1702(2)(a) and the developer gives direct notice of the public release to each deployer (6-1-1702(2)(b)).

Can a contract shift anti-discrimination liability entirely to the other party?

Not for a party's own acts or omissions. Under 6-1-1707(7)(a), an indemnity of that kind relating to Colorado anti-discrimination law violations is void as contrary to public policy, with limits stated in 6-1-1707(7)(b)-(d).

Can individuals sue under SB 26-189?

No new private right of action is created, and the Attorney General has exclusive enforcement of 6-1-1702 to 6-1-1705. Existing rights and remedies under other law, such as the Colorado Anti-Discrimination Act, are not reduced (6-1-1706(4)).

Developer vs. Deployer Duties: Colorado SB 26-189 | CertifiedData