Data breach notification laws by state
| Jurisdiction | Statute | Enacted or effective | Who must notify | Notice to individuals | Notice to a state regulator | Threshold for regulator notice | Encryption safe harbor |
|---|---|---|---|---|---|---|---|
| Alabama Full page | StatuteAla. Code §§ 8-38-1 to 8-38-12 (Alabama Data Breach Notification Act of 2018)1 | Enacted or effectiveEnacted by Act 2018-3961 | Who must notifyEntities, including nonprofits and state, county and municipal government entities, that acquire or use sensitive personally identifying information; third-party agents must tell the entity within 10 days.1 | Notice to individualsAs expeditiously as possible, within 45 days of determining a breach likely to cause substantial harm or of a third-party agent's notice.1 | Notice to a state regulatorAttorney General, in writing, within the same 45 days, when more than 1,000 individuals must be notified.1 | Threshold for regulator noticeMore than 1,000 individuals (Attorney General and nationwide credit agencies).1 | Encryption safe harborYes, encrypted or otherwise secured data is excluded, unless the entity knows or has reason to know that the encryption key or security credential was breached together with it.1 |
| Alaska | StatuteAlaska Stat. §§ 45.48.010 to 45.48.0902 | Enacted or effectiveNot confirmed (see Method) | Who must notifyPersons doing business, persons with more than 10 employees, and state or local agencies (not the judicial branch) owning or licensing residents' personal information in any form.2 | Notice to individualsMost expeditious time possible and without unreasonable delay; law-enforcement delay allowed.2 | Notice to a state regulatorNo regulator notice for a notified breach; written notice to the Attorney General is required before skipping notice on a no-harm determination.2 | Threshold for regulator noticeNot applicable: no regulator notice threshold; nationwide credit agencies if more than 1,000 residents notified.2 | Encryption safe harborYes, encrypted or redacted information is excluded, unless the encryption key has been accessed or acquired.2 |
| Arizona | StatuteAriz. Rev. Stat. §§ 18-551, 18-5524 | Enacted or effectiveNot confirmed (see Method) | Who must notifyPersons doing business in Arizona, including governments and agencies, that own, maintain or license computerized personal information; state police, sheriffs, municipal police, prosecutors and courts are excluded.3 | Notice to individualsWithin 45 days after determining a breach occurred; law enforcement may delay, then 45 days after clearance.4 | Notice to a state regulatorAttorney General and director of the Arizona Department of Homeland Security, in writing, within the same 45 days, if over 1,000 individuals.4 | Threshold for regulator noticeMore than 1,000 individuals (AG, homeland security director and three largest credit agencies).4 | Encryption safe harborYes: a breach covers only unencrypted and unredacted computerized personal information; the text sets no key-compromise exception.3 |
| Colorado Full page | StatuteColo. Rev. Stat. § 6-1-7165 | Enacted or effectiveAdded 2006, effective September 1, 2006; repealed and reenacted in part by HB 18-1128, effective September 1, 20185 | Who must notifyPersons that maintain, own or license personal information in their business, vocation or occupation; third-party service providers must notify the covered entity.5 | Notice to individualsMost expedient time possible, no later than 30 days after determining a breach occurred; not required if misuse has not occurred and is unlikely.5 | Notice to a state regulatorColorado Attorney General, no later than 30 days after determining the breach, if 500 or more residents are reasonably believed affected.5 | Threshold for regulator notice500 or more Colorado residents (AG); more than 1,000 residents (nationwide credit agencies).5 | Encryption safe harborYes, unless the encryption key or other means to decipher the data was also acquired or reasonably believed acquired.5 |
| Connecticut Full page | StatuteConn. Gen. Stat. § 36a-701b6 | Enacted or effectiveP.A. 05-148, effective January 1, 2006; last amended by P.A. 23-986 | Who must notifyAny person that owns, licenses or maintains computerized data including personal information of Connecticut residents.6 | Notice to individualsWithout unreasonable delay, no later than 60 days after discovery, unless federal law requires sooner; no notice if harm is unlikely after investigation.6 | Notice to a state regulatorAttorney General, no later than the time notice goes to residents.6 | Threshold for regulator noticeAny breach requiring resident notice (no minimum).6 | Encryption safe harborYes: a breach excludes data secured by encryption or other means making it unreadable or unusable; no key-compromise exception stated.6 |
| Delaware Full page | StatuteDel. Code tit. 6, §§ 12B-101 to 12B-1047 | Enacted or effectiveEnacted by 75 Del. Laws c. 61; most recently amended by 85 Del. Laws c. 4647 | Who must notifyPersons doing business in Delaware that own or license computerized personal information; 'person' includes governments and agencies. Data maintainers must notify the owner.7 | Notice to individualsWithout unreasonable delay, no later than 60 days after determining the breach; not required if harm is unlikely after investigation.7 | Notice to a state regulatorAttorney General, no later than notice to residents, when over 500 residents are affected.7 | Threshold for regulator noticeMore than 500 Delaware residents.7 | Encryption safe harborYes, unless the encryption key was also acquired, or reasonably believed acquired, and could make the data readable.7 |
| District of Columbia Full page | StatuteD.C. Code §§ 28-3851, 28-38529 | Enacted or effectiveD.C. Law 16-237 (Mar. 8, 2007), applying as of July 1, 2007; amended by D.C. Law 23-98 (June 17, 2020)8 | Who must notifyPersons or entities doing business in DC that own or license computerized or electronic personal information; the DC government is excluded.8 | Notice to individualsMost expedient time possible and without unreasonable delay, subject to law-enforcement needs and steps to scope the breach.9 | Notice to a state regulatorOffice of the Attorney General for DC, in writing, promptly and no later than notice to residents, if 50 or more residents affected.9 | Threshold for regulator notice50 or more DC residents (AG); more than 1,000 persons (nationwide credit agencies).9 | Encryption safe harborYes, data made secure by encryption or redaction is excluded, unless information obtained could compromise that protection.8 |
| Florida Full page | StatuteFla. Stat. § 501.17110 | Enacted or effectiveCreated by ch. 2014-189 and ch. 2014-190, Laws of Florida; most recently amended by ch. 2026-5210 | Who must notifyCommercial entities that acquire, maintain, store or use personal information, plus state governmental entities for notice duties; third-party agents must tell the entity within 10 days.10 | Notice to individualsAs expeditiously as practicable, no later than 30 days after determining or having reason to believe a breach occurred; 15-day extension possible for good cause.10 | Notice to a state regulatorDepartment of Legal Affairs (Attorney General), in writing, within 30 days, if 500 or more Floridians are affected.10 | Threshold for regulator notice500 or more individuals in Florida (department); more than 1,000 at once (nationwide credit agencies).10 | Encryption safe harborYes, encrypted, secured or de-identified information is excluded from 'personal information'; no key-compromise exception stated.10 |
| Georgia Full page | StatuteO.C.G.A. §§ 10-1-911, 10-1-912 (Georgia Personal Identity Protection Act)11 | Enacted or effectiveEnacted by Ga. L. 2005, p. 851 (SB 230); § 10-1-912 amended Ga. L. 2007, p. 450 (SB 236)11 | Who must notifyInformation brokers (paid sellers of personal data to third parties) and data collectors (state or local agencies); general businesses are not named11 | Notice to individualsMost expedient time possible and without unreasonable delay, subject to law enforcement needs and scoping; vendors must tell the owner within 24 hours11 | Notice to a state regulatorNone required by this statute11 | Threshold for regulator noticeNot applicable: no regulator notice; consumer reporting agencies if more than 10,000 residents at one time11 | Encryption safe harborYes: notice covers unencrypted data, and personal information applies only when name or data elements are not encrypted or redacted11 |
| Hawaii Full page | StatuteHaw. Rev. Stat. §§ 487N-1, 487N-212 | Enacted or effectiveL 2006, c 135; § 487N-2 amended L 2008, c 1912 | Who must notifyBusinesses owning or licensing residents' personal information in any form (computerized, paper or otherwise) and State or county government agencies12 | Notice to individualsWithout unreasonable delay, subject to law enforcement needs and measures to find contacts, set scope and restore the system12 | Notice to a state regulatorBusinesses: Hawaii Office of Consumer Protection, in writing without unreasonable delay; no regulator notice stated for agencies in this section12 | Threshold for regulator noticeMore than 1,000 persons notified at one time (same threshold for consumer reporting agencies)12 | Encryption safe harborYes, unless the encrypted data is acquired along with the confidential process or key13 |
| Idaho Full page | StatuteIdaho Code §§ 28-51-104, 28-51-10514 | Enacted or effectiveAdded 2006, ch. 258; § 28-51-105 amended 2014, ch. 9714 | Who must notifyCity, county or state agencies, individuals and commercial entities doing business in Idaho that own or license computerized personal information of residents14 | Notice to individualsAs soon as possible, in the most expedient time possible without unreasonable delay, once investigation finds misuse occurred or is reasonably likely14 | Notice to a state regulatorAgencies only: Idaho Attorney General within 24 hours of discovering the breach; no regulator notice stated for private entities14 | Threshold for regulator noticeAny agency breach (no minimum); not applicable to private entities14 | Encryption safe harborYes: a breach covers only unencrypted data, and personal information applies when name or data elements are not encrypted15 |
| Illinois Full page | Statute815 ILCS 530/5, 530/10, 530/12 (Personal Information Protection Act)16 | Enacted or effectiveP.A. 94-36, eff. 1-1-06; Sec. 10 last amended by P.A. 101-343, eff. 1-1-2016 | Who must notifyData collectors (government agencies, universities, corporations, financial institutions, retailers and others) that own or license residents' personal information; State agencies under Sec. 1216 | Notice to individualsMost expedient time possible and without unreasonable delay, consistent with measures to determine scope and restore the system16 | Notice to a state regulatorAttorney General, no later than consumer notice; State agencies within 45 days of discovery or at consumer notice, whichever is sooner16 | Threshold for regulator noticeMore than 500 Illinois residents in a single breach (State agencies: more than 250)16 | Encryption safe harborYes, encrypted or redacted data excluded unless the keys to read it were acquired through the breach16 |
| Indiana Full page | StatuteInd. Code art. 24-4.9 (chiefly IC 24-4.9-3-1 and 24-4.9-3-3)17 | Enacted or effectiveAdded by P.L.125-2006; deadline section last amended by P.L.171-202217 | Who must notifyData base owners: persons owning or licensing computerized personal information; state agencies and the judicial and legislative departments are excluded17 | Notice to individualsWithout unreasonable delay, and not more than 45 days after discovery; listed reasonable delays (scope, system integrity, law enforcement) allowed17 | Notice to a state regulatorAttorney General, whenever disclosure to residents is made; the chapter's 45-day limit applies to disclosures under it17 | Threshold for regulator noticeAny breach requiring resident notice (no minimum); consumer reporting agencies if more than 1,000 consumers17 | Encryption safe harborYes, encrypted or redacted data excluded, unless acquired by someone with access to the encryption key17 |
| Iowa Full page | StatuteIowa Code §§ 715C.1-715C.2 (Chapter 715C)18 | Enacted or effective2008 Acts, ch 1154; most recently amended 2018 Acts, ch 109118 | Who must notifyAny person (including governments and their agencies) owning or licensing computerized personal information used in business, vocation, occupation or volunteer activities18 | Notice to individualsMost expeditious manner possible and without unreasonable delay, subject to law enforcement needs and scoping18 | Notice to a state regulatorDirector of the Attorney General's consumer protection division, in writing within five business days after notifying any consumer18 | Threshold for regulator noticeMore than 500 Iowa residents18 | Encryption safe harborYes, encrypted, redacted or otherwise unreadable data is excluded, unless the keys to read it were obtained in the breach18 |
| Kansas Full page | StatuteK.S.A. 50-7a01, 50-7a0219 | Enacted or effectiveL. 2006, ch. 149, §§ 3-4; July 1 (2006)19 | Who must notifyPersons conducting business in Kansas and governments, governmental subdivisions or agencies that own or license computerized personal information19 | Notice to individualsAs soon as possible, in the most expedient time possible and without unreasonable delay, after investigation finds misuse occurred or is reasonably likely19 | Notice to a state regulatorNone required by this statute; Attorney General (or Insurance Commissioner for insurers) enforces19 | Threshold for regulator noticeNot applicable: no regulator notice; consumer reporting agencies if more than 1,000 consumers at one time19 | Encryption safe harborYes: personal information covers only data elements neither encrypted nor redacted20 |
| Kentucky Full page | StatuteKRS 365.732 (private entities); public agencies are covered separately by KRS 61.931 to 61.93421 | Enacted or effectiveCreated 2014 Ky. Acts ch. 84, sec. 1, effective July 15, 201421 | Who must notifyAny person or business entity conducting business in Kentucky; excludes GLBA- and HIPAA-regulated persons and state and local government agencies21 | Notice to individualsMost expedient time possible and without unreasonable delay, subject to law enforcement needs and scoping21 | Notice to a state regulatorNone required by this statute21 | Threshold for regulator noticeNot applicable: no regulator notice; consumer reporting agencies if more than 1,000 persons at one time21 | Encryption safe harborYes: a breach covers only unencrypted and unredacted data21 |
| Louisiana Full page | StatuteLa. R.S. 51:3073-3074 (Database Security Breach Notification Law)22 | Enacted or effectiveActs 2005, No. 499, effective Jan. 1, 2006; amended Acts 2018, No. 38222 | Who must notifyAny person or agency (state, political subdivision or their bodies) that owns or licenses computerized personal information; maintainers must notify the owner23 | Notice to individualsMost expedient time possible without unreasonable delay, no later than 60 days from discovery; extensions allowed for law enforcement or scoping22 | Notice to a state regulatorNo routine regulator notice in the statute; if notice is delayed, written reasons go to the Attorney General within the 60-day period22 | Threshold for regulator noticeNot applicable: the statute sets no regulator notice threshold22 | Encryption safe harborYes: data is personal information only when the name or data element is not encrypted or redacted23 |
| Maine Full page | Statute10 M.R.S. §§ 1347-1348 (Chapter 210-B, Notice of Risk to Personal Data)24 | Enacted or effectiveAdded by PL 2005, c. 379; most recently amended by PL 2019, c. 51224 | Who must notifyInformation brokers and other persons maintaining computerized personal information; 'person' includes state agencies, municipalities, schools and universities25 | Notice to individualsAs expediently as possible without unreasonable delay, and no more than 30 days after learning of the breach and its scope (absent law enforcement delay)24 | Notice to a state regulatorAppropriate state regulators in the Department of Professional and Financial Regulation, or the Attorney General if not regulated by that department; no timing stated24 | Threshold for regulator noticeAny breach requiring resident notice (no minimum); consumer reporting agencies if more than 1,000 persons24 | Encryption safe harborYes: data is personal information only when the name or data elements are not encrypted or redacted25 |
| Maryland | StatuteMd. Code, Com. Law § 14-3504 (definitions in § 14-3501)26 | Enacted or effectiveNot confirmed (see Method) | Who must notifyBusinesses, including financial institutions and nonprofits, that own, license or maintain computerized personal information of Maryland residents26 | Notice to individualsAs soon as reasonably practicable, no later than 45 days after discovering or being notified of the breach; limited delays allowed26 | Notice to a state regulatorOffice of the Attorney General, before notifying individuals; notice must state number of Maryland residents affected and include a sample notice26 | Threshold for regulator noticeAny breach requiring individual notice (no minimum)26 | Encryption safe harborYes, data elements that are encrypted, redacted or otherwise made unreadable or unusable are excluded from personal information27 |
| Massachusetts | StatuteMass. Gen. Laws ch. 93H, § 3 (definitions in § 1)28 | Enacted or effectiveNot confirmed (see Method) | Who must notifyPersons and state or local agencies that own, license, maintain or store data with personal information of Massachusetts residents28 | Notice to individualsAs soon as practicable and without unreasonable delay; may not wait until the number of affected residents is known28 | Notice to a state regulatorAttorney General and Director of Consumer Affairs and Business Regulation, as soon as practicable; also any consumer reporting or state agencies the director names28 | Threshold for regulator noticeAny breach (no minimum)28 | Encryption safe harborYes, unless the confidential process or key was also acquired; encryption means at least 128-bit29 |
| Michigan Full page | StatuteMich. Comp. Laws § 445.72 (Identity Theft Protection Act, sec. 12)30 | Enacted or effectiveAdded 2006 PA 566, eff. July 2, 2007; amended 2010 PA 315, eff. Apr. 1, 201130 | Who must notifyPersons and state agencies (including state universities) that own or license data in a database31 | Notice to individualsWithout unreasonable delay; delay allowed to scope the breach or at law enforcement request30 | Notice to a state regulatorNone required by this statute; nationwide consumer reporting agencies must be told without unreasonable delay30 | Threshold for regulator noticeNot applicable: no regulator notice. Consumer reporting agency notice unless 1,000 or fewer residents notified30 | Encryption safe harborYes, notice covers unencrypted and unredacted data, or encrypted data taken by someone with the encryption key30 |
| Minnesota Full page | StatuteMinn. Stat. § 325E.6132 | Enacted or effectiveLaws 2005, ch. 167, s. 1; amended 2006, ch. 212 and ch. 23332 | Who must notifyPersons and businesses conducting business in Minnesota that own or license personal information; financial institutions exempt32 | Notice to individualsMost expedient time possible and without unreasonable delay; law enforcement may delay to a date certain32 | Notice to a state regulatorNone required by this statute; Attorney General enforces it32 | Threshold for regulator noticeNot applicable: no regulator notice. Consumer reporting agencies within 48 hours if more than 500 persons notified32 | Encryption safe harborYes, unless the encryption key, password or other means to read the data was also acquired32 |
| Mississippi Full page | StatuteMiss. Code Ann. § 75-24-29 (as amended by 2021 HB 277, effective July 1, 2021)33 | Enacted or effectiveEnacted by 2010 HB 583, effective July 1, 201134 | Who must notifyPersons conducting business in Mississippi that own, license or maintain personal information of residents33 | Notice to individualsWithout unreasonable delay, after investigation to scope the incident; law enforcement may delay33 | Notice to a state regulatorNone required by this statute; Attorney General enforces it as an unfair trade practice33 | Threshold for regulator noticeNot applicable: no regulator notice33 | Encryption safe harborYes, breach covers only data not secured by encryption or another method making it unreadable or unusable33 |
| Missouri Full page | StatuteMo. Rev. Stat. § 407.150035 | Enacted or effectiveEffective August 28, 2009 (L. 2009 H.B. 62)35 | Who must notifyPersons, including businesses and government bodies, that own or license personal information of Missouri residents35 | Notice to individualsWithout unreasonable delay, consistent with law enforcement needs and measures to scope the breach35 | Notice to a state regulatorAttorney General's office and nationwide consumer reporting agencies, without unreasonable delay, when over 1,000 consumers notified at once35 | Threshold for regulator noticeMore than 1,000 consumers notified at one time (same for consumer reporting agencies)35 | Encryption safe harborYes, data elements encrypted, redacted or otherwise made unreadable or unusable are excluded from personal information35 |
| Montana Full page | StatuteMont. Code Ann. § 30-14-170436 | Enacted or effectiveEn. Sec. 7, Ch. 518, L. 2005; amended Ch. 180, L. 2007 and Ch. 62, L. 201536 | Who must notifyPersons and businesses conducting business in Montana that own or license computerized personal information36 | Notice to individualsWithout unreasonable delay, consistent with law enforcement needs and restoring system integrity36 | Notice to a state regulatorAttorney General's consumer protection office, simultaneously with individual notice: copy of notice plus date and method of distribution36 | Threshold for regulator noticeAny breach requiring individual notice (no minimum)36 | Encryption safe harborYes, notice applies only where the name or data elements were not encrypted36 |
| Nebraska Full page | StatuteNeb. Rev. Stat. § 87-803 (definitions in § 87-802)37 | Enacted or effectiveLaws 2006, LB 876, § 3; Laws 2016, LB835, § 2837 | Who must notifyIndividuals and commercial entities (including government bodies) doing business in Nebraska that own or license computerized personal information38 | Notice to individualsAs soon as possible and without unreasonable delay, after a prompt good-faith investigation37 | Notice to a state regulatorAttorney General, no later than the time residents are notified37 | Threshold for regulator noticeAny breach requiring resident notice (no minimum)37 | Encryption safe harborYes, unless the confidential process or key was, or is reasonably believed to have been, acquired in the breach38 |
| Nevada Full page | StatuteNev. Rev. Stat. § 603A.22039 | Enacted or effectiveAdded to NRS by 2005, 2504; amended 2023, 348139 | Who must notifyData collectors: government agencies, colleges, businesses and associations that own or license computerized personal information39 | Notice to individualsMost expedient time possible and without unreasonable delay; law enforcement may delay39 | Notice to a state regulatorNone required by this statute; nationwide consumer reporting agencies must be told without unreasonable delay if over 1,000 notified39 | Threshold for regulator noticeNot applicable: no regulator notice. Consumer reporting agencies if more than 1,000 persons notified at once39 | Encryption safe harborYes, notice covers unencrypted personal information only39 |
| New Hampshire Full page | StatuteN.H. Rev. Stat. Ann. § 359-C:20 (definitions in § 359-C:19)40 | Enacted or effective2006, 242:1, eff. Jan. 1, 200740 | Who must notifyPersons doing business in New Hampshire, including state agencies and political subdivisions, that own or license computerized personal information41 | Notice to individualsAs soon as possible after determining misuse is likely or cannot be ruled out; law enforcement may delay40 | Notice to a state regulatorAttorney General's office, or the primary regulator for regulated trade; no deadline stated, notice gives expected date and count40 | Threshold for regulator noticeAny breach requiring notice (no minimum); consumer reporting agencies if more than 1,000 consumers notified40 | Encryption safe harborYes, unless acquired together with the key, code or password needed to access it41 |
| New Jersey Full page | StatuteN.J. Stat. Ann. § 56:8-163 (definitions in § 56:8-161)42 | Enacted or effectiveEnacted by L.2005, c.226, s.12; amended 2019, c.95, s.242 | Who must notifyBusinesses conducting business in New Jersey and public entities (state and local) that compile or maintain computerized personal information42 | Notice to individualsMost expedient time possible and without unreasonable delay; not required if misuse is not reasonably possible (documented, kept five years)42 | Notice to a state regulatorDivision of State Police (Department of Law and Public Safety), before customers are notified42 | Threshold for regulator noticeAny breach requiring customer notice (no minimum); more than 1,000 persons also requires notice to nationwide consumer reporting agencies42 | Encryption safe harborYes, breach excludes data secured by encryption or other methods making it unreadable or unusable43 |
| New Mexico Full page | StatuteN.M. Stat. Ann. §§ 57-12C-1 to 57-12C-12 (Data Breach Notification Act; notice in § 57-12C-6, AG in § 57-12C-10)44 | Enacted or effectiveLaws 2017, ch. 36; effective June 16, 201744 | Who must notifyPersons owning or licensing personal identifying information of residents; state and political subdivisions exempt, as are persons subject to GLBA or HIPAA44 | Notice to individualsMost expedient time possible, no later than 45 calendar days after discovery; not required if no significant risk of identity theft or fraud44 | Notice to a state regulatorAttorney General, most expedient time possible and within 45 calendar days, with resident count and a copy of the notice44 | Threshold for regulator noticeMore than 1,000 residents in a single breach (same trigger for consumer reporting agencies)44 | Encryption safe harborYes, breach covers unencrypted data, or encrypted data taken with the key or process to decrypt it44 |
| New York | StatuteN.Y. Gen. Bus. Law § 899-aa45 | Enacted or effectiveNot confirmed (see Method) | Who must notifyAny person or business that owns or licenses computerized data including private information of New York residents45 | Notice to individualsMost expedient time possible and without unreasonable delay, and within 30 days after discovery, subject to law enforcement delay45 | Notice to a state regulatorAttorney General, Department of State and State Police whenever residents are notified; also DFS for 23 NYCRR 500 covered entities. Given without delaying resident notice45 | Threshold for regulator noticeAny breach requiring resident notice (no minimum); more than 5,000 residents at once also requires notice to consumer reporting agencies45 | Encryption safe harborYes, encrypted data elements are excluded from private information unless the encryption key was also accessed or acquired45 |
| North Carolina Full page | StatuteN.C. Gen. Stat. § 75-65 (definitions in § 75-61)46 | Enacted or effectiveEnacted by S.L. 2005-414; amended 2009 (S.L. 2009-355, 2009-573) and 2025 (S.L. 2025-25)46 | Who must notifyBusinesses that own or license personal information of residents in any form, including paper; government agencies are excluded from 'business'46 | Notice to individualsWithout unreasonable delay, allowing for law enforcement needs, scoping the breach and restoring system integrity46 | Notice to a state regulatorAttorney General's Consumer Protection Division, without unreasonable delay, whenever affected people are notified46 | Threshold for regulator noticeAny breach requiring individual notice (no minimum); over 1,000 people at once also triggers notice to nationwide consumer reporting agencies46 | Encryption safe harborYes, breach covers only unencrypted and unredacted data, unless the confidential process or key was also acquired47 |
| North Dakota | StatuteN.D. Cent. Code ch. 51-30 (§§ 51-30-01 to 51-30-07; notice in § 51-30-02)48 | Enacted or effectiveNot confirmed (see Method) | Who must notifyAny person that owns or licenses computerized data including personal information; persons maintaining data they do not own notify the owner48 | Notice to individualsMost expedient time possible and without unreasonable delay, subject to law enforcement needs and scoping the breach48 | Notice to a state regulatorAttorney General, by mail or email, in the most expedient time possible, for breaches exceeding 250 individuals48 | Threshold for regulator noticeMore than 250 individuals48 | Encryption safe harborYes, breach excludes data secured by encryption or other methods making it unreadable or unusable48 |
| Ohio Full page | StatuteOhio Rev. Code § 1349.1949 | Enacted or effectiveCurrent version effective March 30, 2007 (Senate Bill 126, 126th General Assembly)49 | Who must notifyPersons, including business entities conducting business in Ohio, that own or license computerized personal information; HIPAA covered entities and federally regulated financial institutions exempt49 | Notice to individualsMost expedient time possible, no later than 45 days after discovery or notification, subject to law enforcement needs49 | Notice to a state regulatorNone required by this statute; the Attorney General may investigate and sue49 | Threshold for regulator noticeNot applicable: no regulator notice. More than 1,000 residents in one breach requires notice to nationwide consumer reporting agencies49 | Encryption safe harborYes, data elements that are encrypted, redacted or otherwise made unreadable are excluded from personal information49 |
| Oklahoma Full page | StatuteOkla. Stat. tit. 24, § 163 (definitions in § 162); Security Breach Notification Act, §§ 161-16650 | Enacted or effectiveAdded by Laws 2008, c. 86, eff. November 1, 2008; amended by Laws 2025, c. 406, eff. January 1, 202650 | Who must notifyIndividuals or entities, including businesses, nonprofits and governments, that own or license computerized personal information of residents50 | Notice to individualsWithout unreasonable delay, allowing for law enforcement delay and measures to scope the breach and restore the system50 | Notice to a state regulatorAttorney General, without unreasonable delay and no later than 60 days after notifying residents50 | Threshold for regulator notice500 or more residents in a single breach (1,000 or more for a credit bureau)50 | Encryption safe harborYes, encrypted or redacted data is excluded unless acquired in readable form or the encryption key was obtained50 |
| Oregon Full page | StatuteOr. Rev. Stat. § 646A.604 (definitions in § 646A.602)51 | Enacted or effectiveEnacted 2007 (Or. Laws 2007 c.759 §3); amended 2015, 2018 and 2019 (2019 c.180 §3)51 | Who must notifyCovered entities: any person, including public bodies, that owns, licenses, maintains or otherwise possesses personal information in its business or activities; vendors notify the covered entity51 | Notice to individualsMost expeditious manner possible, without unreasonable delay, no later than 45 days after discovery or notice of the breach51 | Notice to a state regulatorAttorney General, in writing or electronically, when more than 250 consumers must be notified; vendors also notify the AG in some cases51 | Threshold for regulator noticeMore than 250 consumers; more than 1,000 also requires notice to nationwide consumer reporting agencies51 | Encryption safe harborYes, data rendered unusable by encryption or redaction is excluded, unless the encryption key was also acquired51 |
| Pennsylvania Full page | StatuteBreach of Personal Information Notification Act, Act of Dec. 22, 2005, P.L. 474, No. 94, § 352 | Enacted or effectiveAct of Dec. 22, 2005 (P.L. 474, No. 94), effective in 180 days; amended 2022 (No. 151) and June 28, 2024 (No. 33)52 | Who must notifyEntities: state agencies, political subdivisions, and individuals or businesses doing business in Pennsylvania that maintain, store or manage computerized personal information52 | Notice to individualsWithout unreasonable delay after determining the breach; state agencies, counties, public schools and municipalities within seven business days52 | Notice to a state regulatorOffice of Attorney General, concurrently with resident notice, when over 500 residents affected; state agencies always notify the AG; local bodies notify the district attorney52 | Threshold for regulator noticeMore than 500 residents; more than 500 notices at once also requires notice to nationwide consumer reporting agencies52 | Encryption safe harborYes, only unencrypted and unredacted data triggers notice, unless encryption is breached, data is taken unencrypted, or a key holder is involved52 |
| Rhode Island Full page | StatuteR.I. Gen. Laws § 11-49.3-4 (definitions in § 11-49.3-3)53 | Enacted or effectiveEnacted by P.L. 2015, ch. 138 and ch. 148; amended by P.L. 2023, ch. 375, effective June 27, 202353 | Who must notifyMunicipal agencies, state agencies and persons that store, own, collect, process, maintain, use or license personal information53 | Notice to individualsMost expedient time possible; no later than 30 days (agencies) or 45 days (others) after confirming the breach and the required notice details53 | Notice to a state regulatorAttorney General, without delaying resident notice, when more than 500 residents are to be notified53 | Threshold for regulator noticeMore than 500 residents (also triggers notice to major credit reporting agencies)53 | Encryption safe harborYes, breach covers unencrypted data; encryption means 128-bit or higher and fails if the key or password was also acquired54 |
| South Carolina Full page | StatuteS.C. Code Ann. § 39-1-9055 | Enacted or effective2008 Act No. 190, effective July 1, 2009; amended 2013 Act No. 15, effective April 23, 201355 | Who must notifyPersons conducting business in South Carolina that own or license computerized or other data with personal identifying information55 | Notice to individualsMost expedient time possible and without unreasonable delay; law enforcement may delay notice55 | Notice to a state regulatorConsumer Protection Division of the Department of Consumer Affairs, without unreasonable delay, plus nationwide consumer reporting agencies55 | Threshold for regulator noticeNotice to more than 1,000 persons at one time (same trigger for consumer reporting agencies)55 | Encryption safe harborYes, data rendered unusable through encryption, redaction or other methods is outside the breach definition55 |
| South Dakota Full page | StatuteS.D. Codified Laws §§ 22-40-19 to 22-40-26 (notice duty in § 22-40-20)56 | Enacted or effectiveEnacted by SL 2018, ch 13556 | Who must notifyInformation holders: persons or businesses conducting business in South Dakota that own or license computerized personal or protected information of residents57 | Notice to individualsNo later than 60 days after discovery or notification of the breach, unless law enforcement needs a longer period56 | Notice to a state regulatorAttorney General, by mail or email; AG notice also required before relying on a no-likely-harm determination56 | Threshold for regulator noticeBreach affecting more than 250 South Dakota residents56 | Encryption safe harborYes, encrypted data is excluded unless the encryption key was also acquired57 |
| Texas Full page | StatuteTex. Bus. & Com. Code § 521.053 (definitions in § 521.002)58 | Enacted or effectiveAdded by Acts 2007, 80th Leg., ch. 885, eff. April 1, 2009; last amended Acts 2023, 88th Leg., ch. 246 (S.B. 768), eff. September 1, 202358 | Who must notifyPersons conducting business in Texas that own or license computerized data including sensitive personal information58 | Notice to individualsWithout unreasonable delay and no later than 60 days after determining the breach occurred; law enforcement may delay58 | Notice to a state regulatorAttorney General, as soon as practicable and within 30 days of determining the breach, using the AG's online form58 | Threshold for regulator noticeAt least 250 Texas residents; consumer reporting agencies when more than 10,000 persons are notified at once58 | Encryption safe harborYes, unencrypted name-plus-data defines covered data; encrypted data counts only if the accessor has the decryption key58 |
| Utah Full page | StatuteUtah Code § 13-44-202 (definitions in § 13-44-102)59 | Enacted or effectiveCurrent version effective May 1, 2024; amended by Chapter 426, 2024 General Session59 | Who must notifyPersons that own or license computerized data including personal information of Utah residents59 | Notice to individualsMost expedient time possible without unreasonable delay, after scoping the breach and restoring system integrity; law enforcement may delay59 | Notice to a state regulatorOffice of the Attorney General and the Utah Cyber Center; no separate deadline is stated59 | Threshold for regulator noticeLikely misuse affecting 500 or more Utah residents; consumer reporting agencies at 1,000 or more59 | Encryption safe harborYes, data counts as personal information only when the name or data element is unencrypted or otherwise unprotected60 |
| Vermont Full page | Statute9 V.S.A. § 2435 (Security Breach Notice Act; definitions in § 2430)61 | Enacted or effectiveAdded 2005, No. 162 (Adj. Sess.), eff. Jan. 1, 2007; amended through 2019, No. 89 (Adj. Sess.); revised by 2025, No. 138 (Adj. Sess.), eff. Jan. 1, 202761 | Who must notifyData collectors owning or licensing computerized personal information or login credentials, including the State, state agencies, political subdivisions, universities and businesses62 | Notice to individualsMost expedient time possible without unreasonable delay, and no later than 45 days after discovery or notification61 | Notice to a state regulatorAttorney General, or Department of Financial Regulation for its licensees: preliminary notice within 14 business days, or before consumer notice if sooner61 | Threshold for regulator noticeAny breach (no minimum); consumer reporting agencies when more than 1,000 consumers are notified at once61 | Encryption safe harborYes, data elements that are encrypted, redacted or otherwise made unreadable are outside 'personally identifiable information'62 |
| Virginia Full page | StatuteVa. Code Ann. § 18.2-186.663 | Enacted or effective2008, cc. 566, 801; amended 2017, cc. 419, 427; 2019, c. 484; 2020, c. 26463 | Who must notifyIndividuals and entities owning or licensing computerized personal information; 'entity' includes businesses, nonprofits, governments and agencies63 | Notice to individualsWithout unreasonable delay; reasonable delay allowed to scope the breach and restore the system, or at law enforcement's request63 | Notice to a state regulatorOffice of the Attorney General, without unreasonable delay, for every notifiable breach; also on notices to more than 1,000 persons63 | Threshold for regulator noticeAny notifiable breach (no minimum); consumer reporting agencies when more than 1,000 persons are notified at once63 | Encryption safe harborYes, unless data is acquired in unencrypted form or the breach involves someone with access to the encryption key63 |
| Washington Full page | StatuteRCW 19.255.010 (definitions in RCW 19.255.005)64 | Enacted or effective2005 c 368; amended 2015 c 64 and 2019 c 241, which took effect March 1, 202064 | Who must notifyPersons or businesses conducting business in Washington that own or license data including personal information64 | Notice to individualsMost expedient time possible, without unreasonable delay, and no more than 30 calendar days after discovery64 | Notice to a state regulatorAttorney General, no more than 30 days after the breach was discovered64 | Threshold for regulator noticeNotice to more than 500 Washington residents from a single breach64 | Encryption safe harborYes, secured (NIST-standard encrypted) data is exempt unless the key or other means to decipher it was acquired64 |
| West Virginia Full page | StatuteW. Va. Code §§ 46A-2A-101 to 46A-2A-105 (notice duty in § 46A-2A-102)65 | Enacted or effectiveEnacted by Enrolled Committee Substitute for Senate Bill 340, 2008 Regular Session (per the section's bill history)65 | Who must notifyIndividuals and entities owning or licensing computerized personal information; 'entity' includes businesses, nonprofits, governments and agencies66 | Notice to individualsWithout unreasonable delay, allowing time to scope the breach and restore the system; law enforcement may delay65 | Notice to a state regulatorNone required by this statute; the Attorney General enforces it65 | Threshold for regulator noticeNot applicable: no regulator notice; consumer reporting agencies when more than 1,000 persons are notified65 | Encryption safe harborYes, unless data is acquired in unencrypted form or the breach involves someone with access to the encryption key65 |
| Wisconsin Full page | StatuteWis. Stat. § 134.9867 | Enacted or effectiveCreated by 2005 Wis. Act 138; amended 2007 Wis. Acts 20 and 9767 | Who must notifyNon-individual entities doing business in, or maintaining or licensing personal information in, Wisconsin; lenders and depository institutions; the state and cities, villages, towns and counties67 | Notice to individualsWithin a reasonable time, not more than 45 days after learning of the acquisition; law enforcement may delay67 | Notice to a state regulatorNone required by this statute67 | Threshold for regulator noticeNot applicable: no regulator notice; consumer reporting agencies when 1,000 or more individuals are notified from one incident67 | Encryption safe harborYes, elements that are encrypted, redacted or altered to be unreadable are outside 'personal information'67 |
| Wyoming | StatuteWyo. Stat. Ann. §§ 40-12-501 (definitions) and 40-12-502 (breach notice)68 | Enacted or effectiveNot confirmed (see Method) | Who must notifyIndividuals and commercial entities conducting business in Wyoming that own or license computerized personal identifying information of residents68 | Notice to individualsAs soon as possible, in the most expedient time and without unreasonable delay, after an investigation finds likely misuse68 | Notice to a state regulatorNone required by this statute; the Attorney General may sue to enforce it68 | Threshold for regulator noticeNot applicable: no regulator notice68 | Encryption safe harborNo express encryption exemption; only redacted data elements fall outside 'personal identifying information'68 |
Not yet in this matrix
Arkansas, California, Tennessee: we could not open and confirm the official text yet, so these rows are left out (see Method).
Method
For each state and the District of Columbia we opened the general data breach notification statute on November 13, 2026 (and re-opened every source to check each cell on November 14, 2026) on the legislature's own website or files (for Mississippi, whose code is only on a commercial host, the legislature's enacted bill text; for New Mexico, the official compilation published by the New Mexico Compilation Commission), and recorded in our own words who must notify, when individuals must be told, whether a state regulator must be told and from what number of residents, and whether encrypted data is exempt. The enactment or effective date is shown only where the official page states it. A cell we could not confirm in the text we opened is marked Not confirmed and logged; a jurisdiction whose statute text we could not open from an official source is left out of the matrix until it can be. Sector rules (insurance, health, banking) and separate laws for public bodies are not covered unless a cell says so.
Omitted
What was left out, and why.
- Alaska · Enacted or effective: The akleg.gov statute print view shows no history note or effective date
- Arizona · Enacted or effective: The azleg.gov section pages carry no history note or effective date
- Arkansas · whole row: The current Arkansas Code is published officially only through a LexisNexis-hosted site (a commercial host; this matrix cites government sources only). arkleg.state.ar.us gives session acts such as Act 1030 of 2019, which amend Ark. Code 4-110-101 et seq. but do not give the full current text. Retried November 14, 2026, with no official consolidated text found.
- California · whole row: leginfo.legislature.ca.gov section and bill-text pages returned a Cloudflare challenge (HTTP 403) to both curl and a headless browser on November 13 and 14, 2026, so no statute text was readable; the only other official copy of the code is the Legislature's 1.1 GB bulk database download, not a citable section page. The AG page oag.ca.gov/privacy/databreach/reporting only summarizes the law.
- Maryland · Enacted or effective: The statute text pages (with and without enactments) show no history note or effective date
- Massachusetts · Enacted or effective: The section page shows no history note or effective date
- New York · Enacted or effective: The official section text opened has no history note or enactment date; nysenate.gov section page blocked automated access
- North Dakota · Enacted or effective: The official chapter PDF carries no history note or enactment date
- Tennessee · whole row: Tennessee's official consolidated code text (Tenn. Code Ann. 47-18-2107) is published only through LexisNexis, a commercial host. On November 14, 2026, the Secretary of State's session-law PDF for Public Chapter 692 of 2016 opened, but it amends only parts of the section (subsections (b) to (d) and (i)); the definitions and any later amendments are not in it, so the row cannot be fully sourced.
- Wyoming · Enacted or effective: The official title PDF prints no history or effective-date note for sections 40-12-501 and 40-12-502
Notes
- This matrix describes what each statute says; it is not legal advice and does not say what any organization must do.
Sources
- Alabama Legislature (ALISON). Code of Alabama Title 8, Chapter 38, sections 8-38-1 to 8-38-12 (read through the ALISON code service). Checked .
- Alaska State Legislature. Alaska Statutes AS 45.48.010 to 45.48.090 (Breach of Security Involving Personal Information). Checked .
- Arizona State Legislature. Arizona Revised Statutes section 18-551 (Definitions). Checked .
- Arizona State Legislature. Arizona Revised Statutes section 18-552 (Notification of security system breaches). Checked .
- Colorado General Assembly, Office of Legislative Legal Services. Colorado Revised Statutes 2024, Title 6 (section 6-1-716, Notification of security breach), official PDF edition. Checked .
- Connecticut General Assembly. Connecticut General Statutes chapter 669, section 36a-701b. Checked .
- Delaware General Assembly (Delaware Code Online). Delaware Code Title 6, Chapter 12B (Computer Security Breaches). Checked .
- Council of the District of Columbia (D.C. Law Library). D.C. Code § 28-3851 (Definitions). Checked .
- Council of the District of Columbia (D.C. Law Library). D.C. Code § 28-3852 (Notification of security breach). Checked .
- The Florida Legislature (Online Sunshine). Florida Statutes section 501.171 (Security of confidential personal information). Checked .
- Georgia General Assembly (published under authority of the State of Georgia by the Code Revision Commission). Official Code of Georgia Annotated, Volume 8, Title 10 (2024 Edition), §§ 10-1-911 and 10-1-912. Checked .
- Hawaii State Legislature. Hawaii Revised Statutes §487N-2, Notice of security breach. Checked .
- Hawaii State Legislature. Hawaii Revised Statutes §487N-1, Definitions. Checked .
- Idaho Legislature. Idaho Code 28-51-105, Disclosure of breach of security of computerized personal information. Checked .
- Idaho Legislature. Idaho Code 28-51-104, Definitions. Checked .
- Illinois General Assembly. 815 ILCS 530, Personal Information Protection Act (full Act). Checked .
- Indiana General Assembly. Indiana Code 2026, IC 24-4.9, Disclosure of Security Breach (article PDF). Checked .
- Iowa Legislature. Iowa Code 2026, Chapter 715C, Personal Information Security Breach Protection. Checked .
- Kansas State Legislature, Revisor of Statutes. K.S.A. 50-7a02, Security breach; requirements. Checked .
- Kansas State Legislature, Revisor of Statutes. K.S.A. 50-7a01, Consumer information; security breach; definitions. Checked .
- Kentucky General Assembly, Legislative Research Commission. KRS 365.732, Notification to affected persons of computer security breach. Checked .
- Louisiana State Legislature. Louisiana Revised Statutes 51:3074, Protection of personal information; disclosure upon breach. Checked .
- Louisiana State Legislature. Louisiana Revised Statutes 51:3073, Definitions. Checked .
- Maine Legislature, Office of the Revisor of Statutes. Maine Revised Statutes Title 10, §1348: Security breach notice requirements. Checked .
- Maine Legislature, Office of the Revisor of Statutes. Maine Revised Statutes Title 10, §1347: Definitions. Checked .
- Maryland General Assembly. Maryland Code, Commercial Law § 14-3504. Checked .
- Maryland General Assembly. Maryland Code, Commercial Law § 14-3501 (definitions). Checked .
- The General Court of the Commonwealth of Massachusetts. Massachusetts General Laws, Part I, Title XV, Chapter 93H, Section 3. Checked .
- The General Court of the Commonwealth of Massachusetts. Massachusetts General Laws, Part I, Title XV, Chapter 93H, Section 1 (definitions). Checked .
- Michigan Legislature. Michigan Compiled Laws section 445.72. Checked .
- Michigan Legislature. Michigan Compiled Laws section 445.63 (definitions). Checked .
- Minnesota Office of the Revisor of Statutes. Minnesota Statutes section 325E.61 (2026). Checked .
- Mississippi Legislature. House Bill 277 (As Sent to Governor), 2021 Regular Session, Section 9 amending Section 75-24-29. Checked .
- Mississippi Legislature. House Bill 583 (As Sent to Governor), 2010 Regular Session. Checked .
- Missouri Revisor of Statutes. Missouri Revised Statutes section 407.1500. Checked .
- Montana Legislature. Montana Code Annotated 2025, section 30-14-1704. Checked .
- Nebraska Legislature. Nebraska Revised Statutes 87-803. Checked .
- Nebraska Legislature. Nebraska Revised Statutes 87-802 (definitions). Checked .
- Nevada Legislature. Nevada Revised Statutes chapter 603A (NRS 603A.030, 603A.220). Checked .
- New Hampshire General Court. New Hampshire RSA 359-C:20. Checked .
- New Hampshire General Court. New Hampshire RSA 359-C:19 (definitions). Checked .
- New Jersey Legislature. New Jersey Statutes 56:8-163, Disclosure of breach of security to customers (Legislature statutes database search for the section). Checked .
- New Jersey Legislature. New Jersey Statutes 56:8-161, Definitions relative to security of personal information (Legislature statutes database search for the section). Checked .
- New Mexico Compilation Commission (NMOneSource). NMSA 1978 Chapter 57 (Trade Practices and Regulations), Article 12C, Data Breach Notification Act. Checked .
- New York State Senate (Open Legislation). New York General Business Law § 899-aa (PDF of section text). Checked .
- North Carolina General Assembly. North Carolina General Statutes § 75-65, Protection from security breaches. Checked .
- North Carolina General Assembly. North Carolina General Statutes § 75-61, Definitions. Checked .
- North Dakota Legislative Branch. North Dakota Century Code chapter 51-30, Notice of Security Breach for Personal Information. Checked .
- Ohio Legislative Service Commission (Ohio Laws). Ohio Revised Code section 1349.19, Private disclosure of security breach of computerized personal information data. Checked .
- Oklahoma Legislature. Oklahoma Statutes, Title 24 (complete title), sections 161 to 166: Security Breach Notification Act. Checked .
- Oregon State Legislature. Oregon Revised Statutes chapter 646A (2025 edition), sections 646A.602 and 646A.604. Checked .
- Pennsylvania General Assembly. Breach of Personal Information Notification Act, Act of Dec. 22, 2005, P.L. 474, No. 94, as amended (unconsolidated statute, PDF). Checked .
- State of Rhode Island General Assembly. Rhode Island General Laws § 11-49.3-4, Notification of breach. Checked .
- State of Rhode Island General Assembly. Rhode Island General Laws § 11-49.3-3, Definitions. Checked .
- South Carolina Legislature (Legislative Services Agency). South Carolina Code of Laws Title 39 Chapter 1 (section 39-1-90). Checked .
- South Dakota Legislature (Legislative Research Council). South Dakota Codified Laws 22-40-20 (Notice of breach of system security). Checked .
- South Dakota Legislature (Legislative Research Council). South Dakota Codified Laws 22-40-19 (Definitions). Checked .
- Texas Legislature (Texas Constitution and Statutes, Texas Legislative Council). Texas Business and Commerce Code Chapter 521 (sections 521.002 and 521.053). Checked .
- Utah State Legislature. Utah Code Section 13-44-202 (Personal information -- Disclosure of system security breach). Checked .
- Utah State Legislature. Utah Code Section 13-44-102 (Definitions). Checked .
- Vermont General Assembly. 9 V.S.A. § 2435 Notice of security breaches. Checked .
- Vermont General Assembly. 9 V.S.A. § 2430 Definitions. Checked .
- Virginia General Assembly (Legislative Information System). Code of Virginia § 18.2-186.6 Breach of personal information notification. Checked .
- Washington State Legislature. Chapter 19.255 RCW, Personal information: notice of security breaches (RCW 19.255.005 and 19.255.010). Checked .
- West Virginia Legislature. West Virginia Code § 46A-2A-102 Notice of breach of security of computerized personal information. Checked .
- West Virginia Legislature. West Virginia Code § 46A-2A-101 Definitions. Checked .
- Wisconsin State Legislature (Legislative Reference Bureau). Wisconsin Statutes § 134.98 Notice of unauthorized acquisition of personal information. Checked .
- Wyoming State Legislature. Wyoming Statutes Title 40 (Trade and Commerce), sections 40-12-501 and 40-12-502. Checked .
How we source and check every fact: Editorial standards · Corrections
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Last reviewed .
Spotted an error? Tell us and we will check it and correct the page where needed.