Colorado SB 51 — Age Attestation on Computing Devices

Colorado, 2026A. SB 51: Age Attestation on Computing Devices

Plural source record ↗

Official legislative source ↗

Latest action

June 3, 2026 — Governor Signed

Summary

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; andSend 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; orCommunicate 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.)

Sponsors

• M. Ball — primary sponsor
• L. Liston — primary sponsor
• A. Paschal — primary sponsor
• N. Ricks — primary sponsor
• N. Hinrichsen
• M. Lindsay
• T. Story

Bill text

Signed Act Read version ↗

Final Act Read version ↗

Rerevised Read version ↗

Revised Read version ↗

Reengrossed Read version ↗

Engrossed Read version ↗

Introduced Read version ↗

Recorded votes

Legislative history

1. January 27, 2026Introduced In Senate - Assigned to Business, Labor, & Technology
2. February 24, 2026Senate Committee on Business, Labor, & Technology Refer Amended - Consent Calendar to Senate Committee of the Whole
3. February 27, 2026Senate Second Reading Laid Over to 03/02/2026 - No Amendments
4. March 2, 2026Senate Second Reading Passed with Amendments - Committee
5. March 3, 2026Senate Third Reading Passed - No Amendments
6. April 6, 2026Introduced In House - Assigned to Business Affairs & Labor
7. April 23, 2026House Committee on Business Affairs & Labor Refer Amended to House Committee of the Whole
8. April 28, 2026House Second Reading Laid Over Daily - No Amendments
9. April 29, 2026House Second Reading Special Order - Passed with Amendments - Committee, Floor
10. April 30, 2026House Third Reading Passed - No Amendments
11. May 1, 2026Senate Considered House Amendments - Result was to Concur - Repass
12. May 12, 2026Signed by the President of the Senate
13. May 12, 2026Signed by the Speaker of the House
14. May 12, 2026Sent to the Governor
15. June 3, 2026Governor Signed

State and local records are supplied by Plural Open (Open States), with links to original legislative sources. Coverage and update times vary. A vote passing one chamber does not mean a bill became law. State source changes are checked hourly; some detailed records may appear later because of source limits.