Reference Source

SENATE BILL 24-205 (Colorado) — effective February 1, 2026

For SENATE BILL 24-205 (Colorado), effective date is February 1, 2026; what it applies to is developers and deployers of high-risk artificial intelligence systems, under part 17 of article 1 of title 6 which this act adds, recorded from its source on 2026-09-08; source re-checked 2026-10-15.

Jurisdiction
Colorado our reading
Instrument
SENATE BILL 24-205 verified
Effective date
February 1, 2026 verified
What it applies to
developers and deployers of high-risk artificial intelligence systems, under part 17 of article 1 of title 6 which this act adds our reading
Superseded by
Senate Bill 25B-004 replaced the February 1, 2026 date with June 30, 2026; Senate Bill 26-189 then repealed and reenacted, with amendments, part 17 of article 1 of title 6 effective January 1, 2027 our reading
Sourceleg.colorado.gov
Verified
Review by
DatasetAI law and regulation effective dates by jurisdiction

Values marked our reading are our classification of what the source says — the source does not print them in those words. The quote below is the evidence for each one; judge it yourself.

What the source says

6-1-1702. Developer duty to avoid algorithmic discrimination - required documentation. (1) ON AND AFTER FEBRUARY 1, 2026, A DEVELOPER OF A HIGH-RISK ARTIFICIAL INTELLIGENCE SYSTEM SHALL USE REASONABLE CARE TO PROTECT CONSUMERS FROM ANY KNOWN OR REASONABLY FORESEEABLE RISKS OF ALGORITHMIC DISCRIMINATION ARISING FROM THE INTENDED AND CONTRACTED USES OF THE HIGH-RISK ARTIFICIAL INTELLIGENCE SYSTEM.

— leg.colorado.gov, retrieved 2026-09-08

Where each value comes from

The value above is stated away from the sentence quoted with the answer, so the passage that states it is shown here too.

Instrument

SENATE BILL 24-205

— all from leg.colorado.gov, retrieved 2026-09-08

Source

Last verified against source: . Due for re-check by . This page as Markdown · OKF bundle · full dataset as JSON.

This one changes, and we watch it.AI law and regulation effective dates by jurisdiction is re-read on a schedule and every change is dated. Subscribe: Atom feed · JSON · what has changed so far.