Enabled Jurisdictions Schedule

1. Rules that apply everywhere

These rules are enforced in CLICR’s software at the scanning device and at the point where data enters the venue’s database. No venue setting overrides them.

1. Four fields, and no more. In every state, the scanner reads and the venue database stores at most name, date of birth, ID number and expiration date. Sex or gender, address, zip code, height, eye color, photograph and every other field are never read, derived, displayed, logged or stored, whatever the state allows.
2. CLICR receives counts only. The only data CLICR itself receives from a venue’s operation is in/out headcounts by area and time, recorded from taps in the counting app. Nothing derived from a scan, including an age range, is sent to CLICR in any state.
3. Each business leases its own database. Scan records, ban lists and any venue analytics live in a database dedicated to that business, hosted by CLICR, encrypted with a key specific to that business, and partitioned by liquor licensee. CLICR has no standing read path to its contents.
4. No ban list is ever shared. A ban list belongs to a single liquor licensee and is never shared between venues, businesses or CLICR customers, including venues under common ownership.
5. Unmapped means off. A state not listed as enabled, or newly restricted by a change in law, defaults to “not enabled” until CLICR completes legal review.
6. The venue decides. Every election below (retention, ban list, venue analytics) is the venue’s decision under the ID Scanning Addendum, made after the venue has confirmed lawfulness with its own counsel. CLICR provides defaults and ceilings and enforces them; it does not choose for the venue.

2. Tiers

3. State-by-state configuration

Columns: Fields = maximum fields the venue database may hold. Ordinary retention = default period for scan records and the ceiling a venue may elect where a scan-based statutory defense exists. Ban list = whether the venue may enable a ban list and in what configuration ("Observation" means the configuration in Section 4). Venue analytics = whether the venue may enable the age-range report inside its own database. Consent = whether patron consent is required before scanning.

4. The observation-list ban configuration

Where this schedule shows “Observation” or “Observation only,” a venue may enable a ban list that works as follows, and only as follows.

Entries are created by venue staff at or about the time of an incident, from their own observation. Staff type the individual’s name and date of birth, or confirm them from the face of the ID, choose a reason from a fixed list of lawful security grounds (violence, threats, theft, sexual misconduct, weapons, fraudulent identification, refusal to comply with staff), and set an expiry that defaults to one year and may run to five years only for violence or weapons. The exclusion is communicated to the individual at the time. No entry is created from, linked to or populated by a scan record.

At the door, the name and date of birth decoded from the ID at the moment of scan are compared in device memory against the venue’s list. On a match, staff see the name, date of birth and “banned,” and a manager confirms before anyone is refused entry. No record of the match is written, the ID number is not used in the comparison, and stored scan records are not read. No photograph or biometric is captured or compared. No persistent identifier is assigned to scanned patrons.

The list is scoped to one liquor licensee, can be reviewed and corrected by the venue at any time, and is never shared. In use-limited states (New York, Ohio) the venue acknowledges the residual consideration noted in Section 3 when it enables the feature. The ban list is not available in California, where the statute bars any use of scan information beyond the verification itself.

5. The venue analytics election

Where this schedule shows “Venue election,” a venue may turn on an age-range report inside its own database. The report groups the venue’s own scans into age ranges by area and time interval, derived only from the date of birth field the venue already holds. No cell is shown unless at least ten scans sit behind it; smaller cells roll up into a coarser bucket. The report is the venue’s, stays in the venue’s database, appears only on the venue’s dashboard, and is not sent to, read by or used by CLICR. It is not available where this schedule shows “Off,” and in consent-gated states only where the venue’s consent disclosure covers it.

5A. Defense-period retention (New York, Ohio and Pennsylvania)

Where this schedule shows a defense ceiling, a venue may keep the four permitted fields beyond 21 days, up to the ceiling, only to preserve a transaction-scan record that supports a statutory defense (New York: ABC Law § 65-b(7)(a); Ohio: ORC § 4301.611; Pennsylvania: 47 P.S. § 4-495(g), which requires the licensee to establish that the card was identified as valid by a transaction scan device and was relied upon in good faith), and only after recording that reason in the Service. The statutes set no retention period; retention is lawful for as long as it is necessary to that purpose and for no other. A proceeding for serving or admitting an underage patron is brought after the event and a venue may not learn of it for weeks, so a record deleted at 21 days cannot support the defense. The 90-day ceiling is set to cover the period in which a charge is most likely to be brought while keeping the record short enough that it serves no other purpose. Records kept under this election are used for nothing else and may be shortened at any time.

6. Change of law

CLICR reviews this schedule quarterly and on any change in law or regulator guidance. CLICR may restrict or disable the feature in a state on notice under Section A-8(c) of the ID Scanning Addendum. Scheduled changes already known: Delaware, January 1, 2027 (government ID numbers become sensitive data; consent build required); Vermont, January 1, 2028 (Act 145). Each version of this schedule is dated and prior versions are archived.