State comprehensive privacy laws in 2026: the shared core, the exemptions that now differ, and three new laws, explained
Read side by side, the Virginia, Colorado, Texas, Maryland and Connecticut statutes share a core of consumer rights, data protection assessments and GLBA and HIPAA carve-outs. The details are drifting apart, and Alabama, Oklahoma and Vermont added laws in 2026 that take effect from 2027.
What this explainer covers
This explainer compares eight statutes, each read from the legislature’s own text: Virginia’s Consumer Data Protection Act [1], the Colorado Privacy Act as enacted in 2021 [2], the Texas Data Privacy and Security Act as enacted in 2023 [3], the Maryland Online Data Privacy Act [4] [5] [6] [7], Connecticut’s Data Privacy Act in its 2026 Supplement [8], and the three laws enacted in 2026 in Alabama [9], Oklahoma [10] and Vermont [12]. Other states have similar laws that we did not review for this piece, and Colorado and Texas have been amended since enactment in ways this comparison does not track.
The rights almost all of them share
The rights lists are close to identical. Virginia gives consumers the right to confirm whether a controller is processing their personal data and to access it; to correct inaccuracies; to delete; to obtain a portable copy of data they provided; and to opt out of processing for targeted advertising, sale, or profiling in furtherance of decisions that produce legal or similarly significant effects [1]. Colorado lists rights to opt out, of access, to correction, to deletion and to data portability [2]. Texas [3], Oklahoma [10] and Alabama [9] follow the same pattern; Alabama frames the profiling opt-out as covering solely automated significant decisions [9].
The newer texts go further on profiling. In the version in force from July 1, 2026, Connecticut’s access right extends to inferences derived from personal data and to whether the data is used for profiling that produces legal or similarly significant effects. A consumer subject to such a decision may, if feasible, question the result, be told the reason, and review the data used, with a right to correct data used in housing decisions [8]. Vermont’s access right also reaches inferences and profiling [12].
The mechanics also converge. Virginia and Alabama both give controllers 45 days to respond, with a possible extension of 45 more days [1] [9]. Virginia requires an appeal process and a written answer within 60 days of an appeal [1]. We found no appeal provision in Alabama’s enrolled text [9].
Data protection assessments
Most of these laws require a controller to conduct and document a data protection assessment before certain processing. Virginia’s list has five triggers: targeted advertising, sale, profiling that presents a reasonably foreseeable risk of listed harms, processing of sensitive data, and any processing that presents a heightened risk of harm [1]. The assessment weighs the benefits of the processing against the risks to the consumer, as mitigated by safeguards, and the Attorney General can obtain it through a civil investigative demand while it stays confidential [1]. Texas uses the same five triggers [3]. Colorado requires an assessment for processing that presents a heightened risk of harm, defined to include targeted advertising, risky profiling, selling personal data and processing sensitive data [2].
The details then diverge:
- Maryland requires assessments “on a regular basis,” including an assessment for each algorithm that is used, adds the necessity and proportionality of the processing to the weighing, and applies the requirement to processing on or after October 1, 2025 [7].
- Connecticut, from July 1, 2026, adds a separate impact assessment for profiling used to make decisions with legal or similarly significant effects, covering purpose, risks and mitigations, data inputs and outputs, performance metrics, transparency measures and post-deployment monitoring [8].
- Vermont requires data protection assessments, and a separate impact assessment for such profiling [12].
- Oklahoma requires data protection assessments; a controller must make one available to the Attorney General on written request under a civil investigative demand, and assessments are confidential [10].
- Alabama’s enrolled text contains no data protection assessment requirement [9].
The GLBA and HIPAA carve-outs, and where they now differ
Every statute reviewed exempts data regulated by Title V of the Gramm-Leach-Bliley Act and by HIPAA, but the level of the exemption matters for banks, health systems and their vendors:
- Entity-level for both: Virginia exempts any financial institution or data subject to GLBA Title V and any HIPAA covered entity or business associate [1]. Texas [3] and Oklahoma [10] use nearly the same wording. Alabama exempts financial institutions or affiliates governed by GLBA, data handled in accordance with Title V, and covered entities and business associates [9].
- Entity-level for finance, data-level for health: Colorado exempts financial institutions and affiliates subject to GLBA, but for health it exempts protected health information collected, stored and processed by a covered entity or its business associates [2]. Maryland exempts financial institutions, affiliates and GLBA data, but its health exemption is for protected health information under HIPAA and related categories, not for covered entities as such [5].
- Narrowed finance exemption: From July 1, 2026, Connecticut deleted its exemption for any financial institution or data subject to GLBA. It now exempts data subject to Title V, plus banks and credit unions that are only and directly engaged in financial activities, are regulated and examined by the Department of Banking or a federal bank regulator, and have a program to meet that regulator’s personal data requirements; and broker-dealers and investment advisers regulated by the Department of Banking or the SEC. Covered entities and business associates remain exempt [8].
- Vermont exempts covered entities that are not hybrid entities, the health care components of hybrid entities and business associates; data subject to GLBA Title V; and state- or federally chartered banks and credit unions, or affiliates principally engaged in financial activities [12].
For a financial or health organization, the practical point is that an exemption that covered the whole entity in one state may cover only certain data in another. In our view, a data inventory that tags which records are GLBA or HIPAA data is what makes those differences manageable; that is a practice view, not a requirement of any of these laws.
Who is covered
Applicability thresholds have moved down over time:
- Virginia: 100,000 consumers in a calendar year, or 25,000 consumers plus over 50% of gross revenue from selling personal data [1]. Oklahoma uses the same figures [10]. Colorado: 100,000 consumers, or 25,000 consumers plus revenue or a discount from selling personal data [2].
- Texas has no consumer count. It applies to a person that does business in Texas, processes or sells personal data, and is not a small business as defined by the U.S. Small Business Administration [3].
- Maryland: 35,000 consumers, or 10,000 consumers plus more than 20% of gross revenue from selling personal data [4]. Connecticut, from July 1, 2026: 35,000 consumers, or any control or processing of sensitive data, or offering personal data for sale [8]. Vermont: 35,000 consumers, sensitive data of 3,000 consumers, or offering for sale the personal data of 3,000 consumers [12].
- Alabama: more than 25,000 consumers, or more than 25% of gross revenue from selling personal data. It exempts businesses with fewer than 500 employees that do not sell personal data [9].
Maryland also adds a rule the others do not share: a controller may not collect, process or share sensitive data unless strictly necessary to provide or maintain a specific product or service the consumer requested, and may not sell sensitive data [6].
The three 2026 laws and their dates
- Oklahoma, SB 546. Passed the House on February 19, 2026 and the Senate on March 16, 2026 [10]; approved by the Governor on March 20, 2026 [11]; effective January 1, 2027 [10]. The Attorney General must give 30 days’ written notice and an opportunity to cure; penalties are up to $7,500 per violation [10].
- Alabama, HB 351, the Alabama Personal Data Protection Act. The enrolled bill records passage by the House on February 24, 2026, Senate passage with amendment on April 7, 2026 and House concurrence the same day; it takes effect May 1, 2027 [9]. The Attorney General must issue a notice of violation and allow 45 days to correct it, and a court may assess up to $15,000 per violation [9].
- Vermont, S.71 (Act 145), the Vermont Data Privacy and Online Surveillance Act. Signed by the Governor on June 16, 2026 [12] [13]; effective January 1, 2028 [12]. From January 1, 2028 to June 30, 2029, the Attorney General must give notice and 60 days to cure where a cure is possible. The legislature chose not to create a private right of action. Privacy notices must state whether the controller collects, uses or sells personal data to train large language models [12].
In Virginia, Alabama, Oklahoma and Vermont, the Attorney General enforces the law, and each of those statutes includes a notice and cure step, permanent or time-limited [1] [9] [10] [12]. Virginia’s cure period is 30 days and its civil penalty up to $7,500 per violation [1].
This explainer compares statutes; it is not legal advice, and organizations should confirm with counsel which laws apply to them and how.
Moraph’s teams help organizations with work like this. See our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.