Age Attestation on Computing Devices
Concerning age attestation for users of computing devices.
Official status: Became Law
Prime sponsors
- Matt Ball (Senate) — Prime Sponsor
- Larry Liston (Senate) — Prime Sponsor
- Amy Paschal (House) — Prime Sponsor
- Naquetta Ricks (House) — Prime Sponsor
Progress (from the official record)
Official summary
Official text — shown in English exactly as published by the official source. The official text controls.
The act requires an operating system provider that operates a publicly available internet website, software application, online service, or platform that distributes and facilitates, on a commercial basis, the download of applications from third-party developers to users of devices (covered application store) or makes a covered application store available preinstalled on an operating system to: Provide an accessible interface at account setup that requires an account holder to indicate the birth date, age, or age bracket of the user of that device in order to provide a signal regarding the user's age (age signal) to applications available in the covered application store; Provide application developers with a reasonably consistent, real-time application programming interface to request and receive an age signal; and Send only the minimum amount of information necessary to comply with the act. An operating system provider or covered application store shall not share an age signal with a third party for a purpose not required by the act. The act requires a consumer software application that is accessed through a covered application store and that may be run or directed by a user on a device (covered application) to request an age signal with respect to a particular user when the covered application is initially launched or when a user first creates an account. A covered application that receives an age signal is deemed to have knowledge of the age range of the user to whom that age signal pertains across all platforms of the application and points of access of the application. However, if a developer has clear and convincing information that a user's age is different than the age indicated by an age signal, the developer shall use that information as the primary indicator of the user's age range. A developer shall ensure that a covered application that receives an age signal does not: Request more information concerning a user from an operating system provider or a covered application store than is necessary to comply with the act; or Communicate an age signal to a third party for a purpose not required by the act. With respect to a device for which account setup was completed before July 1, 2028, the act requires an operating system provider to provide, before January 1, 2029, an accessible interface that allows an account holder to indicate the birth date or age of the user of that device for the purpose of providing an age signal regarding the user's age-bracket data to covered applications available in the operating system provider's covered application store. If a covered application last updated on or after July 1, 2027, was downloaded to a device before July 1, 2028, and the covered application has not requested an age signal with respect to the user of the device on which the covered application was downloaded, the covered application must request an age signal from the covered application store from which the covered application was downloaded with respect to that user before January 1, 2029. A person that violates the act must pay a civil penalty of not more than $2,500 for each minor affected by each negligent violation or not more than $7,500 for each minor affected by each intentional violation. The penalty is assessed and recovered in a civil action brought by the attorney general. An operating system provider or covered application store that makes a good faith effort to comply with the act is not liable for an erroneous age signal or for conduct by a covered application that receives an age signal. (Note: This summary applies to this bill as enacted.)
Status timeline
| Date | Location | Action |
|---|---|---|
| 01/27/2026 | Senate | Introduced In Senate - Assigned to Business, Labor, & Technology |
| 02/24/2026 | Senate | Senate Committee on Business, Labor, & Technology Refer Amended - Consent Calendar to Senate Committee of the Whole |
| 02/27/2026 | Senate | Senate Second Reading Laid Over to 03/02/2026 - No Amendments |
| 03/02/2026 | Senate | Senate Second Reading Passed with Amendments - Committee |
| 03/03/2026 | Senate | Senate Third Reading Passed - No Amendments |
| 04/06/2026 | House | Introduced In House - Assigned to Business Affairs & Labor |
| 04/23/2026 | House | House Committee on Business Affairs & Labor Refer Amended to House Committee of the Whole |
| 04/28/2026 | House | House Second Reading Laid Over Daily - No Amendments |
| 04/29/2026 | House | House Second Reading Special Order - Passed with Amendments - Committee, Floor |
| 04/30/2026 | House | House Third Reading Passed - No Amendments |
| 05/01/2026 | Senate | Senate Considered House Amendments - Result was to Concur - Repass |
| 05/12/2026 | Senate | Signed by the President of the Senate |
| 05/12/2026 | House | Signed by the Speaker of the House |
| 05/12/2026 | Governor | Sent to the Governor |
| 06/03/2026 | Governor | Governor Signed |
Recorded votes
- 04/23/2026 — House Business Affairs & Labor: “Refer Senate Bill 26-051, as amended, to the Committee of the Whole.” — the motion passed on a vote of 7–6.
- 02/24/2026 — Senate Business, Labor, & Technology: “Refer Senate Bill 26-051, as amended, to the Committee of the Whole and with a recommendation that it be placed on the consent calendar.” — the motion passed on a vote of 5–0.
Proposed amendments (7 proposed amendments)
| Amendment | Committee / floor hearing | Offered | Disposition | Official document |
|---|---|---|---|---|
| L.001 | Committee amendment — Business, Labor, & Technology (Senate) | 02/24/2026 | Passed | View official document |
| L.005 | Committee amendment — Business Affairs & Labor (House) | 04/23/2026 | Passed | View official document |
| L.006 | Committee amendment — Business Affairs & Labor (House) | 04/23/2026 | Passed | View official document |
| L.004 | Committee amendment — Business Affairs & Labor (House) | 04/23/2026 | Passed | View official document |
| L.008 Sponsor: Representative Paschal | Floor amendment — Second Reading (House) | 04/29/2026 | Passed | View official document |
| L.009 Sponsor: Representative Richardson | Floor amendment — Second Reading (House) | 04/29/2026 | Lost | View official document |
| L.010 Sponsor: Representative Richardson | Floor amendment — Second Reading (House) | 04/29/2026 | Lost | View official document |
Source: Colorado General Assembly (leg.colorado.gov) · Data as of
Full text
- Signed Act version (official PDF), 06/04/2026
- Final Act version (official PDF), 05/07/2026
- Rerevised version (official PDF), 04/30/2026
- Revised version (official PDF), 04/29/2026
- Reengrossed version (official PDF), 03/03/2026
- Engrossed version (official PDF), 03/02/2026
- Introduced version (official PDF), 01/27/2026
Official record
View SB26-051 on leg.colorado.gov
Source: Colorado General Assembly (leg.colorado.gov) · Data as of
Verify this record
This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.
SHA-256 fingerprint
2ccbfe4afcd5f37bbeb1d04f1c1b23128fcd8bcfc9dcf6d1f2929e94a6d21cd7
What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.
The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.
If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.
