CertifiedData.io

Colorado SB 26-189 · ADMT in consequential decisions

Consumer notices and adverse-outcome disclosures under SB 26-189

Colorado SB 26-189 requires a deployer to give consumers a clear and conspicuous notice before using a covered ADMT to materially influence a consequential decision, and to send a disclosure within 30 days after an adverse outcome (C.R.S. 6-1-1704). The Attorney General's proposed interim draft Rule 7 (October 6, 2026, subject to change) would add detail on form, timing, content, and responses to consumer requests.

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.

Pre-use notice and public posting

Before a deployer uses a covered ADMT to materially influence a consequential decision, it must give the consumer a clear and conspicuous notice that it used or will use a covered ADMT in a consequential decision affecting the consumer, with instructions on how to obtain the additional information described in the section (6-1-1704(1)).

Under 6-1-1704(2), a deployer complies by maintaining a prominent public notice reasonably accessible at points of consumer interaction, including a link or posting reasonably proximate to the interaction or transaction in which a consequential decision may occur.

What is an adverse outcome, and what must the 30-day disclosure say?

Section 6-1-1701(1) defines an adverse outcome as (a) a decision that denies, terminates, revokes, or materially reduces or restricts a consumer's access to, eligibility for, selection for, compensation for, or the provision of an opportunity or service, or (b) a decision that results in materially less favorable differentiated price, cost, compensation, or other material terms reasonably likely to materially limit, delay, or effectively deny, or otherwise fundamentally alter, such access compared to terms offered to similarly situated consumers.

If a deployer uses a covered ADMT to materially influence a consequential decision that results in an adverse outcome, it must provide the following within 30 days after making the decision (6-1-1704(3)):

  • (a) A plain-language description of the consequential decision and the role the covered ADMT played.
  • (b) Instructions and a simple-to-follow process to request additional information about the covered ADMT and its inputs: the ADMT name, version number if applicable, developer, and the types, categories, and sources of personal data used, to the extent the deployer receives the necessary information from the developer under 6-1-1702.
  • (c) An explanation of the consumer rights in 6-1-1705 and how to exercise them.

Section 6-1-1704(4) states the General Assembly's intent that disclosure specifics be clarified by rulemaking, and directs the Attorney General to adopt rules on or before January 1, 2027, which may cover personal-data content, sector-specific examples, standards for describing the ADMT's role, and interaction with other notice laws.

Trade secrets, creditors, accessibility, education, and health care

  • Trade secrets (6-1-1704(5)): a deployer need not disclose a trade secret or information protected by state or federal law, but must notify the consumer if it withholds information.
  • Creditors (6-1-1704(6)): a creditor that is required to provide, and provides, a notice under the Equal Credit Opportunity Act and Regulation B (and the Fair Credit Reporting Act when applicable) complies with the notice or disclosure requirements of the section for the same decision if that notice also satisfies those requirements, and need not send a separate or duplicative notice. Such a notice may include a brief statement that a covered ADMT was used to materially influence the decision and instructions for obtaining additional information or exercising rights (6-1-1704(6)(d)).
  • Prohibited or protected disclosures (6-1-1704(7)): part 17 does not require a disclosure to the extent it would be prohibited by federal law or would compromise confidentiality or integrity of cybersecurity, fraud prevention, anti-money laundering, counter-terrorist financing, or economic sanctions programs required by law.
  • Accessibility (6-1-1704(8)): notices and disclosures must be reasonably accessible to consumers with disabilities and limited English proficiency, consistent with applicable law.
  • FERPA (6-1-1704(9)): for education decisions, a deployer subject to FERPA satisfies the notice requirements by using processes and channels consistent with FERPA notices and student record access procedures, including notice to a parent, guardian, or eligible student, without a separate duplicative process.
  • HIPAA covered entities (6-1-1708(3)(c)-(e)): a covered entity must give patients a general notice of use of advanced technologies, including a covered ADMT, which may be combined with other patient notices. A covered entity using a covered ADMT to determine financial assistance eligibility must provide specified disclosures, either as an advance general disclosure or within thirty calendar days after an adverse outcome.

Proposed AG Rule 7: adverse outcome disclosures (interim draft, October 6, 2026)

Everything in this section is a proposed interim draft (October 6, 2026) of 4 CCR 904-6, subject to change. It is a redline in which struck and inserted text appear together. Verify each point against the current official version before relying on it.

Form and timing (proposed Rules 7.2 and 7.3)

The draft would require the disclosure to be in writing, including electronically, and delivered through the channels the deployer typically uses to interact with the consumer, with electronic delivery where the deployer communicates electronically. Printed disclosures would be in at least 12-point font, and the disclosure would need to meet the general consumer-communication requirements of Rule 3.2. Notification would occur when the deployer delivers the disclosure, for example by email, mail, messaging portal, or text message.

Content (proposed Rule 7.4)

  • Rule 7.4(A) restates the three statutory elements of 6-1-1704(3)(a)-(c).
  • Rule 7.4(B) would require the decision description to say what decision was made and, where applicable, the effective date of an adverse outcome such as a termination or reduction of an existing benefit; the ADMT's role to be described with specificity and accuracy, including the purpose, how the ADMT was used, and the role of any human reviewers; and the principal reasons for the adverse outcome with specificity. Vague statements such as reliance on internal standards are given as examples of insufficient descriptions.
  • Rule 7.4(B) would also require that, where a principal reason is an inference or a profile, risk, or other score, the disclosure identify the inference or state the score and explain the underlying personal data; that automatic-denial factors be disclosed; and, where the outcome stemmed from insufficient or incomplete information, that the disclosure say so and identify the additional information needed.
  • Rule 7.4(B) would restate that a trade secret need not be disclosed but the consumer must be notified of the withholding, and that a deployer missing developer information should provide as much specificity as it can from what it received.
  • Rule 7.4(C) would require the instructions to offer one or more specific request methods, including an online method via a hyperlink or URL, any process to be easy to follow with a minimal number of steps, and requests to be possible at any time of day.
  • Rule 7.4(D) would require the disclosure to explain the consumer's right to request instructions for obtaining and correcting personal data and the right to meaningful human review and reconsideration to the extent commercially reasonable, and to provide a unified method for exercising these rights and requesting information.

Sector examples (proposed Rule 7.5)

Rule 7.5 would give illustrative disclosure examples for education, residential real estate, financial or lending services, insurance, and employment. The draft states the examples are illustrative and not exhaustive, and that deployers must determine whether a disclosure is needed and what it must contain.

Responses to consumer requests (proposed Rule 7.6)

Rule 7.6 would govern how a deployer responds when a consumer requests the additional ADMT information under 6-1-1704(3)(b): the response would include the ADMT name, version if applicable, developer, and types, categories, and sources of personal data, with sources identified by name when known to the deployer. The redline contains overlapping struck and inserted timing language (including a fifteen-day period and a ten-business-day period), so confirm the operative response deadline in the current official draft.

Interaction with other law and miscellaneous (proposed Rules 7.7 and 7.8)

Rule 7.7 would treat an ECOA or FCRA adverse action or risk-based pricing notice as satisfying 6-1-1704(3) if it contains the information in 6-1-1704(3)(b)-(c) and Rule 7.4(C)-(D) (which may be in a supplemental disclosure delivered at the same time) and is provided within 30 days after the decision. Similar treatment is proposed for FERPA-subject deployers and for notices required by other federal, state, or local law. Rule 7.8 would allow additional voluntary information and would prohibit retaliation against a consumer for exercising rights under 6-1-1704 and 6-1-1705.

How CertifiedData supports evidence

CertifiedData helps you produce records showing what was sent and when. Decision Ledger records are canonicalized with RFC 8785 JCS, SHA-256 hashed, Ed25519 signed, and hash-chained so modification is detectable, and can be checked at /verify. Audit bundle export produces a ZIP with the certificate, transparency log entry, public key, and verification instructions.

The Colorado ADMT evidence pack (/compliance/colorado-sb-26-189/evidence-pack) records the adverse-outcome flag, pre-use notice reference, disclosure timestamp and a 30-day deadline check, ADMT name, version, and developer, data categories, trade-secret flag, and consumer correction and human-review requests, together with hash-chain and signature verification material. It records what the deployer supplies. It does not decide whether a disclosure was adequate.

Frequently asked questions

How soon must an adverse-outcome disclosure be sent?

Within 30 days after making the decision (C.R.S. 6-1-1704(3)). The Attorney General's proposed Rule 7.7 uses the same 30-day period for ECOA, FCRA, and other-law notices relied on for compliance.

Can a lender rely on its ECOA adverse action notice?

Under 6-1-1704(6), yes if the ECOA (and FCRA, when applicable) notice is required, is provided, and also satisfies the section's notice requirements, in which case no separate notice is required.

Do I have to disclose trade secrets in the disclosure?

No, but if you withhold information on that basis you must notify the consumer (6-1-1704(5)).

Are the Attorney General's Rule 7 requirements final?

No. They come from a proposed interim draft (October 6, 2026) and are subject to change until final rules are adopted.

Colorado SB 26-189 Consumer Notices & Disclosures | CertifiedData