Colorado SB 26-189 · ADMT in consequential decisions
Record keeping and evidence under SB 26-189
Developers must retain records reasonably necessary to demonstrate compliance for not less than three years after the record is created (C.R.S. 6-1-1702(4)), and deployers for not less than three years after the date of the consequential decision (6-1-1703), or longer if other law requires. The statute does not prescribe a record format. What you keep, and how, is a judgment to make with counsel.
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 retention: 6-1-1702(4)
A developer shall retain, for not less than three years after the creation of a record required or created under 6-1-1702, or for a longer period if required by applicable state or federal law, records reasonably necessary to demonstrate compliance with that section. The statute says records include system version identifiers, changelogs, and documentation and notices of material updates provided to deployers under 6-1-1702(2).
The clock runs from creation of each record, so a changelog entry or update notice has its own retention period.
Deployer retention: 6-1-1703
A deployer shall retain, for not less than three years after the date of a consequential decision, or for a longer period if required by applicable state or federal law, records reasonably necessary to demonstrate compliance with part 17. Records may include, as applicable, covered ADMT version identifiers, changelogs, and documentation of material mitigation changes.
Here the clock runs from the date of the consequential decision, not from when a record was made. A pre-use notice shown on one date and a disclosure sent 30 days after the decision are both tied to the decision date for retention purposes.
| Party | Statute | Minimum retention | Clock starts |
|---|---|---|---|
| Developer | C.R.S. 6-1-1702(4) | Not less than three years, or longer if other law requires | Creation of the record |
| Deployer | C.R.S. 6-1-1703 | Not less than three years, or longer if other law requires | Date of the consequential decision |
What the statute does not prescribe
Neither section prescribes a record format, schema, storage system, or an exhaustive list of records. The standard is records "reasonably necessary to demonstrate compliance." The listed items (version identifiers, changelogs, documentation of material mitigation changes) are examples of what records may include. The statute does not say a regulator will ask for a particular artifact. Anything beyond the statutory text below is practice, not requirement.
Evidence worth keeping (practice, not statutory requirement)
This list is a practical suggestion for building an evidence trail. It is not a statutory checklist, and meeting it does not establish compliance. Counsel should decide what is reasonably necessary for your use cases.
- Versions of the pre-use notice shown to consumers (6-1-1704(1)-(2)), with timestamps of when each version was live or shown.
- ADMT name, version, and developer for each decision, since the adverse-outcome disclosure refers to these (6-1-1704(3)(b)).
- For adverse outcomes, the disclosure content and the time it was sent, checked against the 30-day period (6-1-1704(3)).
- Categories and sources of personal data used, to the extent you receive them from the developer.
- Notices to consumers when a trade secret or legally protected information was withheld (6-1-1704(5)), and developer notices when information was withheld from you (6-1-1702(1)(e)).
- Consumer correction and human-review requests, how they were handled, and outcomes (6-1-1705).
- Reviewer identity and authority, and the information the reviewer had (6-1-1701(15)).
- Developer-supplied documentation and update notices you received, and any mitigation changes you made.
Enforcement context
Violations of the disclosure requirements and consumer rights in 6-1-1702 through 6-1-1705 are enforceable exclusively by the Attorney General (6-1-1706(1)(b)). Before any enforcement action, the Attorney General shall issue a notice of violation if a cure is deemed possible by the Attorney General (6-1-1706(3)(a)); if the developer or deployer fails to cure within 60 days after receipt, the Attorney General may bring an action (6-1-1706(3)(b)). No cure period is required where the Attorney General finds and can demonstrate a knowing or repeated violation (6-1-1706(3)(c)). Subsection (3), the cure provision, is repealed effective January 1, 2030 (6-1-1706(3)(f)). The part creates no new private right of action (6-1-1706(4); 6-1-1709(1)).
Records matter in this setting because the retention standard is tied to demonstrating compliance. Compliance with part 17 is also not a defense to noncompliance with other applicable law (6-1-1709(2)).
How CertifiedData supports evidence
Hash-chained, signed ledgers support evidence for the integrity of the records you keep. Decision Ledger records are canonicalized (RFC 8785 JCS), SHA-256 hashed, Ed25519 signed, and hash-chained, so modifying a recorded entry is detectable. A third party can verify them independently using the public key and the public verifier at /verify. The audit bundle export is a ZIP with the certificate, transparency log entry, public key, and verification instructions.
The Colorado ADMT evidence pack is an authenticated export that packages Colorado-specific decision metadata (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 equal to the decision date plus three years) together with hash-chain and signature verification material. Documentation is at /compliance/colorado-sb-26-189/evidence-pack.
Retention is your responsibility. The retention-until date in the export is a recorded value computed from the decision date; it is not a statement that CertifiedData retains your data for three years. You must configure and confirm retention and storage settings yourself. The evidence pack records what you supply and does not decide coverage or whether a disclosure was adequate.
Frequently asked questions
How long must a deployer keep records under SB 26-189?
Not less than three years after the date of the consequential decision, or longer if other state or federal law requires (C.R.S. 6-1-1703). The records covered are those reasonably necessary to demonstrate compliance with part 17.
Does the statute say what format records must be in?
No. Sections 6-1-1702(4) and 6-1-1703 set retention periods and give examples such as version identifiers and changelogs, but they do not prescribe a format or schema.
Does a signed, hash-chained ledger satisfy the retention requirement?
Not by itself. It supports evidence for the integrity of the records, since modification is detectable, but the statute concerns retention for a minimum period. You must separately confirm that records are retained for the required duration.
Can a consumer sue under SB 26-189 if records are missing?
The part creates no new private right of action (C.R.S. 6-1-1706(4) and 6-1-1709(1)). Enforcement of the disclosure and rights provisions is exclusive to the Attorney General, and existing rights under other law are not limited.
Related
Sources
- SB 26-189 enacted session law (S.L. 2026, ch. 131; C.R.S. 6-1-1701 to 6-1-1709), approved May 14, 2026
- SB 26-189 enrolled text (LegiScan)
- SB 26-189 fiscal note (Senate 2nd reading, May 6, 2026)
- Colorado Attorney General — ADMT and chatbot rulemaking page
- AG proposed rules, interim draft redline (Oct 6, 2026) — 4 CCR 904-6, proposed
- AG Regulatory Analysis (Oct 21, 2026)
- Colorado Secretary of State eDocket, tracking no. 2026-00360