Data Protection Monitor
Global Privacy & Data Protection Intelligence

Ohio, USA Data Protection & Privacy Regulation

US-OH schema gdpri-v2 trajectory: not yet assessed regulated (sectoral) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 49 claims · 34 sources in the cumulative register

Ohio's data-protection enforcement and redress posture saw a discrete legislative development this cycle: House Bill 801, introduced March 27, 2026 by Representative Allison Russo, would bar Ohio state government entities from collecting, recording, or sharing residents' personal or identifying information with out-of-state entities except where required or permitted by law.

Data collected Data published

AI-assembled from cited sources

Not covered: Cross-Border & Adequacy. Not fully checked this cycle: Regulator & Framework, Algorithmic, Biometric & Surveillance Governance (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 8 binding instruments
Supervisory authorityOhio Attorney General
Next milestoneNo upcoming dated milestone on record
Record & confidence mix49 claims · 33 sources · machine-compiled
5 Confirmed39 Probable4 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

United States federal law that applies in Ohio, USA is covered once, on the United States page. This page covers Ohio, USA’s own layer: its own law, regulators and enforcement.

Jurisdiction brief

Latest update · 25 October 2026

Lead Signal

Ohio's dominant data-protection signal is the disclosure by Central Ohio Primary Care Physicians of a breach affecting approximately 1.4 million patients and employees. COPC discovered the incident on 25 August 2026 and disclosed it on 15 October 2026, confirming that exposed information includes names, addresses, Social Security numbers, financial information, and limited health-related patient data. The disclosure triggers notification duties under Ohio Revised Code 1349.19, which requires businesses to notify affected Ohio residents of a breach of unencrypted personal information in the most expedient time possible and no later than forty-five days after discovery, with a parallel duty to notify nationwide consumer reporting agencies without unreasonable delay where more than one thousand Ohio residents are affected at one time. Reporting attributes the incident's origin to a voice-phishing, or vishing, social-engineering attack associated with a ransomware group identified as 'Chaos'; COPC's Epic MyChart patient portal was reported as unaffected. No Ohio Attorney General enforcement notice specific to this matter has been located.

Key regulatory facts for Ohio, USA
Key regulatory facts for Ohio, USA
Regulatory DimensionOhio, USA Standing Position
JurisdictionOhio, USA (US-OH)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 49 sourced findings)
Regulator & FrameworkA real, enforceable framework exists (federal FTC Act + Ohio breach-notification statute + AG consumer-protection authority) but it is narrow, sectoral and reactive rather than a comprehensive omnibus regime — amber reflects partial, non-comprehensive coverage rather than a total gap.
Lawful Processing & Special DataNo enumerated lawful bases, no general consent standard, and no special-category regime exist under Ohio or applicable sectoral-federal law outside of narrow sector carve-outs (e.g., HIPAA for health data, which is a federal sectoral overlay tracked separately).
Data Subject RightsNo omnibus consumer-rights statute exists in Ohio; this is a genuine, confirmed regulatory gap rather than an under-researched area.
Controller/Processor DutiesBreach notification is a binding, in-force obligation (amber-to-green on that narrow point) but accountability/DPIA/DPO/ROPA/security-mandate infrastructure that exists in omnibus regimes is entirely voluntary or absent in Ohio, pulling the module rating to amber overall.
Primary Instruments CitedCommoner Law, Ohio, USA Official Instrument (dinsmore.com ohio-law-imposes-new-cybersecuri), AI Law Tracker, IAPP, IAPP
Last Confirmed / Updated (34 sources in cumulative register)

#

A real, enforceable framework exists (federal FTC Act + Ohio breach-notification statute + AG consumer-protection authority) but it is narrow, sectoral and reactive rather than a comprehensive omnibus regime — amber reflects partial, non-comprehensive coverage rather than a total gap.

Primary frameworkFTC Act Section 5 (federal) + Ohio Revised Code §1349.19 (breach notification) + Ohio Data Protection Act, ORC Ch. 1354 (voluntary cybersecurity safe harbor)
Supervisory authorityOhio Attorney General
Traffic-light rationale — AmberA real, enforceable framework exists (federal FTC Act + Ohio breach-notification statute + AG consumer-protection authority) but it is narrow, sectoral and reactive rather than a comprehensive omnibus regime — amber reflects partial, non-comprehensive coverage rather than a total gap.

Sub-modules (5)

Regulator and authorityAmber

The Ohio Attorney General enforces the state's consumer-protection and breach-notification statutes; there is no dedicated Ohio privacy regulator with rulemaking authority analogous to a DPA.

Claims (3):

  • The Ohio Attorney General is the principal state enforcement authority for consumer-protection and data-breach matters in Ohio, operating without a dedicated omnibus privacy statute.
  • ORC 1349.191 gives the Ohio Attorney General investigative authority over suspected breach-notification violations, and ORC 1349.192 authorizes a civil enforcement action; the AG may also seek declaratory judgments and injunctions under the Consumer Sales Practices Act where a data practice is unfair or deceptive.
  • Ohio Attorney General — May investigate and bring a civil action for an alleged failure to comply with the breach-notification statute under R.C. 1349.191 and 1349.192

Act and instrumentsAmber

Instruments in force: FTC Act §5 (federal baseline); ORC §1349.19 breach-notification statute; Ohio Data Protection Act (2018 SB 220, effective 2018-11-02) voluntary cybersecurity safe harbor. A comprehensive Ohio Personal Privacy Act (HB 376) was introduced in 2021 but was placed on hold and has not been re-enacted.

Claims (5):

  • The FTC Act's Section 5 general unfair/deceptive-practices authority applies nationally, including to entities operating in Ohio, as the federal baseline for privacy-adjacent enforcement absent a comprehensive statute.
  • The Ohio Data Protection Act (2018 SB 220) was launched as part of the Ohio Attorney General's CyberOhio Initiative and went into effect on 2 November 2018, offering a voluntary cybersecurity safe harbor rather than mandatory minimum security standards.
  • Ohio's comprehensive consumer-privacy bill, the Ohio Personal Privacy Act (House Bill 376), was introduced in 2021 but was placed on hold, and no comprehensive Ohio consumer-privacy statute has been enacted as of mid-2026 (Ohio is not among the 19 states listed as having enacted comprehensive privacy laws).
  • Ohio Data Protection Act (SB 220) / Security Breach Notification Act — Ohio relies on a patchwork of targeted laws — a voluntary cybersecurity safe harbor, breach-notification requirement, government data-practices rules, insurance data-security standards, and Consumer Sales Practices Act enforcement — rather than a single comprehensive consumer privacy statute
  • Ohio — A comprehensive consumer data-privacy statute; its patchwork consists of the breach-notification statute (R.C. 1349.19) and the voluntary cybersecurity safe-harbor (R.C. Chapter 1354)

Material scopeAmber

Ohio's breach statute covers only a narrow definition of 'personal information' (name plus SSN/driver's license/financial account identifiers) rather than the broad 'personal data' concept used in omnibus regimes.

Claims (1):

  • Ohio's breach-notification statute (ORC §1349.19) defines covered 'personal information' narrowly — an individual's name combined with identifiers such as Social Security number, driver's license number, or financial account/access data — narrower than the 'personal data' concept in omnibus regimes.

Territorial scopeAmber

Consistent with the general pattern of US state breach-notification statutes, Ohio's law applies to any entity holding covered personal information of Ohio residents regardless of where the entity is established.

Claims (1):

  • US state breach-notification statutes, including Ohio's, generally apply to any organization holding covered personal information of that state's residents regardless of the organization's place of establishment.

Regulator registration and filingRed

No controller/processor registration or filing regime exists in Ohio; there is no omnibus statute establishing such an obligation.

Category narrative 82 words

Ohio has no dedicated data-protection regulator or comprehensive privacy statute. The governing framework is a composite of (a) the FTC's general Section 5 unfair/deceptive-practices authority, which applies nationally including Ohio, and (b) Ohio-specific instruments limited to breach notification (ORC §1349.19 and related §§1347.12, 1349.191-.192) and a voluntary cybersecurity safe-harbor statute (the Ohio Data Protection Act, 2018 SB 220). The Ohio Attorney General is the principal state-level enforcement actor for consumer-protection/privacy-adjacent matters, operating under general consumer-protection authority rather than a dedicated privacy statute.

Sources and claims (10)
  1. Probable NAAG — The Ohio Attorney General is the principal state enforcement authority for consumer-protection and data-breach matters in Ohio, operating without a dedicated omnibus privacy statute. observed
  2. Confirmed Federal Trade Commission — The FTC Act's Section 5 general unfair/deceptive-practices authority applies nationally, including to entities operating in Ohio, as the federal baseline for privacy-adjacent enforcement absent a comprehensive statute. observed
  3. Confirmed IAPP — The Ohio Data Protection Act (2018 SB 220) was launched as part of the Ohio Attorney General's CyberOhio Initiative and went into effect on 2 November 2018, offering a voluntary cybersecurity safe harbor rather than mandatory minimum security standards. observed
  4. Confirmed IAPP — Ohio's comprehensive consumer-privacy bill, the Ohio Personal Privacy Act (House Bill 376), was introduced in 2021 but was placed on hold, and no comprehensive Ohio consumer-privacy statute has been enacted as of mid-2026 (Ohio is not among the 19 states listed as having enacted comprehensive privacy laws). observed
  5. Probable DataGuidance (OneTrust) — Ohio's breach-notification statute (ORC §1349.19) defines covered 'personal information' narrowly — an individual's name combined with identifiers such as Social Security number, driver's license number, or financial account/access data — narrower than the 'personal data' concept in omnibus regimes. observed
  6. Probable DataGuidance (OneTrust) — US state breach-notification statutes, including Ohio's, generally apply to any organization holding covered personal information of that state's residents regardless of the organization's place of establishment. observed
  7. High RecordingLaw — Ohio Data Protection Act (SB 220) / Security Breach Notification Act — Ohio relies on a patchwork of targeted laws — a voluntary cybersecurity safe harbor, breach-notification requirement, government data-practices rules, insurance data-security standards, and Consumer Sales Practices Act enforcement — rather than a single comprehensive consumer privacy statute observed
  8. Probable recordinglaw.com — ORC 1349.191 gives the Ohio Attorney General investigative authority over suspected breach-notification violations, and ORC 1349.192 authorizes a civil enforcement action; the AG may also seek declaratory judgments and injunctions under the Consumer Sales Practices Act where a data practice is unfair or deceptive. observed
  9. Confirmed recordinglaw.com — Ohio Attorney General — May investigate and bring a civil action for an alleged failure to comply with the breach-notification statute under R.C. 1349.191 and 1349.192 observed
  10. Confirmed recordinglaw.com — Ohio — A comprehensive consumer data-privacy statute; its patchwork consists of the breach-notification statute (R.C. 1349.19) and the voluntary cybersecurity safe-harbor (R.C. Chapter 1354) observed

#

No enumerated lawful bases, no general consent standard, and no special-category regime exist under Ohio or applicable sectoral-federal law outside of narrow sector carve-outs (e.g., HIPAA for health data, which is a federal sectoral overlay tracked separately).

Traffic-light rationale — RedNo enumerated lawful bases, no general consent standard, and no special-category regime exist under Ohio or applicable sectoral-federal law outside of narrow sector carve-outs (e.g., HIPAA for health data, which is a federal sectoral overlay tracked separately).

Sub-modules (4)

Lawful basesRed

No enumerated lawful-basis framework (GDPR Art 6 analogue) exists under Ohio or general US federal law; processing legality is instead tested reactively against FTC Act §5 unfairness/deception standards.

Claims (1):

  • Ohio has no enumerated lawful-basis statute analogous to GDPR Article 6; general commercial data processing is regulated reactively via FTC Act Section 5 unfair/deceptive-practices review rather than a proactive lawful-basis requirement.

Special categoriesRed

No general statutory 'special category' data regime exists in Ohio; sensitive-data protections are confined to sector overlays (health via HIPAA, financial via GLBA) tracked under sectoral_watch.

Pseudonymisation and anonymisationRed

No Ohio statutory definition or safe harbor for pseudonymisation/anonymisation exists; the Ohio Data Protection Act's safe harbor concerns cybersecurity-program conformity, not data de-identification.

Category narrative 72 words

Ohio has no GDPR-style enumerated lawful-basis regime. Processing is governed by sector-specific notice-and-consent/opt-out models (e.g., GLBA opt-out for financial nonpublic personal information) and general FTC deception/unfairness review, rather than an affirmative lawful-basis test. There is no general statutory definition of 'special category' data or a codified pseudonymisation/anonymisation safe harbor at the state level; the Ohio Data Protection Act references NIST/HIPAA/GLBA/FISMA/PCI security frameworks but these govern security posture, not lawful-basis or special-category classification.

Sources and claims (2)
  1. Confirmed Federal Trade Commission — Ohio has no enumerated lawful-basis statute analogous to GDPR Article 6; general commercial data processing is regulated reactively via FTC Act Section 5 unfair/deceptive-practices review rather than a proactive lawful-basis requirement. observed
  2. Confirmed IAPP — Under GLBA Title V, financial institutions must provide privacy notices and an opportunity for consumers to opt out of certain disclosures of nonpublic personal information to nonaffiliated third parties — an opt-out consent model rather than an opt-in/affirmative-consent standard. observed

#

No omnibus consumer-rights statute exists in Ohio; this is a genuine, confirmed regulatory gap rather than an under-researched area.

Traffic-light rationale — RedNo omnibus consumer-rights statute exists in Ohio; this is a genuine, confirmed regulatory gap rather than an under-researched area.

Sub-modules (5)

Access rightRed

No general right of access to personal data held by commercial entities exists under Ohio law.

Claims (2):

  • Ohio has not enacted a comprehensive consumer-privacy statute and therefore confers no general statutory right of access to personal data held by commercial entities; Ohio is absent from the list of 19 US states with enacted comprehensive privacy laws as of the most recent tracking.
  • Ohio residents have none of the access, correction, deletion, or opt-out-of-sale rights against private businesses that more than 20 comprehensive state privacy laws grant, as of May 2026

Rectification and erasureRed

No general right to correct or delete personal data exists under Ohio law absent sector-specific carve-outs.

Restriction and objectionRed

No general right to restrict processing or object to processing/profiling exists under Ohio law.

Data portabilityRed

No statutory data-portability right exists under Ohio law.

Deadlines and response windowsRed

Because no general consumer data-subject-rights regime exists, there are no associated statutory response-window deadlines in Ohio (breach-notification timing is tracked under controller_processor_duties.breach_notification, which is a distinct obligation).

Category narrative 53 words

Ohio confers no general statutory access, rectification, erasure, restriction, objection, or portability rights on consumers with respect to commercial data processing. Such rights exist only within narrow federal sectoral carve-outs (e.g., HIPAA access rights for designated health records), which are tracked under sectoral_watch rather than as a general consumer right in this JID.

Sources and claims (2)
  1. Confirmed IAPP — Ohio has not enacted a comprehensive consumer-privacy statute and therefore confers no general statutory right of access to personal data held by commercial entities; Ohio is absent from the list of 19 US states with enacted comprehensive privacy laws as of the most recent tracking. observed
  2. High RecordingLaw — Ohio residents have none of the access, correction, deletion, or opt-out-of-sale rights against private businesses that more than 20 comprehensive state privacy laws grant, as of May 2026 observed

#

Breach notification is a binding, in-force obligation (amber-to-green on that narrow point) but accountability/DPIA/DPO/ROPA/security-mandate infrastructure that exists in omnibus regimes is entirely voluntary or absent in Ohio, pulling the module rating to amber overall.

Primary frameworkOhio Data Protection Act (ORC Ch. 1354, voluntary safe harbor) + ORC §1349.19 breach notification (mandatory)
Supervisory authorityOhio Attorney General
Traffic-light rationale — AmberBreach notification is a binding, in-force obligation (amber-to-green on that narrow point) but accountability/DPIA/DPO/ROPA/security-mandate infrastructure that exists in omnibus regimes is entirely voluntary or absent in Ohio, pulling the module rating to amber overall.

Sub-modules (7)

Accountability & DPIARed

No mandatory accountability principle or DPIA-trigger regime exists in Ohio; the Data Protection Act's cybersecurity-program element is voluntary and tied only to litigation safe harbor, not a standalone compliance duty.

Claims (1):

  • The Ohio Data Protection Act explicitly does not set minimum data-security standards or impose liability on businesses that fail to maintain a conforming cybersecurity program; compliance is voluntary and incentive-based rather than a mandatory accountability duty.

DPO requirementsRed

No DPO appointment threshold or independence requirement exists under Ohio law.

Ropa requirementsRed

No records-of-processing-activities obligation exists under Ohio law.

Joint controller arrangementsRed

No statutory joint-controller framework exists under Ohio law.

Security measuresAmber

The Ohio Data Protection Act incentivizes, via an affirmative tort defense, businesses to create and maintain a written cybersecurity program reasonably conforming to one of several named industry frameworks, but it does not itself impose mandatory minimum security standards or liability for non-compliance.

Claims (5):

  • To qualify for the Ohio Data Protection Act's affirmative-defense safe harbor, a covered entity must create, maintain, and comply with a written cybersecurity program that reasonably conforms to one of several named frameworks, including the NIST Cybersecurity Framework and NIST SP 800-53/800-53A/800-171.
  • Recognized cybersecurity frameworks that qualify an entity for the Ohio Data Protection Act's safe harbor also include the HIPAA Security Rule, GLBA Title V, FISMA, and the PCI Data Security Standard.
  • Under Ohio Rev. Code Ch. 1354 (Ohio Data Protection Act), a covered entity qualifies for an affirmative-defense safe harbor against Ohio tort claims alleging failure to implement reasonable security controls only if it creates, maintains and reasonably conforms its cybersecurity program to an industry-recognized framework; the amended version of this law took effect Nov. 2 (year of amendment not confirmed this cycle).
  • Ohio Data Protection Act covered entities — Written cybersecurity program reasonably conforming to an industry-recognised framework, scaled per R.C. 1354.02(C), as a voluntary affirmative defense carrying no private right of action (R.C. 1354.04)
  • Ohio Rev. Code Chapter 1354 gives covered entities with a conforming written cybersecurity program an affirmative defense to tort claims for breach, on a voluntary basis.

Breach notificationGreen

Ohio's breach-notification statute (ORC §1349.19, with related provisions at §§1347.12, 1349.191-.192) mandates notification obligations in the event of a security breach involving computerized personal information, but is confined to notification and does not create broader consumer privacy rights.

Claims (6):

  • Ohio's data-breach notification statute addresses notification obligations only and does not establish comprehensive consumer privacy rights such as access, deletion, or opt-out.
  • Central Ohio Primary Care Physicians disclosed on 2026-10-15 a cyberattack discovered 2026-08-25 that exposed personal information (names, addresses, SSNs, financial data, limited health data) of approximately 1.4 million patients and employees; notices are being mailed to affected individuals under ORC 1349.19.
  • Ohio Security Breach Notification Act (ORC 1349.19) — Requires notification of affected consumers within 45 days of discovering a breach involving personal or sensitive information, with credit-bureau notification required if more than 1,000 Ohio residents are affected
  • Ohio Rev. Code 1349.19 — Requires notification to affected Ohio residents 'in the most expedient time possible' and no later than 45 days after discovery of a breach causing a material risk of identity theft or fraud; notification to consumer-reporting agencies required if more than 1,000 residents are affected. Financial institutions subject to GLBA are exempt.
  • Ohio businesses holding computerized personal information — A breach of the security of the system in the most expedient time possible but not later than 45 days following discovery, subject to law-enforcement delay (R.C. 1349.19(B)(2))
  • Ohio Rev. Code 1349.19 requires notification of a data breach to affected Ohio residents within 45 days of discovery, with CRA notice above 1,000 affected residents and no private right of action under the statute.

Retention and disposalRed

No general statutory retention-limitation or disposal-duty regime exists under Ohio law outside sector-specific overlays.

Category narrative 77 words

Ohio imposes no general accountability, DPIA, DPO, ROPA, or joint-controller regime. The one operative Ohio-specific instrument is the Data Protection Act's voluntary cybersecurity safe harbor, which incentivizes (but does not mandate) alignment with recognized frameworks (NIST CSF, NIST SP 800-53/-53A/-171, HIPAA Security Rule, GLBA Title V, FISMA, PCI-DSS) in exchange for an affirmative tort defense. Breach notification is separately and mandatorily governed by ORC §1349.19 (and related §§1347.12, 1349.191-.192). No general retention/disposal mandate exists outside sectoral overlays.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (12)
  1. Confirmed IAPP — The Ohio Data Protection Act explicitly does not set minimum data-security standards or impose liability on businesses that fail to maintain a conforming cybersecurity program; compliance is voluntary and incentive-based rather than a mandatory accountability duty. observed
  2. Confirmed IAPP — To qualify for the Ohio Data Protection Act's affirmative-defense safe harbor, a covered entity must create, maintain, and comply with a written cybersecurity program that reasonably conforms to one of several named frameworks, including the NIST Cybersecurity Framework and NIST SP 800-53/800-53A/800-171. observed
  3. Confirmed IAPP — Recognized cybersecurity frameworks that qualify an entity for the Ohio Data Protection Act's safe harbor also include the HIPAA Security Rule, GLBA Title V, FISMA, and the PCI Data Security Standard. observed
  4. Confirmed DataGuidance (OneTrust) — Ohio's data-breach notification statute addresses notification obligations only and does not establish comprehensive consumer privacy rights such as access, deletion, or opt-out. observed
  5. Probable NBC4 / WCMH — Central Ohio Primary Care Physicians disclosed on 2026-10-15 a cyberattack discovered 2026-08-25 that exposed personal information (names, addresses, SSNs, financial data, limited health data) of approximately 1.4 million patients and employees; notices are being mailed to affected individuals under ORC 1349.19. observed
  6. High Commoner Law — Ohio Security Breach Notification Act (ORC 1349.19) — Requires notification of affected consumers within 45 days of discovering a breach involving personal or sensitive information, with credit-bureau notification required if more than 1,000 Ohio residents are affected observed
  7. Uncertain Jones Day via Legal500 — Under Ohio Rev. Code Ch. 1354 (Ohio Data Protection Act), a covered entity qualifies for an affirmative-defense safe harbor against Ohio tort claims alleging failure to implement reasonable security controls only if it creates, maintains and reasonably conforms its cybersecurity program to an industry-recognized framework; the amended version of this law took effect Nov. 2 (year of amendment not confirmed this cycle). observed
  8. Probable recordinglaw.com — Ohio Rev. Code 1349.19 — Requires notification to affected Ohio residents 'in the most expedient time possible' and no later than 45 days after discovery of a breach causing a material risk of identity theft or fraud; notification to consumer-reporting agencies required if more than 1,000 residents are affected. Financial institutions subject to GLBA are exempt. observed
  9. Confirmed recordinglaw.com — Ohio businesses holding computerized personal information — A breach of the security of the system in the most expedient time possible but not later than 45 days following discovery, subject to law-enforcement delay (R.C. 1349.19(B)(2)) observed
  10. Confirmed Ohio House of Representatives — Ohio Data Protection Act covered entities — Written cybersecurity program reasonably conforming to an industry-recognised framework, scaled per R.C. 1354.02(C), as a voluntary affirmative defense carrying no private right of action (R.C. 1354.04) observed
  11. Probable recordinglaw.com — Ohio Rev. Code Chapter 1354 gives covered entities with a conforming written cybersecurity program an affirmative defense to tort claims for breach, on a voluntary basis. observed
  12. Probable recordinglaw.com — Ohio Rev. Code 1349.19 requires notification of a data breach to affected Ohio residents within 45 days of discovery, with CRA notice above 1,000 affected residents and no private right of action under the statute. observed

#

This is a confirmed structural absence consistent with the US sectoral model; no transfer-mechanism infrastructure exists to evaluate at the Ohio level.

Traffic-light rationale — RedThis is a confirmed structural absence consistent with the US sectoral model; no transfer-mechanism infrastructure exists to evaluate at the Ohio level.

Sub-modules (6)

Transfer mechanismsRed

No Ohio or applicable federal general-purpose cross-border transfer mechanism (adequacy/SCC/BCR/derogation) exists for commercial personal data.

Adequacy receivedRed

No adequacy decisions are received by Ohio/the US at the state level; this concept does not apply outside omnibus regimes.

Adequacy grantedRed

Ohio does not grant adequacy decisions; this concept is not applicable to a US sub-national jurisdiction lacking an omnibus statute.

SCCs and BCRsRed

No Ohio-specific SCC or BCR framework exists.

Transfer impact assessmentRed

No TIA requirement exists under Ohio law.

Data localisationRed

No general data-localisation mandate applies to commercial personal data in Ohio.

Claims (1):

  • US-OH cross-border transfer regime — No Ohio-specific cross-border transfer mechanism or data-localisation mandate identified
Category narrative 41 words

Neither Ohio nor US federal sectoral law maintains a GDPR-style cross-border transfer regime. There are no Ohio-specific adequacy determinations (received or granted), no SCC/BCR analogue, no transfer-impact-assessment requirement, and no data-localisation mandate applicable to general commercial data at the state level.

Sources and claims (1)
  1. Assessed RecordingLaw — US-OH cross-border transfer regime — No Ohio-specific cross-border transfer mechanism or data-localisation mandate identified observed

#

Financial and insurance sector overlays are well-evidenced and binding; other sectors (telecoms, employment, credit-scoring, education) show no Ohio-specific instrument and are carried as gaps.

Primary frameworkGLBA Title V (financial) + Ohio Insurance Data Security Standards Act + HIPAA (health, federal)
Traffic-light rationale — AmberFinancial and insurance sector overlays are well-evidenced and binding; other sectors (telecoms, employment, credit-scoring, education) show no Ohio-specific instrument and are carried as gaps.

Sub-modules (7)

Financial sector overlayGreen

GLBA Title V imposes an affirmative and continuing obligation on financial institutions to protect the security and confidentiality of customers' nonpublic personal information, enforced by the FTC (for entities not otherwise regulated) and other federal/state financial regulators.

Claims (2):

  • Under GLBA Title V, each financial institution has an affirmative and continuing obligation to respect the privacy of its customers and protect the security and confidentiality of nonpublic personal information.
  • The FTC has enforcement jurisdiction over the GLBA Privacy Rule for financial institutions and other persons not regulated by other federal or state agencies, and state insurance authorities are responsible for issuing regulations and enforcing GLBA with respect to insurance providers.

Health sector overlayAmber

HIPAA's Security Rule is named as one of the qualifying frameworks under the Ohio Data Protection Act's safe harbor, indicating HIPAA operates as the substantive health-data protection regime in Ohio rather than any state-specific health-privacy statute.

Claims (1):

  • The HIPAA Security Rule is listed among the industry-recognized cybersecurity frameworks a covered entity may adopt to qualify for the Ohio Data Protection Act's litigation safe harbor.

Telecoms and eprivacyRed

No Ohio-specific ePrivacy/telecoms-privacy analogue (e.g., cookie-consent statute) was identified.

Employment dataRed

No Ohio-specific employment-data privacy statute was identified.

Credit and scoringAmber

Credit-related data handling in Ohio is governed by the federal Fair Credit Reporting Act rather than an Ohio-specific credit-scoring privacy statute; this module entry is carried at lower confidence pending direct primary-source verification.

educationRed

No Ohio-specific student-data privacy statute distinct from federal FERPA was identified in this run.

insuranceGreen

Ohio enacted an Insurance Data Security Standards statute establishing cybersecurity requirements for licensed insurance entities operating in the state.

Claims (2):

  • Ohio's Governor signed an insurance data-security standards bill establishing cybersecurity obligations for insurance entities licensed in the state.
  • Ohio political subdivisions — A cybersecurity program under R.C. 9.64, with compliance expected by county/city governments from Jan. 1, 2026 and other entities incl. school districts from July 1, 2026
Category narrative 82 words

In the absence of an Ohio omnibus statute, sectoral federal overlays do the substantive work: GLBA Title V governs financial-institution nonpublic personal information (enforced by the FTC, federal banking regulators, and state insurance authorities), Ohio has separately enacted an Insurance Data Security Standards statute aligning with the NAIC Insurance Data Security Model Law, and HIPAA governs health information as one of the named safe-harbor frameworks under the Ohio Data Protection Act. No Ohio-specific telecoms/ePrivacy, employment-data, credit-scoring, or education-sector privacy statute was identified.

Sources and claims (5)
  1. Confirmed IAPP — Under GLBA Title V, each financial institution has an affirmative and continuing obligation to respect the privacy of its customers and protect the security and confidentiality of nonpublic personal information. observed
  2. Confirmed Federal Trade Commission — The FTC has enforcement jurisdiction over the GLBA Privacy Rule for financial institutions and other persons not regulated by other federal or state agencies, and state insurance authorities are responsible for issuing regulations and enforcing GLBA with respect to insurance providers. observed
  3. Confirmed IAPP — The HIPAA Security Rule is listed among the industry-recognized cybersecurity frameworks a covered entity may adopt to qualify for the Ohio Data Protection Act's litigation safe harbor. observed
  4. Probable DataGuidance (OneTrust) — Ohio's Governor signed an insurance data-security standards bill establishing cybersecurity obligations for insurance entities licensed in the state. observed
  5. Probable https://www.dinsmore.com/publications/ohio-law-imposes-new-cybersecurity-requirements-for-local-government/ — Ohio political subdivisions — A cybersecurity program under R.C. 9.64, with compliance expected by county/city governments from Jan. 1, 2026 and other entities incl. school districts from July 1, 2026

#

Confirmed absence of Ohio-specific adtech/commercial-privacy statutes; only the reactive federal baseline applies.

Primary frameworkFTC Act Section 5 (federal baseline only)
Supervisory authorityFederal Trade Commission
Traffic-light rationale — RedConfirmed absence of Ohio-specific adtech/commercial-privacy statutes; only the reactive federal baseline applies.

Sub-modules (6)

Cookies and trackersRed

No Ohio cookie/tracker consent statute exists.

Dark patternsRed

Dark-pattern prohibitions exist in a subset of other US comprehensive state privacy laws but Ohio, lacking such a law, has no equivalent prohibition.

Claims (1):

  • A subset of enacted US state comprehensive privacy laws prohibit consent obtained through manipulative or deceptive dark patterns; Ohio, having no comprehensive privacy law, has no equivalent statutory prohibition.

Opt out signalsRed

No Ohio requirement to honor universal opt-out signals (e.g., Global Privacy Control) exists.

Clean rooms and dcrRed

No Ohio clean-room/data-collaboration-room regulation exists.

Cross context advertisingRed

No Ohio 'sale'/'share' cross-context-advertising framework analogous to CPRA exists.

Direct marketingRed

No Ohio-specific direct-marketing consent/suppression statute beyond general federal telemarketing/CAN-SPAM frameworks was identified in this run.

Category narrative 50 words

Ohio has no cookie/tracker consent statute, dark-pattern prohibition, opt-out-signal mandate, clean-room regulation, cross-context-advertising 'sale/share' framework, or direct-marketing consent regime comparable to those found in the 19 US states with comprehensive privacy laws. Commercial adtech practices in Ohio are governed only by the general federal FTC Act Section 5 deception/unfairness standard.

Sources and claims (1)
  1. Probable IAPP — A subset of enacted US state comprehensive privacy laws prohibit consent obtained through manipulative or deceptive dark patterns; Ohio, having no comprehensive privacy law, has no equivalent statutory prohibition. observed

#

Confirmed absence of Ohio biometric/algorithmic-governance statutes relative to the small set of US states that have legislated in this space.

Traffic-light rationale — RedConfirmed absence of Ohio biometric/algorithmic-governance statutes relative to the small set of US states that have legislated in this space.

Sub-modules (6)

Profiling restrictionsRed

No Ohio statute restricts automated profiling.

Automated decision making transparencyRed

No Ohio ADM transparency or explanation-right statute exists.

Claims (1):

  • Ohio House Bill 828 — House Bill 828 would enact ORC 4113.90 to regulate the use of automated employment decision tools; as of its last tracked action (2026-05-13) it remains referred to committee with no floor action.

AI risk assessmentsRed

No Ohio AI-specific risk-assessment statute was identified in this run.

Biometric regimeRed

Ohio has not enacted a biometric-information-privacy statute; only Illinois (BIPA), Washington, and Texas have state biometric-specific privacy legislation among US states.

Claims (1):

  • Among US states, only Illinois, Washington and Texas have passed biometric-specific privacy legislation; Ohio has not enacted a comparable biometric-information-privacy statute.

Genetic dataRed

No Ohio-specific genetic-data privacy statute was identified.

State surveillance carveoutsRed

No Ohio-specific codified state-surveillance carve-out distinct from general federal national-security exemptions was identified.

Category narrative 48 words

Ohio has no state-specific biometric-privacy statute; among US states, only Illinois, Washington and Texas have enacted biometric-specific privacy legislation, and Ohio is not among them. Correspondingly, Ohio has no profiling restriction, ADM transparency/explanation right, AI-specific risk-assessment mandate, genetic-data statute, or codified state-surveillance carve-out distinct from general federal frameworks.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (2)
  1. Confirmed IAPP — Among US states, only Illinois, Washington and Texas have passed biometric-specific privacy legislation; Ohio has not enacted a comparable biometric-information-privacy statute. observed
  2. Probable AI Law Tracker — Ohio House Bill 828 — House Bill 828 would enact ORC 4113.90 to regulate the use of automated employment decision tools; as of its last tracked action (2026-05-13) it remains referred to committee with no floor action. observed

#

A federal sectoral floor (COPPA) exists and state AGs assist in its enforcement, but no Ohio-specific instrument supplements it, and several sub-modules are wholly unaddressed at the state level.

Primary frameworkCOPPA (federal)
Traffic-light rationale — AmberA federal sectoral floor (COPPA) exists and state AGs assist in its enforcement, but no Ohio-specific instrument supplements it, and several sub-modules are wholly unaddressed at the state level.

Sub-modules (5)

Age verificationRed

No Ohio-specific age-verification statute for data processing was identified.

Claims (1):

  • Ohio Social Media Parental Notification Act (R.C. 1349.09) — Parental consent for minors under 16 to use social media, reported effective 2026-06-18, following 2024 judicial injunction against earlier version

Minor profiling bansRed

No Ohio-specific statutory ban on profiling minors was identified.

Education settingsRed

No Ohio-specific education-settings data-privacy statute beyond federal FERPA was identified in this run.

Dependent adultsRed

No Ohio-specific dependent-adult (elderly/incapacitated) data-protection statute was identified.

Category narrative 39 words

Ohio relies on the federal Children's Online Privacy Protection Act (COPPA), enforced with attorney-general involvement, as its operative children's-data framework; no Ohio-specific age-verification, parental-consent, minor-profiling-ban, or education-settings privacy statute was identified. No Ohio-specific dependent-adult data-protection statute was identified either.

Sources and claims (3)
  1. Probable NAAG — State attorneys general, including through coordinated NAAG efforts, participate in enforcing federal children's-privacy legislation such as COPPA alongside the FTC, in the absence of an Ohio-specific children's-data statute. observed
  2. Uncertain Wikimedia Foundation — Ohio Social Media Parental Notification Act (R.C. 1349.09) — Parental consent for minors under 16 to use social media, reported effective 2026-06-18, following 2024 judicial injunction against earlier version observed
  3. Probable davispolk.com — FTC COPPA Rule, 16 C.F.R. Part 312 — The FTC's amended COPPA Rule, fully effective April 22, 2026, requires separate verifiable parental consent before disclosing a child's personal information to third parties for targeted advertising, broadens 'personal information' to include biometric identifiers, and imposes new data-retention limits; this federal rule is the operative standard for Ohio-reaching child-directed services. observed

#

Real AG enforcement capacity exists and is active nationally (state AGs coordinate on breach enforcement), but Ohio-specific penalty schedules, recent enforcement actions, and private-right-of-action status could not be confirmed to Confirmed-level certainty from available sources in this run.

Primary frameworkOhio consumer-protection/AG enforcement authority + FTC Act Section 5
Supervisory authorityOhio Attorney General
Traffic-light rationale — AmberReal AG enforcement capacity exists and is active nationally (state AGs coordinate on breach enforcement), but Ohio-specific penalty schedules, recent enforcement actions, and private-right-of-action status could not be confirmed to Confirmed-level certainty from available sources in this run.

Sub-modules (6)

Regulator powers and penaltiesAmber

Following a successful breach-law enforcement action, state attorneys general may pursue injunctions and civil penalties as set out under state consumer-protection laws; the specific Ohio penalty schedule was not independently confirmed via a primary Ohio Revised Code citation in this run.

Claims (5):

  • Following a successful enforcement action for violation of state data-breach laws, attorneys general may pursue remedies including injunctions requiring companies to update systems/governance and civil penalties as provided under state consumer-protection statutes.
  • Ohio Attorney General — Under Ohio Rev. Code 1349.191, the Attorney General may investigate violations of the breach-notification statute, with escalating civil penalties of up to $10,000 per day for intentional or reckless non-compliance; there is no private right of action under the statute itself.
  • Ohio Rev. Code 1349.19 penalty structure — For intentional or reckless noncompliance with the breach-notification duty, the Ohio Attorney General may obtain graduated civil penalties of up to $1,000/day for the first 60 days, up to $5,000/day from day 60-90, and up to $10,000/day thereafter; there is no private right of action under this statute.
  • Ohio Rev. Code 1349.19 — Escalating daily penalties up to $10,000 per day for noncompliance with breach-notification obligations; enforcement via Ohio Attorney General, no private right of action
  • Ohio Attorney General — Civil action for an alleged failure to comply with the breach-notification statute under R.C. 1349.191 and 1349.192

Enforcement activity indexAmber

National enforcement activity has intensified, led by Texas and California, with multistate AG coordination on breach matters; no Ohio-specific enforcement action in the last 12 months was located in this run.

Claims (1):

  • US state privacy-enforcement activity increased in the most recent tracked period, led by Texas and California, alongside coordinated multistate attorney-general breach enforcement; no Ohio-specific major action was identified as part of this trend.

Regulator funding and capacityRed

No specific Ohio Attorney General privacy-unit funding/headcount data was located in this run.

Collective redress and class actionsAmber

No Ohio-specific collective-redress mechanism dedicated to privacy claims was confirmed; general Ohio class-action procedure (Ohio Civ. R. 23) may apply to breach-related tort claims but was not independently verified in this run.

Private right of actionAmber

Some, but not all, US state breach-notification statutes allow a private right of action; whether Ohio's statute does so was not conclusively confirmed via primary source in this run and should be treated as Uncertain pending direct Ohio Revised Code review.

Claims (3):

  • A minority of US state data-breach-notification statutes allow a private right of action for noncompliance, while the majority rely exclusively on attorney-general enforcement; Ohio's specific position on this point was not independently confirmed in this run.
  • Ohio data-privacy enforcement regime — Ohio has no private right of action for data-privacy violations; enforcement runs solely through Attorney General action under existing consumer-protection statutes
  • Ohio Data Protection Act — Private right of action, including a class action, for failure to meet or qualify for its affirmative-defense safe harbor (R.C. 1354.04)

Recent developments 180dRed

No new Ohio comprehensive privacy legislation, enacted amendment, or adequacy-relevant development was identified within the last 180 days; the most recent substantive Ohio-specific development remains the 2021 introduction and subsequent hold of the Ohio Personal Privacy Act (HB 376), which has not been reintroduced or advanced to enactment as of this run.

Claims (2):

  • Ohio's comprehensive privacy bill (Ohio Personal Privacy Act, HB 376) remains on hold following its 2021 introduction, with no confirmed reintroduction or enactment identified as of this run.
  • Ohio House Bill 801 — Would bar Ohio state government entities from collecting, recording, or sharing personal/identifying information with out-of-state entities except where required or permitted by law
Category narrative 95 words

Enforcement in Ohio is carried out principally by the Ohio Attorney General under general consumer-protection authority and by the FTC under Section 5, rather than under a dedicated privacy-enforcement statute with codified maximum penalties. Ohio's breach-notification statute is enforced by the Attorney General; the Ohio Data Protection Act creates no independent enforcement mechanism at all (it is a voluntary safe harbor). No comprehensive collective-redress/class-action mechanism or general private right of action for privacy violations was confirmed for Ohio in this run; this should be treated as an open verification item rather than a settled negative.

Periodic update · new data 2026-10-25

Ohio's breach-notification enforcement authority rests with the Ohio Attorney General, who under Ohio Revised Code 1349.191 may investigate violations of the breach-notification statute and pursue escalating civil penalties of up to ten thousand dollars per day for intentional or reckless non-compliance; the statute itself does not create a private right of action. No Ohio Attorney General enforcement action specific to the Central Ohio Primary Care Physicians breach has been located. Private redress activity has nonetheless begun: Edelson Lechtzin LLP announced on 16 October 2026 that it is investigating data-privacy claims on behalf of patients and employees affected by the COPC breach, which discovered on 25 August 2026 and disclosed on 15 October 2026 affected approximately 1.4 million individuals.

Outlook

Whether the Ohio Attorney General opens a formal investigation under its ORC 1349.191 authority, and whether Edelson Lechtzin's announced investigation proceeds to filed litigation, are the two developments most likely to define the enforcement and redress picture for the COPC matter going forward.

1 earlier distinct update
Periodic update · new data 2026-10-18

Ohio's breach-notification enforcement authority rests with the Ohio Attorney General, who under Ohio Revised Code 1349.191 may investigate violations of the breach-notification statute and pursue escalating civil penalties of up to ten thousand dollars per day for intentional or reckless non-compliance; the statute itself does not create a private right of action. No Ohio Attorney General enforcement action specific to the Central Ohio Primary Care Physicians breach has been located as of this cycle. Private redress activity has nonetheless begun: Edelson Lechtzin LLP announced on 16 October 2026 that it is investigating data-privacy claims on behalf of patients and employees affected by the COPC breach, which discovered on 25 August 2026 and disclosed on 15 October 2026 affected approximately 1.4 million individuals.

Outlook

Whether the Ohio Attorney General opens a formal investigation under its ORC 1349.191 authority, and whether Edelson Lechtzin's announced investigation proceeds to filed litigation, are the two developments most likely to define the enforcement and redress picture for the COPC matter going forward.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (11)
  1. Probable NAAG — Following a successful enforcement action for violation of state data-breach laws, attorneys general may pursue remedies including injunctions requiring companies to update systems/governance and civil penalties as provided under state consumer-protection statutes. observed
  2. Probable IAPP — US state privacy-enforcement activity increased in the most recent tracked period, led by Texas and California, alongside coordinated multistate attorney-general breach enforcement; no Ohio-specific major action was identified as part of this trend. observed
  3. Uncertain NAAG — A minority of US state data-breach-notification statutes allow a private right of action for noncompliance, while the majority rely exclusively on attorney-general enforcement; Ohio's specific position on this point was not independently confirmed in this run. observed
  4. Probable IAPP — Ohio's comprehensive privacy bill (Ohio Personal Privacy Act, HB 376) remains on hold following its 2021 introduction, with no confirmed reintroduction or enactment identified as of this run. observed
  5. High Ohio House of Representatives — Ohio House Bill 801 — Would bar Ohio state government entities from collecting, recording, or sharing personal/identifying information with out-of-state entities except where required or permitted by law observed
  6. High PrivacyOn — Ohio data-privacy enforcement regime — Ohio has no private right of action for data-privacy violations; enforcement runs solely through Attorney General action under existing consumer-protection statutes observed
  7. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/ohio-data-privacy-laws/data-breach-notification/ — Ohio Attorney General — Under Ohio Rev. Code 1349.191, the Attorney General may investigate violations of the breach-notification statute, with escalating civil penalties of up to $10,000 per day for intentional or reckless non-compliance; there is no private right of action under the statute itself.
  8. Probable openagreements.org — Ohio Rev. Code 1349.19 penalty structure — For intentional or reckless noncompliance with the breach-notification duty, the Ohio Attorney General may obtain graduated civil penalties of up to $1,000/day for the first 60 days, up to $5,000/day from day 60-90, and up to $10,000/day thereafter; there is no private right of action under this statute. observed
  9. Probable CyberRiskPolicy.com — Ohio Rev. Code 1349.19 — Escalating daily penalties up to $10,000 per day for noncompliance with breach-notification obligations; enforcement via Ohio Attorney General, no private right of action observed
  10. Confirmed recordinglaw.com — Ohio Attorney General — Civil action for an alleged failure to comply with the breach-notification statute under R.C. 1349.191 and 1349.192 observed
  11. Probable Ohio House of Representatives — Ohio Data Protection Act — Private right of action, including a class action, for failure to meet or qualify for its affirmative-defense safe harbor (R.C. 1354.04) observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 49 claim(s) (49 category placement(s)), 34 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: nothing tested (no claim on this page was eligible for an automated test). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (38 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsaccess right
Art. 14Data Subject Rightsaccess right
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrectification and erasure
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy received
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacytransfer mechanisms
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressregulator powers and penalties
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 81Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redresscollective redress and class actions
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties