Law / United States / Colorado

Colorado

All 32 named instruments researched to a stage, across five of the ten areas of law we track: 26 in force, 5 not yet in force and 1 no longer in force. As of .

When each starts30 of 32 carry a date, 2 do not. Earlier is before 2016.
Before 2016: 6 instruments (6 in force) earlier 2016: 1 instrument (1 in force) 2017: 0 instruments 2018: 3 instruments (3 in force) 2019: 0 instruments 2020: 0 instruments ’20 2021: 1 instrument (1 in force) 2022: 1 instrument (1 in force) 2023: 2 instruments (2 in force) 2024: 2 instruments (2 in force) 2025: 6 instruments (6 in force) ’25 2026: 3 instruments (3 in force) 2027: 4 instruments (4 not yet in force) 2028: 1 instrument (1 not yet in force) ’28 today

in forcenot yet in forceblocked by a courtproposedno longer in force

  1. AI law 10
  2. Privacy law 14
  3. Scraping law 3
  4. Cybersecurity law 2
  5. Communications law not researched
  6. Content moderation law not researched
  7. Product and AI liability law not researched
  8. Digital accessibility law not researched
  9. Age gating law 3
  10. Reuse law

Case lawPremium data

Our analysis of Colorado law draws on 1 court ruling.

Which laws the rulings read, and each ruling, are premium data, in the Plus, Pro and Enterprise plans.

  • No current case law for Colorado AI law
  • No current case law for Colorado privacy law
  • No current case law for Colorado scraping law
  • No current case law for Colorado cybersecurity law
  • No current case law for Colorado communications law
  • No current case law for Colorado content moderation law
  • No current case law for Colorado product and AI liability law
  • No current case law for Colorado digital accessibility law
  • Age gating law: 1 court ruling
  • No current case law for Colorado reuse law

See the plansSign in

AI law10 instruments, 5 in force, 4 not yet in force, 1 no longer in force

Research summary (343 words)

Colorado's landmark Colorado AI Act (SB 24-205, 2024) never took effect.

Its operative date slipped from to under SB 25B-004 (2025 Special Session B), a federal court stayed its enforcement in April 2026 in litigation brought by xAI and joined by the U.S. Department of Justice, and before the June date arrived, the legislature repealed and re-enacted its Part 17 of Title 6 wholesale as SB 26-189 (signed ), replacing the risk-management framework with a narrower automated-decision-making-technology disclosure regime whose consumer-facing duty does not take effect until .

SB 25B-004, officially titled "Increase Transparency for Algorithmic Systems" and sometimes called the Colorado AI Sunshine Act, only extended SB 24-205's effective date and created no independent disclosure duty of its own, so it is described here only as part of SB 24-205's history, not as a standalone instrument. Separately and unaffected by any of this, Colorado's candidate election-deepfake disclosure statute, HB 24-1147, has been in force since .

A fourth instrument, HB 26-1263 (2026), Chapter 208, adds Part 17 duties for operators of conversational AI services (chatbots): age estimation, minor-specific safety and disclosure requirements, a suicide and self-harm response protocol, a ban on claiming professional credentials for the service's output, and annual reporting to the Attorney General, with its consumer-facing duties taking effect and its reporting duty .

Separately, Colorado's insurance code carries its own algorithmic-discrimination duty on insurers: SB 21-169 (2021), C.R.S. 10-3-1104.9, in effect since , bars an insurer from unfairly discriminating and, once the Commissioner of Insurance adopts implementing rules for a line of insurance, bars a discriminatory use of an external consumer data and information source (ECDIS) or an ECDIS-based algorithm or predictive model.

The Division of Insurance's Regulation 10-1-1 (3 CCR 702-10) implements that mandate with a governance, risk-management and quantitative-testing framework, first in effect for life insurers on and, as amended, extended to private passenger automobile insurers and health benefit plan insurers effective .

AI governance

SB 26-189 (2026), Automated Decision-Making Technology Act, deployer record keeping

C.R.S. 6-1-1703official enrolled act text, Colorado General Assembly

archived copyRead from a public archive copy, not the publisher directly. The publisher does not serve this page to automated readers, so a direct fetch was not an option here; how we access sources. Archived 2026. Publisher's page: https://leg.colorado.gov/bill_files/116432/download

Not yet in force. from , in 2 months It starts to bind on .

Binds private bodies.

What this law does

A deployer of a covered automated decision-making technology must retain, for not less than three years after the date of a consequential decision or for a longer period if state or federal law requires, records reasonably necessary to demonstrate compliance with Part 17 of Title 6 of the Colorado Revised Statutes. The records may include the technology's version identifiers, changelogs, and documentation of material mitigation changes. The Act takes effect on .

What it requires

AI risk obligations

HB 26-1139 (2026), Use of Artificial Intelligence in Health Care

Colo. HB 26-1139, 2026 Colo. Sess. Laws ch. 325Colorado General Assembly bill page for HB 26-1139, with the enacted bill summary and session-law record

Not yet in force. from , in 2 months It starts to bind on .

Binds private bodies.

What this law does

HB 26-1139 takes effect on as Chapter 325 of the 2026 Colorado session laws. The Governor signed it on . From that date, entities that use an AI system to conduct utilization review of health-care services, including carriers, pharmacy benefit managers, private utilization review organizations, behavioral health administrative services organizations and managed care entities, must ensure that the AI system complies with the act's requirements.

The system must make determinations based on medical or clinical history and individual clinical circumstances, must not rest solely on group data, must not be used in a discriminatory way, and must be periodically assessed for accuracy and reliability. An entity must disclose to the applicable state agency the utilization review functions for which the system will be used, the process for human oversight of adverse coverage determinations, and the process for maintaining audit information.

A carrier's denial of coverage based in whole or in part on medical necessity may not be issued solely on the output of an AI system without human review by a licensed clinician or physician or other competent regulated professional. The act also bars a carrier and a public-program payer from paying for psychotherapy services conducted directly with a client by an AI system.

What it requires

AI sector rules

Amended Regulation 10-1-1 (2025), Governance and Risk Management Framework for Insurers' Use of External Consumer Data and Information Sources, Algorithms, and Predictive Models

3 CCR 702-10, Regulation 10-1-1Code of Colorado Regulations, 3 CCR 702-10, Regulation 10-1-1, Colorado Secretary of State

In force since . Binds private bodies.

What this law does

An insurer authorized to do business in Colorado that offers individually issued life insurance, private passenger automobile insurance, or a health benefit plan, and that uses an external consumer data and information source (ECDIS), or an algorithm or predictive model that uses one, in any insurance practice, must establish a documented, risk-based governance and risk management framework, including a cross-functional governance group, designed to determine through quantitative testing whether that use results in unfair discrimination with respect to race, and to remediate any discrimination detected.

An insurer that does not use ECDIS instead files a signed officer attestation. The Division of Insurance adopted the original version of this regulation for life insurers alone effective , under the authority of C.R.S. 10-1-109 and 10-3-1104.9; this amended version, effective , extends the same framework to private passenger automobile insurers and health benefit plan insurers, with a deadline for those two lines' first compliance report.

What it requires

HB 26-1195 (2026), Psychotherapy Artificial Intelligence Restrictions

Colo. HB 26-1195, 2026 Colo. Sess. Laws ch. 358Colorado General Assembly bill page for HB 26-1195, with the enacted bill summary and session-law record

In force since . Binds private bodies.

What this law does

HB 26-1195 took effect on as Chapter 358 of the 2026 Colorado session laws. The Governor signed it on .

It prohibits a regulated psychotherapy professional from allowing an AI system to interact with clients in any form of therapeutic communication without synchronous, real-time interaction between the professional, the AI system, and the client, or from letting the system generate therapeutic recommendations or treatment plans without the professional's review and approval. A professional must inform clients of these prohibitions at initial client contact.

If a session will be recorded or transcribed through an AI system, the professional must disclose that use in advance and obtain written, informed consent.

The act also makes it an unfair or deceptive trade practice under the Colorado Consumer Protection Act for any person to use a term in the use of an AI system that implies its outputs are provided or endorsed by a regulated professional, that represents that the system provides psychotherapy services, or that suggests therapist-client confidentiality. A regulated professional who violates the act may be disciplined by the appropriate licensing board.

What it requires

SB 21-169 (2021), Insurers' Use of External Consumer Data and Information Sources, Algorithms, and Predictive Models

C.R.S. 10-3-1104.9SB 21-169, official signed act text, Colorado General Assembly

In force since . Binds private bodies.

What this law does

An insurer may not unfairly discriminate based on race, color, national or ethnic origin, religion, sex, sexual orientation, disability, gender identity, or gender expression in any insurance practice, and, once the Commissioner of Insurance adopts implementing rules for a type of insurance, may not use an external consumer data and information source (ECDIS), or an algorithm or predictive model that uses one, in a way that has that same discriminatory effect.

The duty does not reach title insurance, a surety bond, or most commercial insurance policies, though it does reach a business owners' or commercial general liability policy carrying an annual premium of ten thousand dollars or less. The Commissioner's implementing rules for a given insurance type are Division of Insurance Regulation 10-1-1 (3 CCR 702-10), held as its own instrument in this topic.

What it requires

AI transparency

HB 24-1147, Candidate Election Deepfake Disclosures

C.R.S. 1-46-103official signed act text, Colorado General Assembly

In force since . Binds public and private bodies.

What this law does

No person may distribute, publish, broadcast, or display a communication about a candidate for elective office that includes a deepfake within 60 days of a primary or 90 days of a general election, unless the communication carries a specified clear and conspicuous disclosure that it has been edited and falsely appears authentic. This binds any distributing party, not only the AI system's provider or deployer, and is unaffected by the litigation and repeal touching SB 24-205 and SB 26-189.

What it requires

HB 26-1263 (2026), Conversational AI Service Operator Requirements

C.R.S. 6-1-1708official session-law chapter text, Chapter 208 (2026), Colorado General Assembly

archived copyRead from a public archive copy, not the publisher directly. The publisher does not serve this page to automated readers, so a direct fetch was not an option here; how we access sources. Archived 2026. Publisher's page: https://leg.colorado.gov/bill_files/116772/download

In force since . Binds private bodies.

What this law does

An operator that develops and makes publicly available, or offers to a consumer, a conversational artificial intelligence service must use commercially reasonable or generally accepted methods to estimate a user's age, and must not willfully disregard clear and convincing information that an account holder or user is a minor. The act's effective date is . The age-estimation duties carry no start date later than that effective date.

Starting , if an operator knows an account holder or user is a minor, the operator must disclose that the service is artificial intelligence, withhold unpredictable-interval engagement rewards from the minor, prevent the service from producing explicit sexual content, intimate digital depictions, or statements simulating romantic companionship or emotional dependence with the minor, and give the minor and a parent or guardian tools to manage privacy and account settings.

Starting , an operator must also disclose to every user, not only minors, that the service is artificial intelligence, run a suicide and self-harm response protocol that refers a user to a crisis service provider rather than law enforcement, and not represent the service's output as coming from a licensed health-care, legal, or mental-health professional or a qualified dietitian; starting , it must report annually to the Attorney General on crisis referrals and self-harm safeguards without including user-identifying information.

Signed as Chapter 208 and added to Part 17 of Title 6 alongside SB 24-205 and SB 26-189, a violation of this duty is a deceptive trade practice under the Colorado Consumer Protection Act enforced by the Colorado Attorney General, subject to a 60-day right to cure before an enforcement action, and creates no new private right of action.

What it requires

SB 24-205 (2024), Colorado AI Act, original enactment

C.R.S. 6-1-1701 et seq., as originally enactedofficial signed act text, Colorado General Assembly

No longer in force. in force repealed Repealed. The page is kept as a record.

Binds private bodies.

What this law does

As originally enacted, this disclosure duty (6-1-1704) required a deployer or developer that made an artificial intelligence system available to interact with consumers to ensure disclosure to each consumer that they were interacting with an artificial intelligence system, unless it would be obvious to a reasonable person, and sat alongside a broader high-risk-system duty to avoid algorithmic discrimination in consequential decisions elsewhere in Part 17, outside this topic's scope.

The operative date slipped twice: first to as originally enacted, then to under SB 25B-004 (2025 Special Session B, Chapter 3), which extended the effective date of SB 24-205's requirements and added no independent disclosure duty of its own; enforcement was then stayed by a federal court on in X.AI LLC v. Weiser (a stipulated stay on joint motion of xAI and the state, not a merits ruling) after xAI sued and the United States intervened.

Before the delayed date arrived, SB 26-189 (signed ) repealed and re-enacted the same Part 17 with a successor framework, effective ; the Colorado General Assembly's own bill summary describes this action as repealing and reenacting Part 17, and multiple law firm summaries of the signed act likewise describe SB 24-205 as repealed.

Because it never reached its own operative date before being repealed, this statute was never in force at any point, and is recorded here as repealed.

What it requires

SB 26-189 (2026), Automated Decision-Making Technology Act

C.R.S. 6-1-1704official enrolled act text, Colorado General Assembly

Not yet in force. from , in 2 months It starts to bind on .

Binds private bodies.

What this law does

Prior to using a covered automated decision-making technology that materially influences a consequential decision (education, employment, housing, financial or lending services, insurance, health care, or essential government services), a deployer must provide a clear and conspicuous notice that it used or will use covered ADMT in that decision, satisfiable by a prominent public notice at points of consumer interaction.

If the ADMT produces an adverse outcome, the deployer must, within 30 days, provide a plain-language description of the decision and the technology's role, plus an explanation of the consumer's rights. Signed . The consumer disclosure duty itself takes effect . The Colorado General Assembly's own bill status page confirms the signature date.

What it requires

SB 26-189 (2026), Automated Decision-Making Technology Act, developer documentation and records

C.R.S. 6-1-1702official enrolled act text, Colorado General Assembly

archived copyRead from a public archive copy, not the publisher directly. The publisher does not serve this page to automated readers, so a direct fetch was not an option here; how we access sources. Archived 2026. Publisher's page: https://leg.colorado.gov/bill_files/116432/download

Not yet in force. from , in 2 months It starts to bind on .

Binds private bodies.

What this law does

On and after , a developer must make available to each deployer of a covered automated decision-making technology it developed a general statement of the technology's intended uses and known harmful or inappropriate uses, a description of the categories of data used to train it, its known limitations, and instructions for appropriate use, monitoring and meaningful human review.

The developer must also make available the information reasonably necessary for the deployer to comply with the deployer disclosure section, and must notify the deployer if information is withheld. A developer must give each deployer notice of material updates, intentional and substantial modifications, and changes to the intended use of, limitations for, or risk mitigation for the technology within a reasonable time.

These disclosure duties apply only to a deployer's use of a technology that was marketed, advertised, configured, contracted, sold or licensed to be used to materially influence a consequential decision.

A developer must retain, for not less than three years after the creation of a record required or created under the section, or for a longer period if state or federal law requires, records reasonably necessary to demonstrate compliance, including system version identifiers, changelogs, and documentation and notices of material updates provided to deployers. The Act takes effect on .

What it requires

Privacy law14 instruments, 14 in force

Research summary (577 words)

Colorado's comprehensive privacy regime is the Colorado Privacy Act (CPA, C.R.S. 6-1-1301 et seq., enacted by SB 21-190), in effect since , binding a controller that conducts business in or intentionally targets Colorado residents and meets a 100,000-consumer, or a 25,000-consumer-plus-sale-revenue, processing threshold.

No express government-entity exemption clause was located in the text reviewed; the reading that it binds the private sector rests on the act's business-facing definitions and its placement inside the Colorado Consumer Protection Act, not on a located carve-out. Three 2024-session amendments extend the CPA on staggered effective dates. HB 24-1058 () added biological and neural data as sensitive-data categories.

HB 24-1130 () added a dedicated biometric-identifier regime, naming voiceprint and facial map, geometry, or template explicitly, that binds a controller processing any amount of biometric data with no volume threshold, requiring pre-collection notice and consent and a written retention-and-destruction schedule.

SB 24-041 () layered a duty of care and consent-gated processing limits onto a minor's data, and kept its own 60-day cure period in force through after the CPA's general cure period sunset on . SB 25-276 (chapter 240 of the 2025 Colorado session laws) took effect on . It makes precise geolocation data sensitive data. It also bars a controller from selling a consumer's sensitive data without the consumer's consent.

The Department of Law also retains open rulemaking authority for biometric security standards under C.R.S. 6-1-1314(7).

A standalone statute, C.R.S. 6-1-716, requires a private entity to notify affected Colorado residents of a security breach within 30 days of determination, with Attorney General notice once 500 or more residents are affected and consumer-reporting-agency notice once more than 1,000 residents are affected; a separate statute, C.R.S. 24-73-103, covers a governmental entity's own breach-notification duty.

Enforcement of the CPA is exclusive to the Attorney General and district attorneys, with no private right of action anywhere in the act. Civil penalties apply under the Colorado Consumer Protection Act's general penalty provision, C.R.S. 6-1-112.

Section 6-1-715 of the Colorado Revised Statutes bars a person or entity from publicly posting an individual's social security number, printing it on an access card, or requiring its transmission over the internet without a secure connection or encryption.

Section 10-3-1104.6 of the Colorado Revised Statutes makes genetic information confidential and privileged and bars an entity from seeking, using or keeping it for nontherapeutic or underwriting purposes connected with health care or medicare supplement insurance.

Section 10-3-1104.7 of the Colorado Revised Statutes makes information derived from genetic testing confidential and privileged and bars an entity from seeking, using or keeping it for nontherapeutic or underwriting purposes connected with group disability or long-term care insurance. Article 16 of title 22 of the Colorado Revised Statutes, the Student Data Transparency and Security Act, binds school service contract providers that contract with public education entities.

Section 25-1-801 of the Colorado Revised Statutes requires a licensed health facility to provide copies of a patient's medical records to the patient on request and to a third person with a Health Insurance Portability and Accountability Act (HIPAA)-compliant authorization, valid subpoena or court order. Section 10-16-423 of the Colorado Revised Statutes requires a health maintenance organization to hold an enrollee's or applicant's health information in confidence.

Section 6-1-1314(6) of the Colorado Revised Statutes limits an employer's use of consent for the collection and processing of an employee's or prospective employee's biometric identifier to four listed purposes as a condition of employment.

Biometric privacy

HB 24-1130, Privacy of Biometric Identifiers and Data

C.R.S. sections 6-1-1303(2.2)-(2.4), 6-1-1314 (2024 Colo. Sess. Laws ch. 313)official legislature bill status page for HB 24-1130 (bill history and staff summary)

In force since . Binds private bodies.

What this law does

Amends the Colorado Privacy Act to define biometric identifier (a fingerprint, a voiceprint, a scan or record of an eye retina or iris, a facial map, facial geometry, or facial template, or another unique biological, physical, or behavioral pattern) and biometric data, and adds C.R.S. 6-1-1314, which requires any controller that controls or processes a biometric identifier, regardless of the CPA's general size thresholds, to give notice and obtain consent before collection, adopt a written retention and destruction policy, maintain a data-security-incident response protocol, and refrain from selling, leasing, or trading a biometric identifier absent consent or a listed exception.

Consumers may request the source, purpose, and third-party disclosures of their biometric data. The biometric-data definition excludes a photograph and an audio or video recording, and data generated from either, but only conditionally: the exclusion drops away the moment that data is used for identification purposes, so a voiceprint or faceprint extracted from a recording specifically to identify someone remains covered.

What it requires

Use of consent by employers: biometric identifiers of employees and prospective employees

C.R.S. section 6-1-1314(6) (HB 24-1130, 2024 Colo. Sess. Laws ch. 313)Official codified statute text, Colorado Revised Statutes (Office of Legislative Legal Services, leg.colorado.gov)

In force since . Binds private bodies.

What this law does

Under section 6-1-1314(6)(a), an employer may require as a condition of employment that an employee or prospective employee consent to the employer's collection and processing of the person's biometric identifier only to permit access to secure physical locations and secure electronic hardware and software applications, to record the commencement and conclusion of the full work day, to improve or monitor workplace safety or security, or to improve or monitor public safety in an emergency or crisis.

Under section 6-1-1314(6)(a)(I), an employer may not obtain consent to retain biometric data used for current employee location tracking or for tracking how much time the employee spends using a hardware or software application.

Under section 6-1-1314(6)(b), an employer and its processor may collect and process an employee's or prospective employee's biometric identifier for other uses only with the person's consent, and the employer may not require that consent as a condition of employment or retaliate against a person who does not consent.

Section 6-1-1314(6)(d) does not restrict an employer's or its processor's collection and processing of a biometric identifier for uses aligned with the reasonable expectations of an employee based on the job description or role, or of a prospective employee based on a reasonable background check, an application or identification requirements.

Section 6-1-1311(1)(a) gives the attorney general and the district attorneys exclusive authority to enforce part 13 of article 1 of title 6, and section 6-1-1311(1)(b) provides that part 13 is not the basis for a private right of action. Section 6-1-1311(1)(c) makes a violation of part 13 a deceptive trade practice for enforcement by the attorney general or a district attorney.

Section 6-1-112(1)(a) makes a person who violates any provision of article 1 of title 6 liable to a civil penalty of not more than $20,000 for each violation, and each consumer or transaction involved is a separate violation. Under section 6-1-1314(6)(a)(II), an employer may require consent to collect the biometric identifier to record the commencement and conclusion of the employee's full work day, including meal breaks and rest breaks in excess of thirty minutes.

House Bill 24-1130 added section 6-1-1314 to the Colorado Privacy Act, effective , and applies to the collection, retention, processing and use of biometric identifiers and biometric data on and after that date.

What it requires

Breach notification

C.R.S. 6-1-716, Notification of Security Breach

C.R.S. section 6-1-716Colorado Attorney General official data-protection-laws resource page

In force since . Binds private bodies.

What this law does

Requires a person or commercial entity that maintains computerized personal identifying information of Colorado residents to notify affected residents of a security breach in the most expedient time possible, without unreasonable delay, and within 30 days of determining a breach occurred, subject to a delay while a law-enforcement investigation is pending.

A breach affecting 500 or more residents must also be reported to the Colorado Attorney General; one affecting more than 1,000 residents must also be reported to nationwide consumer reporting agencies. A separate statute, C.R.S. 24-73-103, covers a governmental entity's own breach-notification duty. HB 24-1130 cross-references this section for the biometric-specific breach-response protocol a controller's written policy must include.

What it requires

Comprehensive regime

Colorado Privacy Act Rules (Attorney General)

4 CCR 904-3Code of Colorado Regulations, 4 CCR 904-3, Colorado Secretary of State

In force since . Binds private bodies.

What this law does

The Colorado Privacy Act Rules, 4 CCR 904-3, are the Attorney General's implementation and operational guidelines for the Colorado Privacy Act. The rules took effect on , with amendments effective and, for Rules 2.02, 6.13, 6.14 and 7.03 B.3, . A controller that receives an opt-out request through a Universal Opt-Out Mechanism must treat it as a valid request to opt out of targeted advertising, the sale of personal data, or both.

A controller must keep records of consumer data rights requests for at least 24 months. A controller must give any required biometric identifier notice at or before the initial collection or processing of a biometric identifier. A controller must conduct and document a data protection assessment before it starts a processing activity that presents a heightened risk of harm to a consumer.

A request to opt out of profiling in furtherance of decisions that produce legal or similarly significant effects must be honored where the profiling rests on solely automated processing or human reviewed automated processing. Personal data must be processed with reasonable and appropriate administrative, technical, organizational and physical safeguards.

An employer may require an employee or prospective employee to consent to biometric collection and processing as a condition of employment only as the Colorado Privacy Act permits.

What it requires

SB 21-190, Colorado Privacy Act (CPA)

C.R.S. sections 6-1-1301 et seq.Official session law text (2021 Colo. Sess. Laws ch. 483, enrolled SB 21-190) and the Colorado General Assembly's official bill page

In force since . Binds private bodies.

What this law does

Colorado's omnibus data-privacy statute requires a controller that conducts business in or intentionally targets Colorado residents, and meets a 100,000-consumer or a 25,000-consumer-plus-sale-revenue threshold, to give consumers notice, minimize collection, obtain affirmative opt-in consent before processing sensitive data or resuming processing after an opt-out, and honor rights to access, correct, delete, and port personal data.

Processors must follow controller instructions and assist with compliance, and a controller must complete a data protection assessment before processing that presents a heightened risk of harm. SB 25-276 (chapter 240 of the 2025 Colorado session laws) took effect on . It defines precise geolocation data as information derived from technology that accurately identifies the present or past location of a device that links or is linkable to an individual within a radius of 1,850 feet.

It makes precise geolocation data sensitive data. It also bars a controller from selling a consumer's sensitive data without the consumer's consent.

What it requires

Data subject rights

Patient records in the custody of health-care facilities and individual providers: inspection and copies

C.R.S. sections 25-1-801 and 25-1-802Official codified statute text, Colorado Revised Statutes (Office of Legislative Legal Services, leg.colorado.gov)

In force since . Binds public and private bodies.

What this law does

Section 25-1-801 reaches every patient record in the custody of a health facility licensed or certified under section 25-1.5-103(1) or article 3 of title 25, or of an entity regulated under title 10 that provides health-care services.

Under sections 25-1-801 and 25-1-802, such a record must be available for inspection to the patient or the patient's personal representative through the attending health-care provider at reasonable times and on reasonable notice, except records withheld under 45 CFR 164.524(a).

Under section 25-1-801, a health-care facility must provide copies of a patient's medical records to the patient or the patient's personal representative on request and payment of the fee a covered entity may impose under Health Insurance Portability and Accountability Act (HIPAA), or to a third person who submits a HIPAA-compliant authorization, valid subpoena or court order.

Under section 25-1-801, a health-care facility must deliver the medical records in electronic format if the person requests it, the originals are stored in electronic format and the records are readily producible that way. Under section 25-1-801, a health-care facility may not charge a fee for the inspection of medical records.

Section 25-1-802 reaches every patient record in the custody of a podiatrist, chiropractor, dentist, doctor of medicine or osteopathy, nurse, optometrist, physical therapist or other provider it lists who is required to be licensed under title 12, or of a person practicing psychotherapy under article 245 of title 12.

Under section 25-1-802, a health-care provider must provide the medical records in electronic format if the person requests it, the originals are stored in electronic format and the records are readily producible that way. Under section 25-1-802, a health-care provider may not charge a fee for the inspection of medical records.

Section 25-1-801 does not require a person responsible for the diagnosis or treatment of sexually transmitted infections, a substance use disorder or drug use in the case of minors to release those records to a parent, guardian or other person than the minor or the minor's designated representative. House Bill 24-1360 (chapter 324 of the 2024 session laws) amended section 25-1-801(5)(c)(II)(A), effective . Sections 25-1-801 and 25-1-802 were added in 1976 as part 8 of article 1 of title 25 and took effect on .

What it requires

Privacy of Consumer Financial and Health Information: insurance licensees' notice, opt-out and authorization duties

3 CCR 702-6, Regulation 6-4-1Official text of 3 CCR 702-6, Regulation 6-4-1, Code of Colorado Regulations, Colorado Secretary of State (sos.state.co.us)

In force since . Binds private bodies.

What this law does

The regulation governs the treatment of nonpublic personal health information and nonpublic personal financial information about individuals by all licensees of the Colorado Division of Insurance.

A licensee must provide a clear and conspicuous initial notice that accurately reflects its privacy policies and practices to a customer not later than when the licensee establishes a customer relationship, and to a consumer before the licensee discloses any nonpublic personal financial information about the consumer to any nonaffiliated third party, other than as Sections 16 and 17 authorize.

A licensee must provide a clear and conspicuous notice to customers that accurately reflects its privacy policies and practices not less than annually during the continuation of the customer relationship.

A licensee may not, directly or through any affiliate, disclose any nonpublic personal financial information about a consumer to a nonaffiliated third party unless it has provided the consumer an initial notice and an opt out notice, has given the consumer a reasonable opportunity to opt out, and the consumer does not opt out.

A licensee shall not disclose nonpublic personal health information about a consumer or customer unless an authorization is obtained from the consumer or customer, and an authorization may not remain valid for more than twenty-four months.

A licensee shall not unfairly discriminate against a consumer or customer because that person has opted out from the disclosure of nonpublic personal financial information or has not granted authorization for the disclosure of nonpublic personal health information. The regulation does not apply to information about companies or about individuals who obtain products or services for business, commercial or agricultural purposes. The regulation is effective .

What it requires

Sensitive categories

Confidentiality of enrollee and applicant health information held by a health maintenance organization

C.R.S. section 10-16-423Official codified statute text, Colorado Revised Statutes (Office of Legislative Legal Services, leg.colorado.gov)

In force. Binds private bodies.

What this law does

Under section 10-16-423, a health maintenance organization must hold in confidence any data or information about the diagnosis, treatment or health of an enrollee or applicant that it obtains from that person or from a provider.

Under section 10-16-423, a health maintenance organization may not disclose that information to any person except as necessary to carry out the insurance code provisions on health maintenance organizations, on the express consent of the enrollee or applicant, under a statute or court order, in a claim or litigation between that person and the organization, or as state or federal law otherwise requires or permits.

Under section 10-16-423, a health maintenance organization may claim any statutory privilege against disclosure that the provider who furnished the information is entitled to claim. Sections 10-3-1107 and 10-3-1108 let the commissioner of insurance hold a hearing when the commissioner has reason to believe a person has violated any other provision of title 10, and order a monetary penalty of not more than $3,000 for each act or violation, up to $30,000 in the aggregate.

Section 10-16-423 was reenacted with article 16 of title 10 in 1992 and amended in 2003. No day on which the section came into force has been located.

What it requires

Confidentiality of social security numbers

C.R.S. section 6-1-715Official codified statute text, Colorado Revised Statutes (Office of Legislative Legal Services, leg.colorado.gov)

In force since . Binds public and private bodies.

What this law does

Under section 6-1-715 of the Colorado Revised Statutes, a person or entity may not publicly post or publicly display an individual's social security number in any manner, print it on a card the individual needs to access products or services, or require the individual to transmit it over the internet unless the connection is secure or the number is encrypted.

Under section 6-1-715 of the Colorado Revised Statutes, a person or entity may not require an individual to use a social security number to access an internet website unless a password, unique personal identification number or other authentication device is also required.

Under section 6-1-715 of the Colorado Revised Statutes, a person or entity may not print an individual's social security number on materials mailed to the individual unless state or federal law requires, permits or authorizes it.

Under section 6-1-715 of the Colorado Revised Statutes, a person or entity that used a social security number before in a manner subsection (1) bars may continue that use only if the use is continuous, and subsection (1) applies again if the use stops for any reason. Under section 6-1-715 of the Colorado Revised Statutes, a person or entity continuing such a use must also give the individual an annual disclosure that the individual has the right to stop it.

Under section 6-1-715 of the Colorado Revised Statutes, a person or entity continuing such a use must implement a written request to stop the use within 30 days after receipt, may not charge a fee for doing so, and may not deny services because the individual makes the request. Section 6-1-715 does not prevent the collection, use or release of a social security number as required, permitted or authorized by state or federal law, or its use for internal verification or administrative purposes.

Section 6-1-715 does not apply to documents or records that are recorded or required to be open to the public under the constitution or laws of the state, or to an entity subject to the federal Health Insurance Portability and Accountability Act of 1996. Section 6-1-103 of the Colorado Revised Statutes makes the attorney general and the district attorneys concurrently responsible for enforcing article 1 of title 6.

Section 6-1-112(1)(a) of the Colorado Revised Statutes makes a person who violates any provision of article 1 of title 6 liable to a civil penalty of not more than $20,000 for each violation, and each consumer or transaction involved is a separate violation. Section 6-1-715 took effect on .

What it requires

Genetic information in health-care insurance: confidentiality, underwriting limits and required tests

C.R.S. section 10-3-1104.6 (HB 09-1338, 2009 Colo. Sess. Laws ch. 353, section 2)Official session law text, Colorado General Assembly (leg.colorado.gov)

In force since . Binds private bodies.

What this law does

Section 10-3-1104.6 binds an entity, meaning any sickness and accident insurance company, health maintenance organization, nonprofit hospital, medical-surgical and health service corporation, or other entity that provides health care insurance or medicare supplement insurance coverage and is subject to the jurisdiction of the commissioner of insurance.

Under section 10-3-1104.6, genetic information is confidential and privileged, and a release for purposes other than diagnosis, treatment or therapy that identifies the person tested with the test results requires specific written consent by that person or the person's parent or guardian.

Under section 10-3-1104.6, an entity that receives genetic information may not seek, use or keep it for any nontherapeutic purpose or for any underwriting purpose connected with health care insurance or medicare supplement insurance coverage. Under section 10-3-1104.6, an entity may not request or require an individual or a family member to undergo a genetic test unless state or federal law authorizes it.

A violation of section 10-3-1104.6 is an unfair practice under section 10-3-1104(1) of the Colorado Revised Statutes and is subject to the commissioner's powers in sections 10-3-1106 to 10-3-1113. Section 10-3-1108(1)(a) lets the commissioner, after a hearing, order a monetary penalty of not more than $3,000 for each act or violation, up to $30,000 in the aggregate, and for an insurer that knew or should have known of the violation not more than $30,000 for each act, up to $750,000 annually.

Under section 10-3-1104.6, an individual injured by an entity's violation may recover equitable relief and the greater of actual damages or $10,000 per violation. Under section 10-3-1104.6, the prevailing party in an action under the section may recover costs and reasonable attorney fees. House Bill 09-1338, which added section 10-3-1104.6, takes effect and applies to policies and contracts issued, delivered, renewed or reinstated on or after that date.

What it requires

Genetic testing information in group disability, long-term care, life and individual disability insurance

C.R.S. section 10-3-1104.7Official codified statute text, Colorado Revised Statutes (Office of Legislative Legal Services, leg.colorado.gov)

In force since . Binds private bodies.

What this law does

Section 10-3-1104.7 binds an entity, meaning any entity that provides group disability insurance or long-term care insurance coverage and is subject to the jurisdiction of the commissioner of insurance.

Under section 10-3-1104.7 of the Colorado Revised Statutes, information derived from genetic testing is confidential and privileged, and a release for purposes other than diagnosis, treatment or therapy that identifies the person tested with the test results requires that person's specific written consent.

Under section 10-3-1104.7 of the Colorado Revised Statutes, an entity that receives information derived from genetic testing may not seek, use or keep it for any nontherapeutic purpose or for any underwriting purpose connected with group disability insurance or long-term care insurance coverage.

Under section 10-3-1104.7 of the Colorado Revised Statutes, for life insurance or individual disability insurance the only requirements on an insurer are that it not require or perform a genetic test without the specific, written, informed consent of the subject of the test, and that it keep the results privileged and confidential.

A violation of section 10-3-1104.7 is an unfair practice under section 10-3-1104(1) of the Colorado Revised Statutes and is subject to the commissioner's powers in sections 10-3-1106 to 10-3-1113. Section 10-3-1108(1)(a) lets the commissioner, after a hearing, order a monetary penalty of not more than $3,000 for each act or violation, up to $30,000 in the aggregate, and for an insurer that knew or should have known of the violation not more than $30,000 for each act, up to $750,000 annually.

Under section 10-3-1104.7 of the Colorado Revised Statutes, an individual injured by an entity's violation may recover equitable relief and the greater of actual damages or $10,000 per violation. Section 10-3-1104.7 was amended in 2002, with subsection (10) effective , and in 2009 by House Bill 09-1338, which amended subsections (1)(d), (2)(a), (3)(b) and (12)(a), effective , so the current entity scope and the underwriting bar in subsection (3)(b) date from 2009. Section 10-3-1104.7 was added in 1994 and took effect on .

What it requires

HB 24-1058, Protect Privacy of Biological Data

C.R.S. sections 6-1-1303(2.5), 6-1-1303(16.7), 6-1-1303(24)(b)-(d) (2024 Colo. Sess. Laws ch. 68)Colorado General Assembly official bill page for HB24-1058

In force since . Binds private bodies.

What this law does

Amends the Colorado Privacy Act's sensitive-data definition to add biological data (data from technological processing, measurement, or analysis of an individual's biological, genetic, biochemical, physiological, or neural properties, used or intended for identification) and neural data (information generated by measuring central or peripheral nervous system activity, processed by or with a device).

Extends the CPA's opt-in consent duty for sensitive data to both categories, the first such extension to neural data in a US comprehensive privacy statute.

What it requires

SB 24-041, Protecting Minors' Online Data

C.R.S. sections 6-1-1305.5, 6-1-1308.5, 6-1-1309.5, 6-1-1311(1)(d)(II) (2024 Colo. Sess. Laws ch. 296)Official enrolled act text, 2024 Colo. Sess. Laws ch. 296 (SB 24-041), and the Colorado General Assembly's official bill page

In force since . Binds private bodies.

What this law does

Amends the Colorado Privacy Act to add a duty of care: a controller that offers an online service, product, or feature to a consumer it actually knows or willfully disregards is a minor must use reasonable care to avoid a heightened risk of harm to that minor, and must complete a data protection assessment where that risk exists.

Absent opt-in consent (from the minor, or a parent or guardian for a minor under 13), the controller may not process a minor's personal data for targeted advertising, sale, or profiling with legal or similarly significant effects, use a system design feature meant to significantly increase, sustain, or extend a minor's use of the service, or collect a minor's precise geolocation data beyond what is necessary to provide the service.

The minors' provisions keep their own 60-day cure notice requirement in force through , after the CPA's general cure period sunset on .

What it requires

Student Data Transparency and Security Act: school service contract providers

C.R.S. sections 22-16-101 to 22-16-112 (HB 16-1423, 2016 Colo. Sess. Laws ch. 355)Official session law text, Colorado General Assembly (leg.colorado.gov)

In force since . Binds public and private bodies.

What this law does

Under the Student Data Transparency and Security Act, a school service is an internet website, online service, online application or mobile application that is designed and marketed primarily for use in a preschool, elementary school or secondary school, is used at the direction of teachers or other employees of a local education provider, and collects, maintains or uses student personally identifiable information.

Under the Student Data Transparency and Security Act, a school service contract provider must give each public education entity it contracts with clear, layperson information on the data elements of student personally identifiable information it collects, the learning purpose of the collection, and how the information is used and shared.

Under the Student Data Transparency and Security Act, on discovering a misuse or unauthorized release of student personally identifiable information, the provider must notify the contracting public education entity as soon as possible.

Under the Student Data Transparency and Security Act, a school service contract provider may collect, use and share student personally identifiable information only for the purposes the contract authorizes or with the consent of the student or the student's parent.

Under the Student Data Transparency and Security Act, a school service contract provider may not sell student personally identifiable information, except in an acquisition of the provider where the successor stays bound by the article.

Under the Student Data Transparency and Security Act, a school service contract provider may not use or share student personally identifiable information for targeted advertising to students, or use it to create a personal profile of a student other than for supporting purposes the contracting entity authorizes or with consent.

Under the Student Data Transparency and Security Act, a school service contract provider must maintain a comprehensive information security program reasonably designed to protect the security, privacy, confidentiality and integrity of student personally identifiable information.

Under the Student Data Transparency and Security Act, after a contract ends the provider must destroy all student personally identifiable information collected, generated or inferred under it, within the period the contract specifies, and notify the public education entity of the date.

Under the Student Data Transparency and Security Act, a local education provider may not enter into or renew a contract with a school service contract provider that refuses the terms requiring compliance with sections 22-16-108 to 22-16-110, or that has substantially failed to comply with them.

Under the Student Data Transparency and Security Act, if a student's parent finds that a local education provider does not comply with the article, the parent may submit a complaint to the provider's governing board under its complaint policy. The Student Data Transparency and Security Act takes effect on the day following the ninety-day period after final adjournment of the General Assembly, which it gives as if adjournment sine die is on .

What it requires

Scraping law3 instruments, 3 in force

Research summary (915 words)

Colorado diverges from federal scraping law in computer-crime law and in personal-data law. Its cybercrime statute makes it a class 2 misdemeanor to knowingly access a computer, computer network or computer system without authorization, to exceed authorized access, or to use one without authorization or in excess of authorized access (C.R.S. § 18-5.5-102(1)(a), (3)(b)).

The statute defines its own terms where the federal statute leaves authorization undefined: "authorization" is the express consent of a person, which may include an employee's job description, and "exceed authorized access" means to access a computer with authorization and use that access to obtain or alter information the person is not entitled to obtain or alter (C.R.S. § 18-5.5-101(1), (6.7)).

Colorado therefore tests authorization by the owner's consent and requires that consent to be express, and it has no clause treating access to an open system as consent. The Colorado Court of Appeals applied these definitions in People v. Stotz, 2016 COA 16, holding that the knowledge element of § 18-5.5-102(1)(e) reaches the lack of authorization, and that employees who were allowed to use company laptops exceeded their authorized access by deleting files they were not authorized to delete.

In People v. Galang, 2016 COA 68, the court observed that paragraph (1)(a) does not require any resulting injury. No Colorado statute or decision says whether an operator that serves a page to anyone has given the express consent the definition requires, so whether reading a public page without a login is access without authorization is open, as is whether a robots.txt directive or a cease-and-desist letter changes the answer.

Because the knowledge requirement applies to every element of the offence (C.R.S. § 18-1-503(4)), the prosecution must prove the reader knew it lacked express consent, but that does not settle the open-page question: a reader of an open page knows the facts, and what is open is whether serving a page to everyone amounts to express consent.

Subsection (1)(g) names circumvention of technological measures only for software that defeats event-ticket purchase limits, and subsection (5), added in 2022, lets an individual authorize an agent to access and process the individual's own personal data, while the agent remains liable under unfair competition law, the federal Computer Fraud and Abuse Act and the rest of the section. In Vernon v. Qwest Communications International, Inc., 857 F. Supp.

2d 1135 (D. Colo. 2012), an order of a magistrate judge that the district judge affirmed over the plaintiffs' objection, 925 F. Supp. 2d 1185 (D. Colo. 2013), a federal court applying Colorado contract law asked of clickwrap and browsewrap terms alike whether the consumer had reasonable notice, actual or constructive, of the terms and manifested assent to them, and held customers bound who clicked to accept an agreement whose full text sat on a linked page and who kept using the service.

Terms accepted at signup therefore bind, and terms shown only by a link bind where the visitor had notice of them. No Colorado decision applies either rule to a crawler, and none applies the Colorado Consumer Protection Act's general prohibition of unfair or deceptive practices to scraping.

Colorado's Supreme Court defines trespass to chattels as the intentional interference with the possession, or physical condition, of a chattel in the possession of another, without justification, and looks to the Restatement of Torts § 218 for the conditions of liability (Mountain States Telephone & Telegraph Co. v. Horn Tower Construction Co., 147 Colo. 166, 363 P.2d 175 (1961)).

No Colorado appellate decision applies the tort to a website or server, so what impairment a claim over server load must show is open.

The Colorado Privacy Act's publicly-available-information exemption has only two prongs, both keyed to a government record or the consumer's own act, with no third widely-distributed-media catch-all and no prong for a third party's unrestricted disclosure; personal data a scraper pulls from a source that is neither a government record nor the consumer's own disclosure, such as an aggregator or people-search broker, falls outside the exemption.

A 2024 amendment separately defines biometric data (excluding a bare photo, video, or audio recording unless used for identification) and the distinct term biometric identifier (the underlying raw category, such as a fingerprint or facial geometry); processing a scraped photo or voice clip into an identification template converts it into sensitive data requiring opt-in consent. No Colorado statute in force today governs AI training data.

SB 26-189, signed , repeals and reenacts Part 17 of Title 6, which SB 24-205 (2024) created, as a regime for automated decision-making technology used in consequential decisions, and, apart from its rulemaking provisions, takes effect on , applying to consequential decisions made on or after that date.

From then it requires a developer of such technology to make available to each deployer a description of the categories of data, including personal data, used to train it, to the extent known (C.R.S. § 6-1-1702(1)(b)).

That duty is one of five items of developer documentation in an act about automated decisions, runs to deployers rather than the public, and covers only technology marketed for consequential decisions, but its subject is the data used to train that technology, and it binds from .

Copyright and text and data mining are governed by federal law alone, including the unsettled question whether commercial mining is fair use, and Colorado adds no mining exception or opt-out and no database right. No Colorado statute or decision gives robots.txt legal weight of its own.

Computer misuse

Colorado Cybercrime statute (unauthorized access, defined by express consent)

C.R.S. § 18-5.5-102official text, Colorado Revised Statutes 2024, Title 18, article 5.5, Office of Legislative Legal Services (leg.colorado.gov)

In force since . Binds public and private bodies.

What this law does

Subsection (1)(a) makes it a cybercrime for a person to knowingly access a computer, computer network, or computer system without authorization, exceed authorized access, or use one without authorization or in excess of authorized access, and subsection (3)(b) makes that offense a class 2 misdemeanor.

Subsection (1)(e) separately covers altering, damaging, or interrupting a computer or its data without authorization or in excess of authorized access, and subsection (1)(g) covers software that runs automated tasks over the internet to circumvent or disable electronic queues, waiting periods, or other technological measures intended to limit the number of event tickets one person may buy.

Subsection (5) provides that an individual may authorize an agent to access and process, on the individual's behalf, personal data or other information held on a computer that is otherwise accessible to the individual, and that an authorized agent remains liable for unauthorized activity under applicable unfair competition laws, the federal Computer Fraud and Abuse Act, and the other provisions of the section.

What it requires

Personal data

Colorado Privacy Act, publicly-available-information exemption and biometric data (as amended by HB 24-1130)

C.R.S. §§ 6-1-1301 et seq., 6-1-1303(2.2), (2.4), (17), (24)official signed act PDFs, Colorado General Assembly (content.leg.colorado.gov and leg.colorado.gov)

In force since . Binds private bodies.

What this law does

Section 6-1-1303(17) excludes publicly available information from personal data, defined with only two prongs: information lawfully made available from a federal, state, or local government record, and information the controller has a reasonable basis to believe the consumer has lawfully made available to the general public.

The definition has no widely-distributed-media catch-all and no prong for information a third party disclosed without restricting the audience, so personal data a scraper pulls from a source that is neither a government record nor the data subject's own post, such as an aggregator or people-search broker, falls outside the exemption and inside the Act's reach for a qualifying collector.

HB 24-1130 (2024), effective , added Section 6-1-1303(2.2), defining biometric data as one or more biometric identifiers used for identification purposes and excluding a bare digital or physical photograph, an audio or video recording, or data generated from one, unless used for identification; and (2.4), a separate term, biometric identifier, meaning data generated by measuring a person's unique biological, physical, or behavioral characteristics, such as a fingerprint, voiceprint, retina or iris scan, or facial geometry.

Biometric or genetic data processed to uniquely identify an individual is sensitive data under Section 6-1-1303(24)(b), triggering opt-in consent; scraping a raw photo or voice clip is not itself scraping biometric data, but processing it into an identification template is.

What it requires

Unfair competition

Colorado Consumer Protection Act, unfair or deceptive trade practices

C.R.S. § 6-1-105(1)(rrr)official text, Colorado Revised Statutes, Office of Legislative Legal Services (leg.colorado.gov)

In force since . Binds private bodies.

What this law does

Section 6-1-105 lists specific deceptive trade practices that a person commits in the course of the person's business, vocation, or occupation, and paragraph (1)(rrr) reaches a person who either knowingly or recklessly engages in any unfair, unconscionable, deceptive, deliberately misleading, false, or fraudulent act or practice. Paragraph (1)(rrr) is a 2022 addition: HB 22-1287 repealed the former paragraph (1)(kkk) and added the current (1)(rrr) in its place.

What it requires

Cybersecurity law2 instruments, 2 in force

Research summary (554 words)

Colorado's security posture rests on two enacted state statutes added and amended together by HB 18-1128 (2018 Colo. Sess. Laws ch. 266, signed , effective ): C.R.S. 6-1-713.5, requiring a covered entity that maintains, owns, or licenses the personal identifying information of a Colorado resident to implement and maintain reasonable security procedures and practices appropriate to the nature of that information and the nature and size of the business, and its disposal-of-documents sibling, C.R.S. 6-1-713, requiring a written policy to destroy or dispose of paper and electronic documents containing personal identifying information by shredding, erasing, or otherwise rendering it unreadable once no longer needed.

Both duties bind only a private person or commercial entity; a governmental entity's parallel duties sit at C.R.S. 24-73-102 (protection) and 24-73-103 (breach notice), outside this profile's private-sector scope.

No enacted Colorado statute was located that sets security requirements a connected device or software product must meet before or after it reaches the market, comparable to California's or Oregon's connected-device statutes; a search for a Colorado IoT or product-security bill returned only the state's general data-protection statutes, so this is treated as a researched absence rather than a gap in coverage.

No Colorado statute or regulation setting a sector-specific cyber-resilience regime for a software or technology provider, comparable to New York's 23 NYCRR Part 500, was located; the Colorado Division of Insurance may separately regulate insurer cybersecurity, but no citable text was located to support a row.

The Colorado Privacy Act carries its own security-of-processing clause, C.R.S. 6-1-1308(5)'s duty of care, requiring a controller to take reasonable measures to secure personal data during storage and use from unauthorized acquisition, appropriate to the volume, scope, and nature of the personal data and the nature of the business; because that duty is a section of Colorado's comprehensive data-protection act rather than a standalone security statute, it is this jurisdiction's privacy row, not a second row here.

Colorado's breach-notification duty, C.R.S. 6-1-716, is likewise already this jurisdiction's privacy row: a person or commercial entity that experiences unauthorized acquisition of unencrypted computerized personal identifying information must notify affected Colorado residents within 30 days of determination, the Attorney General once 500 or more residents are affected, and nationwide consumer reporting agencies once more than 1,000 are affected.

Enforcement of both security-topic statutes runs through C.R.S. 6-1-716(4), which lets the Attorney General bring an action in law or equity to address a violation of section 6-1-716, 6-1-713, or 6-1-713.5, either to compel compliance or to recover direct economic damages, and states that this route is not exclusive of other applicable law.

Because 6-1-713 and 6-1-713.5 sit in part 7 of the Colorado Consumer Protection Act, a violation of either is also a deceptive trade practice under C.R.S. 6-1-105(1)(x) (violating part 7 of the article), which reaches the article's general civil penalty of up to $20,000 per violation under C.R.S. 6-1-112(1)(a) (up to $50,000 per violation against an elderly person), enforced by the Attorney General or a district attorney, and a private right of action under C.R.S. 6-1-113 for actual damages (with prejudgment interest), a $500 statutory minimum, treble damages on clear and convincing evidence of bad faith, and attorney fees.

This is a broader private remedy than New York's SHIELD Act safeguards duty, which creates no private right of action at all.

Security baseline statutes

Disposal of personal identifying information, written policy duty

C.R.S. 6-1-713 (amended by HB 18-1128, 2018 Colo. Sess. Laws ch. 266, section 1)Colorado Revised Statutes 2024, Title 6, published by the Office of Legislative Legal Services of the Colorado General Assembly

In force since . Binds private bodies.

What this law does

A covered entity that maintains paper or electronic documents containing personal identifying information during the course of business must develop a written policy for the destruction or proper disposal of those documents. Once the documents are no longer needed, the covered entity must destroy or arrange for their destruction by shredding, erasing, or otherwise modifying the personal identifying information to make it unreadable or indecipherable through any means.

"Covered entity" and "personal identifying information" carry the same definitions this section shares with the reasonable-security-procedures duty at C.R.S. 6-1-713.5, and a covered entity already regulated by state or federal law and following that regulator's own disposal procedures is deemed compliant.

Unless an entity specifically contracts with a recycler or disposal firm for destruction, the recycler or disposal firm has no duty to verify that the documents it receives were properly destroyed.

What it requires

Protection of personal identifying information, reasonable security procedures duty

C.R.S. 6-1-713.5 (added by HB 18-1128, 2018 Colo. Sess. Laws ch. 266, section 2)Colorado Revised Statutes 2024, Title 6, published by the Office of Legislative Legal Services of the Colorado General Assembly

In force since . Binds private bodies.

What this law does

A covered entity, a person that maintains, owns, or licenses personal identifying information of a Colorado resident in the course of its business, vocation, or occupation, must implement and maintain reasonable security procedures and practices, appropriate to the nature of the information and the nature and size of the business, to protect personal identifying information from unauthorized access, use, modification, disclosure, or destruction.

Personal identifying information is defined narrowly: a Social Security number, a personal identification number, a password or pass code, a state driver's license or identification card number, a government passport number, biometric data, an employer, student, or military identification number, or a financial transaction device.

Where a covered entity discloses that information to a third-party service provider, it must require the provider to implement and maintain its own reasonable security procedures, unless the covered entity retains primary responsibility and implements technical controls that protect the information. A covered entity already regulated by state or federal law and following that regulator's own data-security procedures is deemed compliant.

This duty binds a private person or commercial entity; a governmental entity's parallel duty sits at C.R.S. 24-73-102, outside this profile's private-sector scope.

What it requires

Age gating law3 instruments, 2 in force, 1 not yet in force

Research summary (187 words)

Colorado has enacted laws in three of the four age-gating families but has not passed a social media minor access or adult content age verification statute. Senate Bill 24-041 amended the Colorado Privacy Act, effective , to impose a duty of care, data protection assessments, and consent requirements before minors' data is used for targeted advertising, sale, profiling, or engagement extending design features.

House Bill 24-1136 required social media platforms to show pop-up warnings to users under 18 after an hour of daily use and at night starting , but a federal court preliminarily enjoined it on First Amendment grounds in November 2025. Senate Bill 26-051, the Age Attestation on Computing Devices Act, requires operating system providers to collect a birth date, age, or age bracket at device setup and share an age signal with app developers, effective .

Several 2025 and 2026 proposals on adult content age verification (SB 25-201), social media transparency and age verification (SB 24-158), and youth privacy design requirements (HB 25-1287, HB 26-1148) all failed to advance past committee or died when their legislative sessions ended.

Age-appropriate design code

SB 24-041 (2024), Privacy Protections for Children's Online Data

Colo. Rev. Stat. §§ 6-1-1305.5, 6-1-1308.5, 6-1-1309.5 (amending the Colorado Privacy Act)official signed act text, Colorado General Assembly

In force since . Binds private bodies.

What this law does

Requires a controller offering an online service, product, or feature to a consumer it actually knows or willfully disregards is a minor (under 18) to use reasonable care to avoid a heightened risk of harm to minors and to conduct data protection assessments.

Without consent (the minor's, or a parent's for a child under 13), the controller may not process a minor's data for targeted advertising, sale, or significant profiling, use a system design feature to significantly increase, sustain, or extend the minor's use, or collect precise geolocation except as specified. Signed .

What it requires

App store age verification (AV)

SB 26-051 (2026), Age Attestation on Computing Devices Act

Colo. Rev. Stat. §§ 6-30-101 to 6-30-105 (2026 Colo. Sess. Laws ch. 343)official session law chapter text, Colorado General Assembly

Not yet in force. from , in 1.7 years It starts to bind on .

Binds private bodies.

What this law does

Requires operating system providers and covered application stores to let an account holder indicate a birth date, age, or age bracket at device setup and to share a real time age signal (under 13, 13 to under 16, 16 to under 18, or 18 and older) with application developers, who must treat the signal as the primary indicator of a user's age range unless they have clear and convincing information otherwise. Signed ; codified as article 30 of title 6 (Age Attestation for Online Users).

What it requires

Social media and minors

HB 24-1136 (2024), Healthier Social Media Use by Youth

Colo. Rev. Stat. § 6-1-1601 (and § 22-2-127.8)official signed act text, Colorado General Assembly

In force since partly blocked by a court. Binds private bodies.

What this law does

Requires a social media platform with more than 100,000 active Colorado users to give users under 18 information on how social media affects the developing brain and youth mental and physical health, and to display a notification every 30 minutes once a minor has spent one hour on the platform in a 24 hour period or is using it between 10 p.m. and 6 a.m. Signed , with the platform requirement set for , but preliminarily enjoined before that date.

The order enjoins Section 4 of the Act, which is section 6-1-1601. The school resource bank in section 22-2-127.8 is a separate part of the Act that the order does not enjoin. Colorado has appealed the injunction to the Tenth Circuit.

What it requires

Our analysis of this law draws on 1 court ruling.Premium data

Where nothing was found1 area of law

These areas of law were researched here and no instrument was recorded. Each finding says what the research checked, as of the date under it. It describes our search, not a guarantee that no such law exists.

Reuse law

Colorado has no press-publisher neighbouring right and no mandatory platform-to-publisher bargaining code comparable to California's since-failed Journalism Preservation Act.

The Colorado Revised Statutes have no title addressing copyright, which is occupied entirely by federal law; Title 6's Colorado Consumer Protection Act reaches deceptive trade practices generally but contains no provision on reproduction of headlines or snippets or a text-and-data-mining opt-out, and Title 18's computer crime article addresses unauthorized access rather than content reproduction.

No Colorado bill proposing a journalism usage fee or a platform-to-publisher payment scheme, and no reported Colorado case addressing snippet reproduction, linking, framing, or hot-news misappropriation specifically, was located.

Copyright over news content published in Colorado, including the copyrightability of headlines and snippets, the availability of a fair-use defense, and any text-and-data-mining exception, arises solely under the federal Copyright Act, already covered in the national document.

As of .

Reporting clocks that run here17 instruments

The instruments whose obligation lines set a deadline for reporting an incident, a vulnerability or a personal-data breach, each deadline read from the sentence that carries it and listed shortest first. The law of Colorado comes first, then the law of the bodies above it that applies here.

Each flag is one law, and a link to it. Read down the scale: the clocks document's time axis, with the empty stretches shortened so the deadlines sit close. Flags on one line set the same duty at the same deadline, and the laws behind them are named to the right, with what each clock counts from.

1 hour
Incident notificationsecurity law
4 hours
Incident notificationsecurity law
8 hours
Incident notificationsecurity law
36 hours
72 hours
Breach notificationprivacy law
Safety-incident reportfrontier-model AI law
4 business days
Incident notificationsecurity law
5 business days
Incident notificationsecurity law
7 business days
Breach notificationprivacy law
30 days
Incident notificationsecurity law
Breach notificationprivacy law
Safety-incident reportfrontier-model AI law
60 days
Breach notificationprivacy law
The deadlines above on one time axis, shortest at the top. The axis keeps its order and, between neighbors, its proportion, but a stretch with no deadline on it is shortened, so the hour marks on the left are what say how far apart two stations really are. Beside each action, the laws that set it, what each counts from, and a status where the law is not yet in force. The List tab has the same data in full, with the sentences.

The law of Colorado

30 days

C.R.S. 6-1-716, Notification of Security Breach

C.R.S. section 6-1-716privacy law, in force since

The sentences the clocks are read from

If you experience unauthorized acquisition of unencrypted computerized personal information of Colorado residents, notify affected residents without unreasonable delay and within 30 days of determining a breach occurred.

Notify the Colorado Attorney General of a security breach affecting 500 or more Colorado residents without unreasonable delay and not later than 30 days after the date of determination that a security breach occurred; also notify nationwide consumer reporting agencies if more than 1,000 residents are affected.

The law of the United States, which applies in Colorado

1 hour4 hours8 hours24 hours

NRC cyber security event notifications by nuclear power plant licensees

NRC cyber security event notifications, 10 CFR 73.77security law, in force since

The sentences the clocks are read from

Notify the NRC Headquarters Operations Center via the Emergency Notification System within one hour after discovery of a cyberattack that adversely impacted safety-related or important-to-safety functions, security functions, or emergency preparedness functions (including offsite communications), or that compromised support systems and equipment resulting in adverse impacts to those functions.

Also notify within one hour after discovery of a cyberattack that adversely impacted the safety, security, and emergency preparedness functions performed by digital assets described in 10 CFR 73.77(a)(1)(ii).

Notify the NRC Headquarters Operations Center within four hours after discovery of a cyberattack that could have caused such an adverse impact, after discovery of a suspected or actual cyberattack initiated by personnel with physical or electronic access to the systems in scope, or after notifying a local, State, or other Federal agency of an event related to your cyber security program that does not otherwise require notification.

Notify the NRC Headquarters Operations Center within eight hours after receipt or collection of information regarding observed behavior, activities, or statements that may indicate intelligence gathering or pre-operational planning related to a cyberattack against the systems in scope.

Use the site corrective action program to record vulnerabilities, weaknesses, failures and deficiencies in your cyber security program, and the notifications you make, within twenty-four hours of their discovery.

24 hours72 hours

Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA)

6 U.S.C. 681-681g (CIRCIA)security law, enacted, not yet in force

The sentences the clocks are read from

Once the final rule takes effect, report a covered cyber incident to the Agency not later than 72 hours after your organization reasonably believes that the covered cyber incident has occurred.

Once the final rule takes effect, report a ransom payment to the Agency not later than 24 hours after your organization makes the payment, even where the underlying ransomware attack is not itself a covered cyber incident.

Once the final rule takes effect, promptly submit an update to a previously submitted covered cyber incident report whenever substantial new or different information becomes available or a ransom payment is later made, continuing until your organization notifies the Agency that the incident has concluded and been fully mitigated and resolved, and preserve data relevant to the incident or payment under the procedures the final rule establishes.

24 hours5 business days30 days

SEC Regulation SCI: notification of SCI events to the Commission and to members

SEC Regulation SCI SCI event notices, 17 CFR 242.1002(b) and (c)security law, in force since

The sentences the clocks are read from

Upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, begin appropriate corrective action and notify the Commission of the SCI event immediately.

Within 24 hours of that conclusion, submit a written notification to the Commission, made on a good faith, best efforts basis, that describes the SCI event and the systems affected and, to the extent available, your assessment of the market participants potentially affected, the potential impact on the market, and the steps you have taken, are taking or plan to take.

If the SCI event is resolved and the investigation closed within 30 calendar days, submit a final written notification within five business days after resolution. If not, submit an interim written notification within 30 calendar days after the event, and a final one within five business days after resolution and closure.

36 hours

Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers

12 CFR Part 53 (OCC); 12 CFR Part 225, Subpart N (Federal Reserve Board); 12 CFR Part 304, Subpart C (FDIC)security law, in force since

The sentences the clocks are read from

If your organization is a banking organization, notify your primary federal banking regulator, the OCC, the Federal Reserve Board, or the FDIC, whichever supervises it, about a notification incident, as soon as possible and no later than 36 hours after your organization determines that a notification incident has occurred.

A notification incident is the subset of computer-security incidents that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, your ability to serve customers, a business line, or an operation whose failure would threaten the financial stability of the United States, so a computer-security incident that falls short of that threshold does not by itself start this clock.

If your organization is a bank service provider, notify at least one bank-designated point of contact at each affected banking organization customer as soon as possible after your organization determines that it has experienced a computer-security incident that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, covered services provided to that banking organization for a period of four hours or more.

This duty carries a standard, as soon as possible, rather than a fixed number of hours to notify by, and that disruption threshold is what engages the duty rather than a period to notify within.

72 hours30 days

Artificial Intelligence Risk Management and Security Act of 2026

S. 5576, 119th Congressfrontier-model AI law, proposed

The sentence the clocks are read from

If you are a developer or provider of a frontier AI model, or an operator of critical infrastructure that uses an AI model to manage industrial control systems or other operational technologies, report any confirmed AI safety incident or AI security incident within 30 days of confirmation, and within 72 hours if the incident poses an imminent threat to national security, critical infrastructure or public safety.

72 hours

NCUA Cyber Incident Notification Requirements for Federally Insured Credit Unions

NCUA Cyber Incident Notification Requirements, 12 CFR 748.1(c)security law, in force since

The sentences the clocks are read from

If your organization is a federally insured credit union, notify the NCUA-designated point of contact of a reportable cyber incident by email, telephone, or another method the NCUA prescribes, so that the NCUA receives the notification as soon as possible and no later than 72 hours after your organization reasonably believes it has experienced a reportable cyber incident.

Where the reportable cyber incident is a disruption of business operations or unauthorized access to sensitive data facilitated through, or caused by, a compromise of a credit union service organization, cloud service provider, or other third-party data hosting provider, or by a supply chain compromise, the NCUA must receive the notification within 72 hours of your organization being notified by the third party if that is sooner.

72 hours30 days

Regulation S-P: incident response program and customer breach notice

17 CFR 248.30(a)(3) to (a)(5)privacy law, in force since

The sentences the clocks are read from

Send the notice as soon as practicable, but not later than 30 days, after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred, delaying it only for the period the United States Attorney General specifies where the Attorney General determines that notice poses a substantial risk to national security or public safety (17 CFR 248.30(a)(4)(iii)).

Maintain written policies and procedures reasonably designed to require oversight, including through due diligence and monitoring, of service providers, including that a service provider notify you as soon as possible, and no later than 72 hours, after becoming aware of a breach in security resulting in unauthorized access to a customer information system it maintains (17 CFR 248.30(a)(5)(i)).

72 hours

SEC Regulation S-P: service provider oversight and 72-hour breach notice to the covered institution

SEC Regulation S-P service provider oversight and notice, 17 CFR 248.30(a)(5)security law, in force

The sentence the clocks are read from

Make those policies and procedures reasonably designed to ensure that each service provider takes appropriate measures to protect against unauthorized access to or use of customer information, and to notify you as soon as possible, but no later than 72 hours after becoming aware that a breach in security has occurred resulting in unauthorized access to a customer information system the service provider maintains.

4 business days

SEC Cybersecurity Risk Management, Governance, and Incident Disclosure (Regulation S-K Item 106; Form 8-K Item 1.05)

17 CFR 229.106; 17 CFR 249.308 (Form 8-K Item 1.05)security law, in force since

The sentences the clocks are read from

If your organization is an Securities and Exchange Commission (SEC) reporting company, determine, without unreasonable delay after you discover a cybersecurity incident, whether the incident is material, and if it is, file a Form 8-K under Item 1.05 within four business days after you make that determination.

If the information called for in Item 1.05 is not determined or is unavailable when you file, state that in the filing and file an amendment to the Form 8-K within four business days after you determine it or it becomes available.

7 business days30 days

FCC CPNI breach notification rule

47 CFR 64.2011privacy law, in force

The sentences the clocks are read from

After you reasonably determine that a breach of your customers' CPNI has occurred, electronically notify the United States Secret Service and the Federal Bureau of Investigation through the central reporting facility as soon as practicable, and in no event later than seven business days (47 CFR 64.2011(b)).

Do not notify customers or disclose the breach where the relevant investigating agency directs you in writing not to, for an initial period of up to 30 days that the agency may extend (47 CFR 64.2011(b)(3)).

60 days

FTC Health Breach Notification Rule

16 CFR Part 318privacy law, in force since

The sentences the clocks are read from

If you are a vendor of personal health records (an entity that offers or maintains an electronic record of health information that can draw information from multiple sources and is managed, shared and controlled by or primarily for the individual) or a PHR related entity, notify each affected individual who is a citizen or resident of the United States, in plain language and without unreasonable delay, no later than 60 calendar days after you discover a breach of security of unsecured PHR identifiable health information.

Notify prominent media outlets serving a State or jurisdiction, without unreasonable delay and in no case later than 60 calendar days after you discover the breach, when the unsecured PHR identifiable health information of 500 or more of its residents is, or is reasonably believed to have been, acquired during the breach.

If you are a third party service provider, notify the official designated in a written contract by the vendor of personal health records or PHR related entity you serve (or else a senior official of that vendor or entity), without unreasonable delay and in no case later than 60 calendar days after you discover the breach; identify each customer of that vendor or entity whose unsecured PHR identifiable health information has been, or is reasonably believed to have been, acquired during the breach; and obtain acknowledgment that the notice was received.

60 days

HIPAA Breach Notification Rule

45 CFR Part 164, Subpart D (Sections 164.400-164.414)privacy law, in force since

The sentences the clocks are read from

Notify affected individuals without unreasonable delay and no later than 60 days after discovering a breach of unsecured protected health information.

For a breach of unsecured protected health information involving more than 500 residents of a State or jurisdiction, notify prominent media outlets serving that State or jurisdiction without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.

If you are a business associate, notify the covered entity of a breach of unsecured protected health information without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.

promptly

CFTC system safeguards: prompt notice to Commission staff of cyber security incidents and targeted threats

CFTC system safeguards notices, 17 CFR 39.18(g), 38.1051(e) and 37.1401(e)security law, in force since

The sentences the clocks are read from

If your organization is a derivatives clearing organization, notify staff of the Division of Clearing and Risk promptly of any hardware or software malfunction, security incident, or targeted threat that materially impairs, or creates a significant likelihood of material impairment of, automated system operation, reliability, security, or capacity, and of any activation of your business continuity and disaster recovery plan.

If your organization is a designated contract market, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and significant systems malfunctions and activations of your business continuity-disaster recovery plan.

If your organization is a swap execution facility, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and material system malfunctions and activations of your business continuity-disaster recovery plan.

immediately

Coast Guard Cybersecurity in the Marine Transportation System: reportable cyber incidents

Coast Guard reportable cyber incident reporting, 33 CFR 101.620(b)(7) and 101.615security law, in force since

The sentence the clocks are read from

Evidence of sabotage, subversive activity, or an actual or threatened cyber incident involving or endangering any vessel, harbor, port, or waterfront facility must be reported immediately to the Federal Bureau of Investigation, the Cybersecurity and Infrastructure Security Agency (for any cyber incident), and the Captain of the Port, or to their respective representatives.

Which of these one incident starts turns on the facts: the incident method works that through. The clocks document draws every clock in the LexLint law library on one axis, with the sentence beside every rung.

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

This page covers the instruments LexLint has researched to a stage. Instruments named in the law library but not yet researched are counted in the head and are not listed here. Every entry carries its own primary source on its note page. This is a research index, not legal advice.