Ohio AI Legislation in 2026

The Ohio Picture

Ohio in mid-2026 occupies an unusual position among large states. It has no comprehensive AI statute, and despite a Senate that passed Senate Bill 163 unanimously in May, no AI-specific bill has yet become law. I want builders to read that precisely. The legally binding AI governance in Ohio today is not legislation at all. It is the Department of Administrative Services policy IT-17, which has been in effect since December 2023 and binds only state agencies and their vendors. If you sell AI into Ohio state government, IT-17 and the multi-agency AI Council are the operative gate. If you sell AI to private Ohioans or businesses, there is currently no Ohio statute that directly regulates your model.

What makes Ohio distinctive is House Bill 469, the AI non-personhood bill. While most states are debating disclosure, bias audits, and consumer protection, Ohio is the state legislating the metaphysics. HB 469 would declare AI systems nonsentient as a matter of Ohio law, forbid any grant of legal personhood, bar AI from marrying, holding a job title, or owning property, and route all liability for AI harm to the human developer or user. The intent is to ensure courts can always trace responsibility to a person and that no defendant can blame the machine. Builders should note the liability angle carefully. Critics warn the definition of AI is broad enough to sweep in ordinary rules-based software. Even though HB 469 is still in committee and not law, its liability-to-the-human principle signals the direction Ohio policymakers favor.

The enforcement pressure Ohio builders feel right now is mostly federal, not state. The federal Take It Down Act already criminalizes nonconsensual intimate deepfakes nationwide, and federal law reaches AI-generated CSAM. Ohio is racing to add its own state offenses through SB 163, which would criminalize AI-CSAM, penalize deepfakes used for fraud, reputational harm, or sexual depiction, and, notably, require a visible watermark on AI-generated content. The watermarking requirement is the provision builders should watch most closely, because if SB 163 is enacted in its current form it would impose a concrete product obligation on anyone generating synthetic media for the Ohio market.

My guidance to builders is to treat Ohio as a low-statute, high-trajectory jurisdiction. Do not assume the absence of a comprehensive law means a free hand. First, if you touch state contracts, comply with DAS IT-17 and engage the AI Council early. Second, design now for content provenance and watermarking, because SB 163 has cleared the Senate unanimously. Third, assume the human-liability principle of HB 469 even before it passes, and keep clear human accountability for any AI decision that affects an Ohioan. Fourth, if you operate in health insurance or behavioral health, track the pending SB 164 and HB 525.