Skip to content

Tracker · re-checked monthly

State privacy laws, and the security each one requires.

The nineteen comprehensive state privacy laws listed here are in force, and four more arrive by 2028. Nearly all require reasonable data security, written processor contracts and, for risky processing, documented assessments. Each row below was checked against the statute or the state's own guidance, last on November 19, 2026.

Last verified November 19, 2026

Laws in force

StateLawIn forceWho is coveredSecurity dutyAssessmentsEnforcement
CaliforniaCCPA as amended (Civ. Code §1798.100 et seq.) and CPPA regulationsIn force; risk-assessment rules from Jan 1, 2026; cybersecurity audit certifications due Apr 1 of 2028, 2029 or 2030 by revenueRevenue over $26,625,000 (2025 adjustment), or 100,000+ consumers or households, or 50%+ of revenue from selling or sharing dataReasonable security appropriate to the information (§1798.100(e), §1798.81.5)Risk assessments; cybersecurity audits for higher-risk businessesCPPA and Attorney General
VirginiaVCDPA (Va. Code §59.1-575 et seq.)Jan 1, 2023100,000 consumers, or 25,000 plus over 50% of revenue from data salesReasonable administrative, technical and physical practices (§59.1-578(A)(3))Yes (§59.1-580)AG; 30-day cure
ColoradoColorado Privacy Act (C.R.S. §6-1-1301 et seq.)Jul 1, 2023100,000 consumers, or 25,000 plus revenue or discounts from data salesReasonable measures to secure data (§6-1-1308(5)); processors must apply risk-appropriate security (§6-1-1305(4))Yes (§6-1-1309)AG and district attorneys; cure period ended Jan 1, 2025
ConnecticutCTDPA (Conn. Gen. Stat. §42-515 et seq.)Jul 1, 2023; amendments Jul 1, 2026From Jul 1, 2026: 35,000 consumers, or any sensitive data, or any sale of dataReasonable data security safeguards (§42-520)Yes; profiling impact assessments for processing from Aug 1, 2026AG; cure period ended Jan 1, 2025
UtahUCPA (Utah Code §13-61-101 et seq.)Dec 31, 2023$25M+ revenue and 100,000 consumers, or 25,000 plus over 50% of revenue from data salesReasonable administrative, technical and physical practices (§13-61-302(2))NoDivision of Consumer Protection and AG; 30-day cure
TexasTDPSA (Bus. & Com. Code ch. 541)Jul 1, 2024No count threshold; SBA small businesses exempt except for selling sensitive data without consentReasonable data security practices (Texas AG summary)YesAG only; 30-day cure (§541.154)
OregonOCPA (ORS 646A.570–646A.589)Jul 1, 2024 (nonprofits Jul 1, 2025)100,000 consumers, or 25,000 plus 25%+ of revenue from data salesSafeguards as required by ORS 646A.622 (ORS 646A.578(1)(c))Yes (ORS 646A.586)AG; cure period ended Jan 1, 2026
MontanaMCDPA (MCA §30-14-2801 et seq.)Oct 1, 202425,000 consumers, or 15,000 plus over 25% of revenue from data salesReasonable administrative, technical and physical practices (§30-14-2812(1)(b))Yes (§30-14-2814)AG; no cure provision in the current text
IowaICDPA (Iowa Code ch. 715D)Jan 1, 2025100,000 consumers, or 25,000 plus over 50% of revenue from data salesReasonable administrative, technical and physical practices (§715D.4(1))NoAG; 90-day cure
DelawareDPDPA (6 Del. C. ch. 12D)Jan 1, 2025; lower thresholds from Jan 1, 202735,000 consumers, or 10,000 plus over 20% of revenue from data sales (10,000 or 5,000 from 2027)Reasonable administrative, technical and physical practices (§12D-106(a)(3))Yes, at 100,000+ consumers (50,000 from 2027)Department of Justice; mandatory cure ended Dec 31, 2025
New HampshireRSA 507-HJan 1, 202535,000 consumers, or 10,000 plus over 25% of revenue from data salesPractices appropriate to the volume and nature of the data (507-H:6, I(c))Yes (507-H:8)AG; mandatory cure ended Dec 31, 2025
New JerseyN.J.S.A. 56:8-166.4 et seq.Jan 15, 2025100,000 consumers, or 25,000 plus revenue or discounts from data salesReasonable security practices (56:8-166.12(a)(3)); processor contracts must include security measuresYesAG; cure period ended Jul 1, 2026
NebraskaNeb. Rev. Stat. 87-1101 to 87-1130Jan 1, 2025Businesses that are not federally defined small businesses and that process or sell personal dataReasonable practices (87-1112(1)(b))YesAG; 30-day cure
TennesseeTennessee Information Protection Act (Tenn. Code Ann. 47-18-3201 et seq.)Jul 1, 2025Over $25M revenue and 175,000 consumers, or 25,000 plus 50%+ of revenue from data salesData security practices required (47-18-3204)YesAG; 60-day cure; a privacy program conforming to the NIST privacy framework is a defense
MinnesotaMCDPA (Minn. Stat. 325M.10–325M.21)Jul 31, 2025100,000 consumers, or 25,000 plus over 25% of revenue from data sales; small businesses largely exemptReasonable security plus a data inventory (325M.16, subd. 2)Yes (325M.18)AG; cure period ended Jan 31, 2026
MarylandMODPA (Com. Law §14-4601 to §14-4614)Oct 1, 2025 (not applied to processing before Apr 1, 2026)35,000 consumers, or 10,000 plus over 20% of revenue from data salesReasonable security (§14-4607(b)(1)(ii)); processor contracts must include securityYes, including for algorithms (§14-4610)Consumer Protection Division; optional cure through Apr 1, 2027
IndianaIndiana Consumer Data Protection Act (IC 24-15)Jan 1, 2026100,000 residents, or 25,000 plus over 50% of revenue from data salesSee IC 24-15See IC 24-15AG
KentuckyKRS 367.3611–367.3629Jan 1, 2026100,000 consumers, or 25,000 plus over 50% of revenue from data salesReasonable practices (367.3617(1)(c))Yes, for processing from Jun 1, 2026AG; 30-day cure
Rhode IslandR.I. Gen. Laws ch. 6-48.1Jan 1, 202635,000 customers, or 10,000 plus over 20% of revenue from data salesReasonable safeguards for data processed under 6-48.1-7(s)YesAG; no cure period

Enacted, not yet in force

StateLawEffectiveWho is coveredSecurity dutyAssessmentsEnforcement
LouisianaAct 502 of 2026 (R.S. 51:1780.1–1780.5)Jan 1, 2027Over $25M revenue, 75,000+ consumers, households or devices, or 50%+ of revenue from data salesR.S. 51:1780.4(A)(1)(b)YesAG; 30-day cure through July 2027
OklahomaSB 546 (2026)Jan 1, 2027Over 100,000 consumers, or 25,000 plus a majority of revenue from data salesRequired—AG
AlabamaHB 351 (2026)May 1, 2027Over 25,000 consumers, or over 25% of revenue from data sales§7(a)(2)NoAG; 45-day cure; up to $15,000 per violation
VermontAct 145 of 2026 (9 V.S.A. §2415a–2415k)Jan 1, 202835,000 consumers, or 3,000 for sensitive data or data sales§2415e(a)(3)Yes (§2415g)AG; 60-day cure through Jun 30, 2029

Thresholds are counts of state residents whose data is processed in a year, as each law defines them. Most laws exempt some entities, such as HIPAA- or GLBA-regulated organizations and nonprofits; check the statute.

Where ISO/IEC 27001 fits

  • One program, many states. The security duties are written in similar terms: reasonable administrative, technical and physical practices scaled to the data. One risk-based information security management system answers all of them, instead of a policy per state.
  • Evidence, not just policy. An ISO/IEC 27001 certificate shows an independent auditor has checked that the controls operate. That is useful when an Attorney General, a customer or an insurer asks what "reasonable" meant in practice.
  • Processors under control. Supplier security, confidentiality terms and flow-down to subcontractors map to Annex A controls 5.19 to 5.22, with each processor contract checked.
  • Assessments with a home. Privacy assessments and the ISMS risk assessment can share one method and one register; ISO/IEC 27701 extends the system to privacy.

Estimate the audit with our ISO 27001 audit days calculator, budget with the ISO 27001 cost guide, and check the standard's status on Is ISO 27001 being revised?

Common questions

Does any state privacy law require ISO 27001 certification?

No. None of the laws on this page requires ISO/IEC 27001. Most require reasonable administrative, technical and physical data security practices, scaled to the volume and sensitivity of the data. An ISO/IEC 27001 information security management system is a well-documented way to show those practices exist, are risk-based and are checked by an independent auditor.

How many states have comprehensive privacy laws?

Nineteen state laws are in force on this page as of November 19, 2026, and four more take effect between January 2027 and January 2028 (Louisiana, Oklahoma, Alabama and Vermont). Many other states have breach-notification and sector laws that are not listed here.

What do processor contracts have to say?

Almost every law requires a contract between the controller and each processor, with a duty of confidentiality for everyone handling the data and help with security and breach obligations. Colorado, New Jersey, Minnesota and Maryland go further on security in the processor relationship. In an ISMS that is supplier security (Annex A 5.19 to 5.22), with the contract terms checked per supplier.

What is a data protection assessment, and does ISO 27001 cover it?

Most of these laws require a documented assessment before high-risk processing such as targeted advertising, selling data, profiling or sensitive data. It weighs benefits against risks to consumers. An ISO/IEC 27001 risk assessment covers security risk to the organization; a privacy assessment needs the consumer-harm view as well. ISO/IEC 27701, the privacy extension, bridges the two.

Sources

Changelog

  • 2026-11-19 — Published. Nineteen laws in force and four enacted for 2027–2028, each checked against statute text, the Attorney General or the state privacy agency on November 19, 2026.

Information, not legal advice. Confirm how a law applies to you with counsel.