Cothron v. White Castle: Every Scan Is a New Claim

Picture the morning line at a White Castle: badge out, thumb down on a small black scanner, coffee not even poured yet. It takes less than a second. Nobody in that line is thinking about a lawsuit. But in Illinois, under one statute, that single second can become its own legal claim, and if it happens every shift, for years, across a whole workforce, the math gets very big, very fast. (Somewhere, a general counsel is running that math on a napkin and losing their appetite for sliders.)

That’s the question the Illinois Supreme Court answered in Cothron v. White Castle System, Inc. on February 17, 2023. The justices weren’t asked whether White Castle’s fingerprint scanners violated the state’s biometric privacy law. That wasn’t in front of them. They were asked something narrower, and far more consequential: when does the clock start, and how many violations are there, when the same scanner runs on the same employee thousands of times over years?

What happened

White Castle, like a lot of employers, used a fingerprint scanner so staff could access their pay stubs and authenticate access to company computer systems. No single scan looks dramatic: the system reads the fingerprint, converts it to a template, checks it, and, per the plaintiff’s allegations, sends data to a third-party vendor. But repeat that sequence daily, for years, across a workforce, and one employment relationship quietly generates thousands of scan-and-transmit events. Nobody notices that number building, until someone starts counting.

Someone did. The plaintiff, a former White Castle manager, argued that Illinois’ Biometric Information Privacy Act (BIPA) is violated each time a scan or transmission happens without the required consent, specifically under Sections 15(b), which requires informed consent before collecting a biometric identifier, and 15(d), which limits disclosure. White Castle argued the opposite: that the claim accrues once, at the first unauthorized scan, and every later scan is just a continuation of that first violation, not a new one. (A slightly rich argument from a company whose entire menu is built on convincing people that five small burgers are a fundamentally different experience from one big one.)

The gap between those two readings is not academic. The case reached the Illinois Supreme Court on a certified question from the U.S. Court of Appeals for the Seventh Circuit, because the answer decides whether an employer’s exposure is capped near the size of its workforce, or scales with the number of scans, a difference of orders of magnitude under BIPA’s per-violation statutory damages.

The court sided with the employee, 4-3. A separate claim accrues with each scan or each transmission that violates Sections 15(b) or 15(d), not only the first one. In dissent, Justice Overstreet warned the ruling could expose businesses to “annihilative liability,” which he described as damages that could far exceed any reasonable estimate of the actual harm.

The artifact: a scan log, not an enrollment form

Here is what that ruling changes on the ground: the evidentiary fight is no longer about whether a scanner exists. It’s about what the system recorded, and when, a question that used to be a footnote and is now the whole case.

An enrollment record shows one event: the day a fingerprint template was created. A scan log (if it exists, and if it was retained) shows something else entirely: a timestamped series of discrete authentication and transmission events, each one now a potential unit of liability. Whether that log exists, what it captures, how long it was kept, and whether every entry actually triggered a transmission to a vendor are technical questions, not legal ones. And now they decide exposure directly, not just liability in principle.

What a software expert witness tests in a biometric-accrual case

This is exactly where a source code expert witness does work a lawyer’s summary can’t reach. A generalist reads the vendor contract and the privacy policy and stops there. A court-grade software expert asks for the system architecture instead: where the scan happens, what gets converted to a template, what leaves the local device, what “transmission” technically means in this specific system, and how the logs that would count individual events are structured, retained, and exportable.

That cuts both ways. For a plaintiff class, proving how many violations occurred is a counting problem that lives in logs, not memory. For a defendant, showing that a given “scan” never generated a separate transmission, or that dedup logic collapsed repeat events into one record, can meaningfully narrow the class and the damages math. (The technical equivalent of insisting you only watched one episode when the streaming log says otherwise.) The underlying technical distinction is one a biometric workflow specialist would insist on drawing: that repeated scans and transmissions are separate technical events, not one continuous act of enrollment. A court-appointed expert isn’t there to argue the law. The expert’s job is to define the method for counting the events the law now cares about, one by one.

Why this matters beyond one company

BIPA is an Illinois statute, but the accrual logic it forced the court to confront doesn’t stay inside Illinois’ borders. Any system (access control, time clocks, device authentication, even repeated biometric checks in a consumer app) that scans the same person over and over creates the same structural question the moment a biometric privacy claim lands on the table: is this one violation, or is it as many violations as there were events?

For Israeli companies selling workforce or access-control software into markets with biometric privacy statutes, the lesson is worth learning long before any lawsuit arrives: know what your system logs, know whether “one scan” and “one transmission” are the same event or two, and know that the answer to that plumbing question can be the difference between a manageable claim and an existential one.

The above is general information and not legal advice. Case facts are drawn from the sources listed.