State guide

Ohio ID scanning law: what 4301.61 and 4301.611 say

Last reviewed September 2026

For Ohio liquor permit holders: section 4301.611 ties an affirmative defense to an ID transaction scan, and 4301.61 limits what scan data may be kept, used or shared.

What the law says

Who and what is covered

Sections 4301.61 and 4301.611 apply to Ohio liquor permit holders and their agents and employees (4301.61(A)(3)). A “transaction scan” is a check, with a transaction scan device, of a license or ID card presented to buy beer, liquor or a low-alcohol beverage, or to enter 21-and-over premises with an on-premises liquor permit (4301.61(A)(4)). Tobacco and nicotine scans have their own section, 2927.021.

Under 4301.61(B)(1), a permit holder “may” scan. Under (B)(2), if the scanned information “fails to match the information printed on” the card, or indicates it’s false or fraudulent, the permit holder and its staff shall not sell alcohol to the card holder.

The affirmative defense (4301.611)

Section 4301.611 lets a permit holder, agent or employee charged under Ohio’s liquor law or a Liquor Control Commission rule, where the buyer’s age is an element, raise an affirmative defense by proving that:

• the buyer presented a driver’s license, commercial driver’s license or ID card;
• a transaction scan of it indicated that the license or card was valid; and
• the sale was made in reasonable reliance on the ID and the completed scan.

The commission or court shall consider any written policy the permit holder has adopted and implemented to prevent underage sales. It shall also consider that reasonable reliance may require reasonable diligence, which a scan device does not excuse, in determining the buyer’s age and whether the card’s description and picture are the holder’s (4301.611(B)).

Good-faith acceptance of an ID (4301.639)

Section 4301.639 is a separate defense that doesn’t involve scanning. It applies if the commission or a court finds that the buyer showed a listed type of ID that displays the holder’s picture and shows the required age, and the seller made a bona fide effort to compare its description with the buyer and check it hadn’t been altered, and had reason to believe the buyer was of legal age. It is in addition to the 4301.611 defense (4301.639(C)).

Keeping and sharing scan data (4301.61(D))

Section 4301.61(D)(1) prohibits recording or maintaining any scan-derived information except the cardholder’s name and date of birth and the card’s expiration date and ID number, and doesn’t require recording them. Scan information may be used only for purposes of 4301.611 ((D)(2)), and the scan device only for alcohol sales or 21-and-over admission ((D)(3)). It may not be sold or shared with any third party, including for marketing, except under a court order or as the Revised Code specifically authorizes ((D)(4)). A court may impose a civil penalty of up to $1,000 for each violation of (B)(2) or (D) (4301.61(F)).

What it means at the counter

The definition of a transaction scan covers entry checks at 21-and-over, on-premises permit premises (4301.61(A)(4)(b)), but the defense’s third condition is about the sale. Whether a door scan supports the defense for a later sale is a question for your lawyer.

Where Check ID fits

Check ID is a tool that helps your staff check IDs. It reads the barcode on US and Canadian licenses and ID cards, checks the birth and expiry dates against your rules, and shows a clear result, such as Verified, Underage or Expired ID. Verified means only that the dates meet your rules; your staff make the call. It doesn’t compare the barcode with what’s printed on the card, or the photo with the person. It can’t tell whether a card is genuine: a well-made fake can carry a valid barcode. We don’t claim it’s a “transaction scan device,” or that its result “indicated that the license or card was valid.”

A scan record never keeps the name, date of birth, address, ID number or a picture of the ID. It keeps details such as the result, age in whole years, issuing state or country, document type, and when and how the ID was scanned. Free and Pro scan history covers 7 days on your device or in your iCloud and can be turned off in Settings. Check ID for Teams (coming soon) keeps records on our servers for two years by default, adjustable from 30 days to about ten years.

Repeat-entry alerts use a one-way code made from the barcode, still derived from personal data. While alerts are on, each device keeps its own copy and clears codes older than 7 days at the first scan after the app restarts. On Check ID for Teams, our servers also keep a keyed copy by default for US venues outside New Hampshire, including Ohio, and delete it after the repeat-entry window (4 hours by default). Owners and managers can change that per venue. None of these defaults is built around Ohio’s rule.

Personal guest lists hold the names you add, which can include one saved from a scan. Teams guest lists hold the names your team types in or imports. Our product analytics include coarse scan statistics, such as the result, state and age, but never a name, birth date, address, ID number or photo. Security & data describes what’s kept on each plan.

Whether 4301.61(D) allows these records and uses, including repeat-entry alerts and guest lists, whether a service such as Check ID or iCloud is a “third party” under (D)(4), and whether a scan helps you under 4301.611 are questions for your lawyer.

Frequently asked questions

Sources

• Ohio Rev. Code 4301.61, retrieved September 2026.
• Ohio Rev. Code 4301.611, retrieved September 2026.
• Ohio Rev. Code 4301.639, retrieved September 2026.
• Ohio Rev. Code 2927.021, retrieved September 2026.
• Ohio Division of Liquor Control, retrieved September 2026.