SB 51 Colorado Senate · 2026 Regular Session

Age Attestation on Computing Devices

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.)
Bill status signed all 5 stages cleared
Introduction
Jan 2026
Committee Review
Apr 2026
Senate Passage
May 2026
House Passage
May 2026
Signed into Law
Jun 2026
Introduced Jan 27, 2026 Signed Jun 3, 2026
Maddy AI version diff · 5 comparisons

What changed between versions

Rerevised Final Act · 6 edits · May 7, 2026
MODERATE
The bill transitions from a draft version to a final act, incorporating specific definitions and operational requirements for age attestation. It establishes a legal framework where operating system providers must collect minimal age data (brackets) during account setup to help apps comply with privacy laws for minors. The final version clarifies that this data is non-identifiable, restricts sharing to necessary parties, and explicitly exempts certain software types like open-source repositories and extensions.
Scope change
The scope remains focused on consumer computing devices and apps accessed through covered application stores, but the final act adds precise definitions for 'covered application' and 'covered application store' to clarify which entities must comply and which are exempt.
DEFINITION

Added detailed definitions for key terms including 'Account Holder' (must be 18+ or parent/guardian), 'Age-Bracket Data' (non-identifiable ranges), and 'Covered Application' (excluding apps that don't process personal data or open-source code).

REQUIREMENT

Added specific mandates requiring operating system providers to offer an accessible interface at account setup to collect birth date or age bracket, while allowing users 18+ to select a bracket without revealing their exact birth date.

Added strict data handling rules requiring developers and OS providers to request only the minimum necessary age information and prohibiting them from sharing age signals with third parties for unauthorized purposes.

EXEMPTIONS

Added explicit exemptions for code repositories, containerized software, and apps that run exclusively within separate host applications (like extensions or plug-ins) to prevent overreach.

TIMELINE

Added a specific effective date of July 1, 2028, for the new age attestation requirements.

ENFORCEMENT

Removed the specific civil penalty amounts ($2,500 for negligent violations and $7,500 for intentional violations) and the mechanism for assessing penalties, which were present in the draft but not carried forward to this version.

Floor votes

How they voted

This bill passed the Senate by voice vote (no roll call recorded).
Full legislative history

Actions timeline

Total actions
15
Key actions
7
Committee
2
Amendments
1
Jun 3, 2026
Signed into law
Governor Signed
executive
May 12, 2026
Lower · Passed
Signed by the Speaker of the House
lower
May 12, 2026
Upper · Passed
Signed by the President of the Senate
upper
May 1, 2026
Introduced
Senate Considered House Amendments - Result was to Concur - Repass
upper
Apr 30, 2026
Lower · Passed
House Third Reading Passed - No Amendments
lower
Apr 23, 2026
Lower · Passed
House Committee on Business Affairs & Labor Refer Amended to House Committee of the Whole
lower
Apr 6, 2026
Introduced
Introduced In House - Assigned to Business Affairs & Labor
lower
Mar 3, 2026
Upper · Passed
Senate Third Reading Passed - No Amendments
upper
Feb 24, 2026
Upper · Passed
Senate Committee on Business, Labor, & Technology Refer Amended - Consent Calendar to Senate Committee of the Whole
upper
Jan 27, 2026
Introduced
Introduced In Senate - Assigned to Business, Labor, & Technology
upper
4 primary · 3 co-sponsors

Sponsors