HB26-1210 · Bill · 2026 Regular Session · Colorado

Prohibit Surveillance Price & Wage Setting

Concerning limiting the use of intimate personal data to make inferences that impact a person's financial position.

Official status: Did Not Become Law

16 proposed amendments

Prime sponsors

Progress (from the official record)

Official summary

Official text — shown in English exactly as published by the official source. The official text controls.

Surveillance data is defined in the act as data that is obtained through observation, inference, or surveillance of consumers or workers and that is related to personal characteristics, online behaviors, or biometrics of an individual or group, band, class, or tier to which the individual belongs. The definition of 'worker' in the act excludes federal and state employees and employees of public entities. The act prohibits discrimination against a consumer or worker resulting from the use of a price or wage setting algorithm (PWSA) that uses statistical modeling, data analytics, artificial intelligence, or other data processing techniques to analyze surveillance data, the output of which is a substantial factor in: Individualized price setting used to determine the amount charged to a consumer; or Individualized wage setting used to determine the wage offered to a worker. The act specifies activities that are not individualized price or wage setting, as well as exemptions from the prohibition on price or wage setting. A person has not engaged in individualized price setting if the person can demonstrate, as described in the act, that differential prices are: Based on differences in the cost in providing a good or service to different consumers, such as delivery distance or temporal differences, such as ride or delivery time; Based on publicly disclosed eligibility criteria to all persons that meet the criteria, such as consumers purchasing in volume, or to all members of a broadly defined group of consumers, such as teachers; Afforded on equal terms to all participants in a loyalty, membership, or rewards program or are offered in response to a consumer complaint, service disruption, request for account cancellation, or similar reason; Offered pursuant to a specified needs-based discount program for reduced pricing related to income or financial need, such as hospital discounted care; Based on a subscription or other continuous agreement that includes a monthly or other recurring price that was not informed by a PWSA; or Based on a refusal to extend credit on specific terms or to enter into a financial transaction based on a consumer's data in a consumer report or data required as part of the application for the financial transaction. A person has not engaged in individualized wage setting if the person can demonstrate, as described in the act, that the person offers individualized wages based solely on data specific to an individual worker that is directly related to worker seniority or the tasks the worker was required to perform, and the person discloses to the worker before hiring, and to all workers whose wages are set in whole or in part by a PWSA, what data is considered and how the PWSA considers the data. A person that uses a PWSA shall develop and publish reasonable procedures to ensure the accuracy of all data considered by the PWSA, for workers to request and receive information about what data is collected, and to correct or challenge data considered by a PWSA. A violation of the prohibition against individualized price or wage setting is a deceptive trade practice under the 'Colorado Consumer Protection Act' and is subject to the enforcement provisions and remedies provided in that act. (Note: This summary applies to this bill as enacted.)

Status timeline

Every recorded action on HB26-1210, oldest first
DateLocationAction
02/13/2026HouseIntroduced In House - Assigned to Business Affairs & Labor
03/12/2026HouseHouse Committee on Business Affairs & Labor Refer Amended to House Committee of the Whole
03/17/2026HouseHouse Second Reading Laid Over Daily - No Amendments
03/26/2026HouseHouse Second Reading Special Order - Passed with Amendments - Committee, Floor
03/27/2026HouseHouse Third Reading Passed - No Amendments
04/01/2026SenateIntroduced In Senate - Assigned to Business, Labor, & Technology
04/21/2026SenateSenate Committee on Business, Labor, & Technology Refer Unamended to Senate Committee of the Whole
04/24/2026SenateSenate Second Reading Laid Over to 04/27/2026 - No Amendments
04/27/2026SenateSenate Second Reading Laid Over Daily - No Amendments
05/01/2026SenateSenate Second Reading Laid Over to 05/04/2026 - No Amendments
05/05/2026SenateSenate Second Reading Passed with Amendments - Floor
05/06/2026SenateSenate Third Reading Passed - No Amendments
05/07/2026HouseHouse Considered Senate Amendments - Result was to Concur - Repass
05/29/2026HouseSigned by the Speaker of the House
05/29/2026SenateSigned by the President of the Senate
05/29/2026GovernorSent to the Governor
06/02/2026GovernorGovernor Vetoed

Recorded votes

Proposed amendments (16 proposed amendments)

Amendments proposed to HB26-1210, oldest first
AmendmentCommittee / floor hearingOfferedDispositionOfficial document
L.001Committee amendment — Business Affairs & Labor (House)03/12/2026PassedView official document
L.003
Sponsor: Representatives Mabrey and Bacon
Floor amendment — Second Reading (House)03/26/2026PassedView official document
L.004
Sponsor: Representatives Mabrey and Bacon
Floor amendment — Second Reading (House)03/26/2026PassedView official document
L.007
Sponsor: Representative Richardson
Floor amendment — Second Reading (House)03/26/2026LostView official document
L.006
Sponsor: Representative Richardson
Floor amendment — Second Reading (House)03/26/2026LostView official document
L.011
Sponsor: Representative DeGraaf
Floor amendment — Second Reading (House)03/26/2026LostView official document
L.010
Sponsor: Representative DeGraaf
Floor amendment — Second Reading (House)03/26/2026LostView official document
L.008
Sponsor: Representative DeGraaf
Floor amendment — Second Reading (House)03/26/2026LostView official document
L.012
Sponsor: Representative DeGraaf
Floor amendment — Second Reading (House)03/26/2026LostView official document
L.018
Sponsor: Senator Weissman
Floor amendment — Second Reading (Senate)05/05/2026PassedView official document
L.036
Sponsor: Senator Weissman
Floor amendment — Second Reading (Senate)05/05/2026PassedView official document
L.019
Sponsor: Senator Simpson
Floor amendment — Second Reading (Senate)05/05/2026LostView official document
L.023
Sponsor: Senator Simpson
Floor amendment — Second Reading (Senate)05/05/2026LostView official document
L.020
Sponsor: Senator Simpson
Floor amendment — Second Reading (Senate)05/05/2026LostView official document
L.027
Sponsor: Senator Simpson
Floor amendment — Second Reading (Senate)05/05/2026LostView official document
L.040
Sponsor: Senator Jodeh
Floor amendment — Second Reading (Senate)05/05/2026PassedView official document

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

Full text

Official record

View HB26-1210 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

2ce9ab5bed720f385490452a248add42d67e4f4f7ac216b67606e767a6206349

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.

Computed 2026-11-06 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: Colorado General Assembly (leg.colorado.gov) · Data as of

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.