COLUMBUS, Ohio — An Ohio House bill that began as a narrow limit on companies selling license-plate camera data has been rewritten into the state's first comprehensive rules for police plate readers — with a fifth-degree felony for misuse, a court order required for older data, deletion within 180 days, and, most controversially, a change that would exempt police searches of that data from public records requests. The House Public Safety Committee held its fourth hearing on House Bill 725 on Tuesday, November 17, with 11 proponents, 11 opponents and 3 interested parties filing testimony, and took no vote, according to the committee record summarised in reporting by the Columbus Dispatch and other Ohio outlets.
Source: Columbus Dispatch, Nov. 16, 2026, via AI Spy Tech summary of HB 725
The bill, sponsored by Rep. Kevin D. Miller, a Newark Republican, covers automated license plate recognition systems — fixed or mobile cameras, including those sold by Flock Safety, that convert plate images into searchable data recording a vehicle's plate, make, model and colour, and the date, time and general location of each scan. Lorain police, in earlier Ohio reporting, described using fixed Flock cameras to find stolen vehicles and missing people and to investigate serious crimes. What the substitute version adds is a rulebook for the police use itself — and a fight over whether the public will still be able to see how that rulebook is used.
How the bill changed since March
House Bill 725 had its first hearing on March 11, 2026. As introduced, it is two pages long: it bars any person from, for commercial purposes, knowingly collecting, using, selling, transferring or sharing plate data, with exemptions for normal business activity such as insurance and regulating access to private property, and it expressly exempted police use “in the course of the agency or officer's law enforcement activities.” In sponsor testimony on March 11, Miller described the bill as closing “a loophole in Ohio law where private entities or third parties can collect and monetize license plate scan data for commercial purposes,” and said it “does not interfere with legitimate law enforcement use of ALPR systems.”
Source: Ohio Legislature — HB 725 sponsor testimony and bill as introduced
The substitute version, posted for the committee's November hearings and described in testimony filed for November 17, is far broader. Police access is tiered by the age of the data: under 30 days old, use is limited to an active criminal investigation or a qualifying emergency; from 30 to 180 days old, a court order is also generally required, according to testimony from the Ohio Association of Chiefs of Police summarised by the Lake Erie Inquiry from the Norwalk Reflector's November 11 report. The ACLU of Ohio's testimony notes that a petitioner is “not required to establish probable cause or identify a suspect in order to obtain a court order” — a point the group raises against the bill. Agencies would also have to adopt a policy on ethical use, with standards for internal audits.
Source: Lake Erie Inquiry / Norwalk Reflector, Nov. 11-15, 2026
The records change at the centre of the fight
Ohio law already shields the camera data itself. The state's Public Records Act, Ohio Revised Code 149.43, excludes “images and data captured by an automated license plate recognition system that are maintained in a law enforcement database” — an exemption that took effect on September 30, 2025, cleveland.com reported. That exemption does not cover every record about the cameras, such as policies or contracts. Crucially, logs of officers' searches of the data have been released as public records under current law, and the Dispatch's reporting depended on them: a Dispatch analysis of Flock records showed Columbus police leadership used the database to monitor the actions of U.S. Immigration and Customs Enforcement during “Operation Buckeye” in December 2025, and Columbus Mayor Andrew Ginther paused the city's use of Flock cameras after the Dispatch asked questions about data analysed by USA Today Network journalists.
The substitute version would exempt law-enforcement searches of plate-reader data from public records requests, according to ACLU of Ohio testimony. Miller told the committee on November 10 that the change was needed because the data can “compromise active investigations,” the Dispatch reported, and said the felony penalties would be similar to those for misusing other types of law-enforcement databases. Gary Daniels, legislative director of the ACLU of Ohio, told the Dispatch he has not seen anything in publicly disclosed audit logs that would compromise an active investigation. “This seems to be the latest attempt to shut off avenues of government transparency and accountability,” Daniels said. He also argued that the bill's text, which says a court “shall” order extensions, removes judicial discretion. Miller did not respond to the Dispatch's request for comment.
Who testified — and where the sides stand
Groups filing testimony in support of the substitute included the Ohio Fraternal Order of Police, the Ohio Association of Chiefs of Police, the Ohio Prosecuting Attorneys Association, the Buckeye State Sheriff's Association, the Ohio Mayors Alliance, the Ohio Chamber of Commerce and Flock Safety, according to the committee's testimony list. Flock Safety's written testimony says the company “supports and applauds HB 725,” that data from a customer's cameras “belongs to and is controlled by that customer, not Flock,” that the customer sets the retention period, and that “Flock does not sell customer data to third parties.” Against the bill, the ACLU of Ohio testified that its position on government use of the cameras is “we want them banned,” pointing to New Hampshire's law requiring deletion within three minutes unless specific categories apply; the Ohio Association of Repossessors testified against the bill's limits on commercial use.
House Bill 725 is not the only plate-reader bill in Columbus. Four more were introduced in September, according to the ACLU of Ohio: Senate Bill 469 (Sen. Cutrona) would require deletion after 10 days unless data is part of an investigation, with monthly internal audits and a ban on cameras within 500 feet of a house of worship or a firearms retailer; House Bill 1010 (Rep. Dean) proposes a general ban with exceptions, a warrant requirement and deletion within 90 days, with cosponsors from both parties; House Bill 1011 (Rep. Click) proposes a one-year moratorium with exceptions; and House Bill 1009 (Reps. Newman and Willis) would extend the existing fifth-degree felony for misusing law-enforcement databases to plate-reader and other surveillance databases. The ACLU of Ohio wrote on November 6 that it is not expected any of the bills will pass during the current legislative session, which ends December 31.
Plate readers record where a vehicle was, and when, every time it passes a camera — data that can map a family's school run, a gurdwara visit or a trucker's route. Ohio has no statewide law today setting how long police may keep that data, what an officer must establish before searching it, who may receive it, or how its use must be audited, a cleveland.com review found. Audit logs released as public records are how Ohioans learned of immigration-related searches of cameras in several Ohio cities by outside agencies — the same logs the substitute bill would place beyond public records requests.
What happens next
As of the afternoon of November 17, the bill had not had a committee vote and no later hearing was posted, according to its committee page. To become law, House Bill 725 would still need to be reported by the House Public Safety Committee — which meets in Room 114 of the Ohio Statehouse, 1 Capitol Square, Columbus, and is chaired by Rep. Cindy Abrams — then pass the full House and the Senate and be sent to the governor, all before the legislative session ends on December 31. Until then, the current rules stand: camera images and data in a law-enforcement database are already exempt from public records, search logs have been treated as public, Flock Safety's announced default retention is seven days (cut from 30 days in August, the Dispatch reported), and individual agencies such as Cleveland's police — whose policy generally limits stored data to 30 days, with exceptions for evidence — set their own limits.
