Ohio Data Privacy Laws: Safe Harbor & Consumer Rights (2026)

Ohio has no comprehensive consumer data privacy law, leaving residents without the broad access, deletion, and opt-out rights available in more than 20 other states. The Ohio Data Protection Act (ORC Chapter 1354) is a voluntary cybersecurity safe harbor for businesses. The breach notification law (ORC 1349.19) requires notice within 45 days.

Ohio takes a patchwork approach to data privacy. Rather than enacting a single comprehensive consumer privacy statute, the state relies on a combination of targeted laws: a first-in-the-nation voluntary cybersecurity safe harbor, a data breach notification requirement, government data practices rules, insurance data security standards, and consumer protection enforcement through the Ohio Consumer Sales Practices Act.

This approach places Ohio behind the growing majority of states. As of May 2026, more than 20 states have enacted comprehensive consumer privacy laws granting residents rights to access, correct, delete, and opt out of the sale of their personal data. Ohio residents have no generally applicable version of those rights against private businesses under state law. The one exception is sector-specific and narrow, and it is covered below: ORC Chapter 3904 gives access, correction, and deletion rights against life, health, and disability insurers.

What Ohio does have is substantial. The 2018 Data Protection Act remains unique nationwide, and the state's enforcement agencies have secured meaningful data-breach settlements on behalf of residents. Understanding what the law covers, and where it does not reach, is essential for both businesses operating in Ohio and residents trying to protect their information.

This guide covers every major Ohio statute affecting data privacy, what protections currently exist, how enforcement works, what federal law adds, and where pending legislation stands as of May 2026.

Ohio Data Protection Act: A Voluntary Safe Harbor, Not Consumer Rights (ORC Chapter 1354)

The Ohio Data Protection Act, enacted through Senate Bill 220 and signed on August 3, 2018, is frequently mischaracterized as an Ohio privacy law. It is not a consumer-rights statute. It does not give Ohio residents the right to access, correct, or delete their data. It does not restrict what data businesses can collect.

The law creates a legal benefit for businesses. A covered entity that creates, maintains, and complies with a qualifying written cybersecurity program earns an affirmative defense against tort lawsuits alleging that the failure to implement reasonable information security controls resulted in a data breach. The law took effect on November 2, 2018, and was the first of its kind in the United States.

What the Safe Harbor Covers

Under ORC 1354.02, the affirmative defense is available against causes of action sounding in tort that are brought under Ohio law and allege that inadequate cybersecurity caused a data breach. The scope of that defense tracks the scope of the program the business actually built. Under ORC 1354.02(D)(1), a business whose written program covers personal information only has a defense limited to claims that its inadequate controls caused a data breach concerning personal information. Only a business whose program covers both personal information and restricted information, the option in ORC 1354.02(A)(2), gets the wider defense in ORC 1354.02(D)(2) that also reaches a breach concerning restricted information.

The safe harbor is a defense raised in court, not an immunity. A business that suffers a breach cannot simply invoke it to avoid all consequences. It must demonstrate compliance with the statutory requirements. The defense does not block regulatory enforcement actions, breach notification obligations, or claims arising under other statutes.

What a Qualifying Cybersecurity Program Requires

To qualify for the safe harbor, a covered entity must maintain a written cybersecurity program with administrative, technical, and physical safeguards. ORC 1354.02(A) offers two options: a program that covers personal information only, or a program that covers both personal information and restricted information. That choice determines how far the affirmative defense reaches. Either way, the program must be designed to accomplish three objectives. First, protect the security and confidentiality of the information the program covers. Second, protect against anticipated threats or hazards to the security or integrity of that information. Third, protect against unauthorized access and acquisition that is likely to result in a material risk of identity theft or other fraud.

The program must be scaled appropriately. Relevant factors include the size and complexity of the covered entity, the nature and scope of its activities, the sensitivity of the information protected, the cost and availability of security tools, and available resources.

Recognized Cybersecurity Frameworks

ORC 1354.03 lists specific frameworks a business may rely on to qualify for the safe harbor.

NIST Cybersecurity Framework. The National Institute of Standards and Technology Framework for Improving Critical Infrastructure Cybersecurity.

NIST SP 800-171. The NIST Special Publication covering protection of controlled unclassified information in nonfederal systems.

NIST SP 800-53 / 800-53A. The NIST Special Publications covering security and privacy controls for federal information systems and their assessment.

FedRAMP. The Federal Risk and Authorization Management Program Security Assessment Framework.

CIS Controls. The Center for Internet Security Critical Security Controls for Effective Cyber Defense.

ISO/IEC 27000. The international Information Security Management Systems standards family.

Industry-regulated entities may also use their sector-specific frameworks. HIPAA and HITECH-covered entities can rely on compliance with those rules. GLBA-regulated financial institutions can rely on Title V compliance. Federal agencies and contractors subject to FISMA qualify through that compliance. PCI DSS-compliant entities must also conform to at least one other listed framework.

The Reasonable Conformance Standard

Under ORC 1354.03, the statute requires reasonable conformance, not perfect compliance. When a listed framework such as the NIST CSF, FedRAMP, CIS Controls, or ISO/IEC 27000 is revised, a covered entity has one year from the revision's publication date to conform to the updated version. For the industry-regulated frameworks (HIPAA, HITECH, GLBA, FISMA), the one-year clock instead runs from the effective date of the amended framework.

Why This Matters for Consumers

Consumers benefit indirectly from the Data Protection Act. Businesses have a financial incentive to invest in cybersecurity because strong programs reduce tort exposure. But the law creates no direct consumer rights. The Data Protection Act itself gives Ohio residents no right to request access to data held by a participating business, no right to deletion, and no right to opt out of data sales. Any such right has to come from somewhere else, such as ORC Chapter 3904 in the insurance context or federal law.

Ohio Data Breach Notification Law (ORC 1349.19)

Ohio's data breach notification law, ORC 1349.19, establishes mandatory notification obligations for businesses and individuals that experience a security breach affecting Ohio residents. The law was originally enacted in 2005 and has been updated since.

Definition of Personal Information

The statute defines personal information as an individual's name combined with any one or more of the following data elements when not encrypted, redacted, or otherwise rendered unreadable or unusable:

• Social Security number
• Driver's license number or state identification card number
• Account number, credit card number, or debit card number combined with any required security code, access code, or password

The encryption safe harbor is significant. If compromised data was encrypted or rendered unreadable at the time of the breach, notification is not required.

Definition of a Breach

A breach of the security of the system means unauthorized access to and acquisition of computerized data that compromises the security or confidentiality of personal information owned or licensed by a person and that causes, reasonably is believed to have caused, or reasonably is believed will cause a material risk of identity theft or other fraud to the person or property of an Ohio resident.

Both access and acquisition must occur. Unauthorized system access alone, without evidence that data was actually acquired, does not trigger notification obligations.

45-Day Notification Timeline

Entities must notify affected Ohio residents in the most expedient time possible, but no later than 45 days after discovering the breach. The notification window permits time to determine the scope of the breach, identify affected residents, and restore reasonable system integrity.

Law enforcement agencies may request a delay if notification would impede a criminal investigation. Once law enforcement determines disclosure will no longer compromise the investigation, the 45-day window resumes.

Methods of Notification

The law permits written notice by letter, telephonic notice by phone call, or electronic notice when the entity's primary communication method with the individual is electronic. Substitute notice is available when direct notification costs exceed $250,000, the affected class exceeds 500,000 residents, or the entity lacks sufficient contact information. Substitute notice requires a combination of email notification, conspicuous website posting, and notification to major statewide media.

Small business substitute notice is available when the entity has 10 or fewer employees and notification costs exceed $10,000. This permits a combination of paid local newspaper notification, website posting, and local media notification.

Large Breach Reporting

When a breach affects more than 1,000 Ohio residents in a single occurrence, the entity must also notify all nationwide consumer reporting agencies without unreasonable delay. That notice must include the timing, distribution, and content of the disclosure sent to affected residents.

Penalties and Enforcement

The Ohio Attorney General has investigative authority under ORC 1349.191 and may bring a civil enforcement action under ORC 1349.192. Civil penalties are graduated based on the duration of noncompliance: up to $1,000 per day for the first 60 days, up to $5,000 per day from 60 to 90 days, and up to $10,000 per day after 90 days of intentional or reckless noncompliance. These penalties require a court action brought by the Attorney General.

Exemptions

Financial institutions subject to federal data breach notification requirements and regulatory examination are exempt from ORC 1349.19 (their breach notification obligations fall under the Gramm-Leach-Bliley Act and federal banking regulations). A second, separate exemption under ORC 1349.19(F)(2) removes HIPAA-covered entities entirely: any person or entity that qualifies as a covered entity under 45 C.F.R. 160.103, including hospitals, health insurers, and other healthcare providers, is not subject to this section's notification requirement at all, because they already answer to the HIPAA Breach Notification Rule. Entities with preexisting contractual notification provisions consistent with the statute may rely on those arrangements.

State Agency Data Breach Notification (ORC 1347.12)

ORC 1347.12 imposes separate and parallel breach notification obligations on Ohio state agencies and political subdivisions. These government entities must disclose any breach to affected Ohio residents when the breach causes or is reasonably believed to cause a material risk of identity theft or other fraud.

When a government agency stores data on behalf of another agency, it must notify the data-owning agency expeditiously so that agency can fulfill its own notification obligations.

The civil penalty structure for government agency noncompliance mirrors the private sector structure under ORC 1349.192: courts may impose up to $1,000 per day for the first 60 days, up to $5,000 per day from day 61 to day 90, and up to $10,000 per day after day 90, for each day of intentional or reckless noncompliance.

Government Data Practices (ORC Chapter 1347)

ORC Chapter 1347 governs how Ohio state agencies collect, maintain, use, and disclose personal information in their systems. This statute predates modern data privacy frameworks and focuses on government accountability.

Individual Rights Against State Agencies

ORC Chapter 1347 gives Ohio residents specific rights regarding personal information held by state agencies. These rights do not extend to private businesses.

Right to know. Any person may request that a state or local agency confirm whether it maintains personal information about that person in its systems.

Right to inspect. The person, their legal guardian, or an authorized attorney may inspect all personal information the agency holds about the individual.

Right to correct. If personal information is inaccurate, the individual may request correction.

Right to challenge. If the agency refuses to correct the information, the individual may submit a statement of disagreement that becomes part of the record.

Confidential Personal Information Rules

Under ORC 1347.15, each state agency must adopt administrative rules under Chapter 119 regulating access to confidential personal information. These rules must cover both electronic and paper records. Agencies must maintain access logs and establish internal procedures preventing unauthorized disclosure.

Ohio Consumer Sales Practices Act: Primary Privacy Enforcement Tool (ORC Chapter 1345)

Without a comprehensive privacy statute, the Ohio Consumer Sales Practices Act (CSPA) is the primary mechanism through which the Ohio Attorney General pursues privacy violations involving consumer transactions.

The CSPA prohibits unfair or deceptive acts or practices in connection with consumer transactions. Companies that promise specific data security protections but fail to deliver can face CSPA enforcement actions for deceptive practices. Businesses that fail to adequately disclose data collection practices may engage in unfair conduct.

Marriott Settlement (October 2024)

In October 2024, the Ohio Attorney General filed suit in Franklin County Common Pleas Court alleging that Starwood and Marriott International violated the CSPA by misrepresenting their cybersecurity practices, which allowed a massive data breach affecting millions of consumers. The parties submitted a consent judgment approved and entered on October 11, 2024. Marriott agreed to strengthen its data-security practices, provide certain consumer protections, and pay $52 million to 49 participating states, with more than $1.5 million going to Ohio.

CSPA Penalty Structure

Courts may impose civil penalties of up to $25,000 per CSPA violation, but only where the violation involved a practice already declared unfair, deceptive, or unconscionable by an Attorney General rule, or by a prior Ohio court decision made public, before the conduct at issue occurred. For a first-instance violation not previously declared unlawful, the Attorney General's civil remedies are limited to declaratory judgment, injunctive relief, and restitution, and the $25,000 penalty does not apply. Violations of court orders (temporary restraining orders, preliminary injunctions, or permanent injunctions) can result in penalties of $5,000 per day regardless of prior declaration. Seventy-five percent of civil penalties go to the state's Consumer Protection Enforcement Fund, with 25% to the county treasury where the action was brought.

Consumers who suffer harm from CSPA violations may bring private lawsuits. The enhanced remedy carries the same precondition: treble damages (three times actual economic damages) or $200, whichever is greater, is available only for a practice already declared unlawful by rule or a prior public court decision. Otherwise, a consumer's recovery is limited to rescission of the transaction or actual economic damages, plus noneconomic damages up to $5,000.

Ohio Department of Commerce: Bayview Settlement (January 2025)

The Ohio Department of Commerce, through its Division of Financial Institutions, joined a $20 million multistate enforcement action against Bayview Asset Management LLC and three affiliates (Lakeview Loan Servicing, Community Loan Servicing, and Pingora Holdings) announced January 8, 2025.

State financial regulators in California, Maryland, North Carolina, and Washington State led the coalition of 52 state financial regulatory agencies. Investigators found that Bayview Companies' cybersecurity practices did not meet federal or state requirements, and the companies delayed examination compliance by failing to respond to state requests in a timely manner.

The breach affected approximately 5.8 million customers across the country, including 138,906 Ohio residents. This settlement represents the first collective multistate enforcement action by state financial regulators specifically targeting a mortgage company data breach.

In addition to the $20 million penalty, Bayview agreed to improve its cybersecurity programs, undergo independent assessments, and provide three years of additional reporting to participating states.

Insurance Data Security Act (ORC Chapter 3965)

Ohio enacted the Insurance Data Security Act through Senate Bill 273, effective March 20, 2019. This law, based on the NAIC Insurance Data Security Model Law, imposes specific cybersecurity requirements on insurance licensees operating in Ohio.

Program Requirements

Licensees must develop, implement, and maintain a comprehensive written information security program with administrative, technical, and physical safeguards protecting nonpublic information. The program must be based on a risk assessment that identifies foreseeable internal and external threats, assesses the likelihood and potential damage of those threats, evaluates existing safeguard sufficiency, and implements appropriate controls.

Breach Notification for Insurance Companies

Insurance licensees must notify the Ohio Superintendent of Insurance as promptly as possible, but no later than three business days after determining that a cybersecurity event has occurred, when either (1) Ohio is the licensee's state of domicile and the event has a reasonable likelihood of materially harming a consumer or a material part of the licensee's operations, or (2) the event involves the nonpublic information of 250 or more Ohio consumers and either a government body requires notice of the event or the event has a reasonable likelihood of materially harming an Ohio consumer or a material part of the licensee's operations.

HIPAA Compliance Equivalency

A licensee in compliance with HIPAA's privacy and security rules (45 C.F.R. Parts 160 and 164) is deemed to meet the requirements of ORC Chapter 3965, except for the notification provisions. HIPAA-compliant entities still must follow Ohio's insurance-specific breach notification rules.

Record Retention

Licensees must maintain all records, schedules, and data supporting their certificate of compliance for five years. Documentation of material improvement areas must be available for inspection by the Ohio Department of Insurance.

Insurance Information and Privacy Protection Act (ORC Chapter 3904)

Chapter 3965 above governs data SECURITY for insurance licensees. A separate, older chapter governs data PRIVACY, and it is the one place in Ohio law where a resident holds access, correction, and deletion rights against a private company: the Insurance Information and Privacy Protection Act, ORC Chapter 3904.

The chapter is deliberately narrow. Under ORC 3904.02, it binds insurance institutions, agents, and insurance support organizations that collect information about Ohio residents in connection with insurance transactions. ORC 3904.01 limits an insurance transaction to life, health, or disability insurance bought primarily for personal, family, or household needs. Auto, homeowners, and commercial lines fall outside it, and the access and correction sections do not apply to consumer reporting agencies.

Right of Access (ORC 3904.08)

After proper identification, an individual may submit a written request for recorded personal information about themselves that is reasonably described and reasonably locatable. Within thirty business days, ORC 3904.08 requires the company to inform the individual of the nature and substance of that information, permit the individual to obtain a copy, disclose the identity of persons to whom it disclosed the information in the previous two years, and provide a summary of the procedure for requesting a correction.

The company may charge a reasonable fee to cover copying costs. Medical record information may be routed either directly to the individual or to a medical professional the individual designates, at the company's election.

Right to Correct, Amend, or Delete (ORC 3904.09)

Within thirty business days of a written request, ORC 3904.09 requires the company either to correct, amend, or delete the disputed portion of the recorded personal information, or to notify the individual of its refusal, the reasons for it, and the individual's right to file a statement of disagreement.

If the company makes the change, it must pass the correction along to any person the individual designates who received the information in the previous two years and to insurance support organizations that received it. If the company refuses, the individual's concise written statement of disagreement is filed with the disputed information and must travel with it on any later disclosure.

Limits on Disclosure and Enforcement

ORC 3904.13 bars these companies from disclosing personal or privileged information collected in an insurance transaction except in the circumstances the statute lists, which include written authorization from the individual and disclosures reasonably necessary to perform an insurance function.

Enforcement runs through the Ohio Superintendent of Insurance rather than the Attorney General. Under ORC 3904.16, the superintendent issues a statement of charges and notice of hearing when there is reason to believe a company has violated the chapter, and an adversely affected person may intervene and be heard at that hearing.

Student Data Privacy (ORC 3319.321 and FERPA)

ORC 3319.321 governs the administrative use of public school records. Student records containing personally identifiable information, other than designated directory information, require written consent from a parent, guardian, or custodian before release. This aligns with and supplements federal Family Educational Rights and Privacy Act (FERPA) requirements.

Directory information may be released consistent with FERPA guidelines, but parents retain the right to opt out of directory information disclosure. When a residential parent presents a court order limiting a non-residential parent's access to student records, the record keeper must comply with those limitations.

Identity Theft and Fraud Protections

Identity Fraud Criminal Statute (ORC 2913.49)

ORC 2913.49 establishes identity fraud as a felony in Ohio. The severity of the offense depends on the financial harm caused.

General offense (division (I)(2)):

• Baseline offense: felony of the fifth degree
• $1,000 to $7,500 in losses: felony of the fourth degree
• $7,500 to $150,000 in losses: felony of the third degree
• $150,000 or more in losses: felony of the second degree

Protected-class offense (division (I)(3)) -- when the victim is an elderly person, disabled adult, active-duty service member, or spouse of an active-duty service member, penalties increase one degree at each tier:

• Baseline offense: felony of the fourth degree
• $1,000 to $7,500 in losses: felony of the third degree
• $7,500 to $150,000 in losses: felony of the second degree
• $150,000 or more in losses: felony of the first degree

When the victim is an elderly person specifically, division (I)(3) adds a further penalty beyond the felony-degree tier above: the offender must pay full restitution to the victim and a fine of up to $50,000, which is forwarded to the county department of job and family services for elder-abuse reporting, investigation, and protective services.

Social Security Number Restrictions (ORC 1349.17)

ORC 1349.17 restricts the recording of Social Security numbers, credit card numbers, and telephone numbers during consumer transactions. Businesses involved in credit card transactions may not record a consumer's Social Security number as part of that transaction process. An exception applies when all three conditions are met: the recording serves a legitimate business purpose, including collections; the other party consents to the recording; and the recorded data is not disclosed to third parties for purposes other than collections and is not used to market unrelated goods or services.

Ohio Privacy Act (HB 801, 136th General Assembly): Narrow Pending Legislation

House Bill 801, introduced by Representative Russo on March 31, 2026, and referred to the House Committee on Technology and Innovation on May 13, 2026, would enact section 149.61 of the Ohio Revised Code and is named the Ohio Privacy Act.

The scope of HB 801 is narrow. The bill targets state government entities, barring them from collecting, recording, or sharing an individual's identifying information or personal data with out-of-state entities except where otherwise required by law or permitted for government operations. It is not a comprehensive consumer privacy statute granting individual rights against private businesses.

HB 801 should not be confused with the broader consumer privacy frameworks enacted in California, Virginia, Colorado, or Texas. It addresses a specific concern about state government sharing resident data across state lines, not the full spectrum of consumer data rights.

As of May 2026, the bill remains pending before the House Committee on Technology and Innovation with no scheduled hearings announced.

Ohio's Failed Attempts at Comprehensive Privacy Legislation

Ohio has made multiple attempts to pass comprehensive consumer privacy legislation. None have succeeded.

HB 376 (134th General Assembly, 2021)

House Bill 376 was introduced during the 134th General Assembly and would have established the Ohio Personal Privacy Act with data rights for Ohio consumers. The bill was re-referred to the Rules and Reference Committee in February 2022 and died without advancing to a floor vote.

HB 345 (135th General Assembly, 2023)

House Bill 345 was introduced during the 135th General Assembly on November 29, 2023, and would have enacted the Ohio Personal Privacy Act establishing consumer rights similar to those in California, Virginia, and Colorado. The bill was referred to the Government Oversight Committee in December 2023 and died in committee.

Both bills would have applied to businesses conducting business in Ohio that either had annual gross revenues exceeding $25 million, processed data of 100,000 or more consumers, or derived more than 50% of gross revenue from data sales while processing data of 25,000 or more consumers. Both would have granted the Attorney General exclusive enforcement authority.

As of May 2026, no comprehensive consumer privacy bill has advanced in the 136th General Assembly.

How Ohio Compares to Other States

Ohio's patchwork approach puts it behind states with comprehensive privacy laws. As of May 2026, more than 20 states have enacted comprehensive consumer data privacy statutes.

California residents have the broadest rights in the nation under CCPA and CPRA, enforced by the dedicated California Privacy Protection Agency. Virginia, Colorado, Connecticut, Texas, and more than 15 other states grant consumers explicit rights to access, delete, correct, and opt out of the sale and sharing of personal data.

Ohio residents have no generally applicable version of those rights against private businesses under state law. The rights available under ORC Chapter 1347 apply only to personal information held by state government agencies, and the single private-sector exception, ORC Chapter 3904, reaches only life, health, and disability insurance.

Ohio's Data Protection Act safe harbor remains unique nationwide. No other state offers the same voluntary cybersecurity incentive structure for businesses. The approach reflects a business-friendly philosophy that uses legal incentives rather than punitive mandates.

Federal Framework: What Applies to Ohio Residents

Because Ohio lacks a comprehensive consumer privacy law, federal statutes play a critical role in data protection for Ohio residents in specific sectors.

HIPAA

The Health Insurance Portability and Accountability Act protects health information held by covered entities including hospitals, health insurers, and healthcare providers operating in Ohio. HIPAA's Privacy Rule, Security Rule, and Breach Notification Rule establish baseline protections for protected health information nationwide.

GLBA

The Gramm-Leach-Bliley Act requires financial institutions doing business in Ohio to provide privacy notices explaining their information-sharing practices and to implement safeguards protecting consumer financial information. GLBA-regulated entities are exempt from Ohio's breach notification law because they operate under equivalent federal requirements.

FERPA

The Family Educational Rights and Privacy Act protects student education records at institutions receiving federal funding. Combined with ORC 3319.321, this creates a two-layer protection system for Ohio students' educational records.

COPPA

The Children's Online Privacy Protection Act protects the personal information of children under 13 collected by websites and online services. The Federal Trade Commission enforces COPPA nationally, including for services accessed by Ohio children. The FTC finalized updated COPPA rules in January 2025, published in the Federal Register on April 22, 2025, with stronger protections for child data in ed-tech and online platforms.

FCRA

The Fair Credit Reporting Act regulates how consumer reporting agencies collect, use, and share consumer credit information. Ohio residents can access free credit reports, dispute inaccurate information, and place fraud alerts through the FCRA framework, regardless of state law.

FTC Act Section 5

The Federal Trade Commission enforces Section 5 of the FTC Act against unfair or deceptive acts or practices affecting commerce. The FTC has used this authority to bring enforcement actions against companies that misrepresent their data security practices or fail to implement reasonable security, providing a federal backstop for Ohio residents.

TAKE IT DOWN Act (Pub. L. 119-12)

The TAKE IT DOWN Act, signed into law on May 19, 2025, criminalizes the publication of nonconsensual intimate visual depictions, including AI-generated deepfakes. The Act requires covered online platforms to establish processes for users to request removal of nonconsensual intimate images and to remove those images (and known identical copies) within 48 hours of a valid notice.

The FTC is the enforcement agency. The platform takedown obligations took effect on May 19, 2026, and platforms that fail to comply face civil penalties of up to $53,088 per violation. Ohio residents who are victims of nonconsensual intimate image sharing can submit removal requests directly to covered platforms under this federal law.

American Privacy Rights Act (APRA): Did Not Pass

The American Privacy Rights Act, a bipartisan bicameral draft released in April 2024, would have established a federal comprehensive privacy framework. The bill did not advance to a floor vote in the 118th Congress and expired when that Congress ended in January 2025. As of May 2026, APRA has not been reintroduced in the 119th Congress. Ohio residents should not anticipate any federal comprehensive privacy legislation in the near term.

Practical Guidance: Businesses Operating in Ohio

Businesses that handle personal information of Ohio residents face several concrete obligations even without a comprehensive privacy law.

Step 1: Implement a written cybersecurity program. Adopt and document a program that reasonably conforms to one of the recognized frameworks in ORC 1354.03. This is the condition for the Data Protection Act safe harbor.

Step 2: Establish a breach response plan. Document your procedure for identifying, assessing, and responding to data breaches. Build in the 45-day notification clock required by ORC 1349.19 and plan for the 1,000-resident threshold triggering consumer reporting agency notification.

Step 3: Audit your privacy disclosures. Under the CSPA, misrepresentations about data security practices are actionable. Ensure your privacy policy and consumer communications accurately reflect your actual data handling and security practices.

Step 4: Assess federal overlay obligations. If you handle health data, financial data, education records, or children's data, identify your specific obligations under HIPAA, GLBA, FERPA, or COPPA. These operate independently of state law.

Step 5: Monitor Ohio legislative developments. HB 801 is pending and concerns state government data sharing, not private businesses. However, the 136th General Assembly could introduce broader consumer privacy legislation. Ohio's failure to pass HB 376 and HB 345 does not preclude future attempts.

Step 6: Check TAKE IT DOWN Act compliance. If you operate an online platform where users share content, assess whether you are a covered platform under the Act and whether your notice-and-removal process meets the 48-hour requirement.

How Ohio Residents Can Exercise Existing Rights

Ohio residents have fewer self-help tools than residents of comprehensive-privacy-law states. However, several avenues are available.

Data held by state agencies. Under ORC Chapter 1347, request confirmation, inspection, and correction of personal information held by any Ohio state agency or political subdivision. Contact the relevant agency's records office directly.

Credit and financial data. Under the FCRA, request your free annual credit reports from AnnualCreditReport.com, dispute inaccurate information with consumer reporting agencies, and place fraud alerts or credit freezes if you suspect identity theft.

Life, health, or disability insurance data. Under ORC 3904.08 and ORC 3904.09, send a written request to the insurer, agent, or insurance support organization asking for the recorded personal information it holds about you, or asking it to correct, amend, or delete information you believe is wrong. It has thirty business days to respond, and if it refuses you may file a statement of disagreement that stays with the record.

Health data. Under HIPAA, request access to and copies of your medical records from covered healthcare providers. You can also request accounting of disclosures and restrict certain uses of your information.

Data breach notification. If a company you do business with suffers a breach, Ohio law requires notification within 45 days. If you believe notification was unreasonably delayed, you can file a complaint with the Ohio Attorney General's Consumer Protection Section.

Federal privacy complaints. File complaints with the FTC at ReportFraud.ftc.gov for deceptive data practices, with the CFPB for financial data issues, and with the FTC for COPPA violations involving children's data.

Nonconsensual intimate imagery. Under the TAKE IT DOWN Act, submit a removal request directly to the platform. If the platform fails to act within 48 hours, you can report violations to the FTC.

This article is for informational purposes only and does not constitute legal advice. Data privacy laws change frequently, and enforcement interpretations evolve over time. Consult a licensed attorney in Ohio for advice about your specific situation. Last reviewed: May 2026.

More Ohio Laws

• Ohio Deepfake Laws
• Ohio Employee Monitoring Laws
• Ohio GPS Tracking Laws
• Ohio Recording Laws