Skip to content

Session Expired

Your session has expired. Please sign in again to continue where you left off.

Sign In Again

OH HB 392: Enact the Ohio Right to Compute Act

In Committee Ohio

Last verified Oct 18, 2026 · official bill text

HB 392 · where it stands

1 of 5 steps complete
  1. Introduced In committee
  2. Passed first chamber
  3. Passed both chambers
  4. Enacted
  5. Effective
What do these statuses mean?
Introduced
Filed in the legislature; may be waiting for a committee hearing.
Passed a chamber
Approved by one or both chambers; awaiting further action.
Enacted
Signed into law, or became law without a signature or over a veto.
Effective date
The date the law says it takes effect. Once it has passed, the page shows "Effective" and the date. A court order can still block a law; if we know of one, the summary says so.
Dead / vetoed
Vetoed, failed, or the session ended without action.

In one paragraph

The Ohio Right to Compute Act would bar state agencies and local governments from restricting anyone's lawful use, development, deployment or possession of computing resources, including AI and machine learning systems, unless the restriction is narrowly tailored to a compelling governmental interest, such as critical infrastructure reliability, fraud, protecting minors from nonconsensual deepfakes, or rules for employees' AI use. Anyone operating an AI system that controls critical infrastructure would need a risk management policy following the NIST AI framework or another recognized standard. The House Technology and Innovation Committee reported an amended version on June 10, 2026.

Plain-English summary, written with AI assistance. The official text controls.

What it means for business

If enacted, Ohio state and local AI or computing rules would need a compelling interest, and operators of AI controlling critical infrastructure would need a NIST-style risk policy.

Key provisions

  1. New R.C. 9.89: state agencies and political subdivisions may not restrict lawful use, development, deployment or possession of a computational resource unless narrowly tailored to a compelling governmental interest
  2. 'Computational resource' includes hardware, software, algorithms, cryptography, AI and machine learning systems and quantum computing tools
  3. Compelling interests listed include critical infrastructure reliability, deception and fraud, protecting minors and vulnerable people from nonconsensual deepfakes, computing-infrastructure nuisances, and governing employees' AI use
  4. Operators of AI systems that control critical infrastructure must adopt a risk management policy meeting federal rules and the NIST AI Risk Management Framework or another recognized AI risk standard
  5. Exempt: AI limited to procedural or preparatory tasks or to carrying out decisions already made by a human, and pure antivirus, antimalware or cybersecurity tools
  6. Does not affect patent, trademark, copyright or trade secret rights
  7. Introduced July 7, 2025; reported as amended by House Technology and Innovation on June 10, 2026

Latest legislative action

Jun 10, 2026. Reported - Amended

Sponsors

NameRole
Primary
Primary
Cosponsor

Topics and industries

Affected industries

This page is general information, not legal advice. Summaries are AI-assisted and may contain errors; read the statute for the controlling text and talk to a lawyer about your situation. Full disclaimer · Report an error