BIPA Compliance for Biometric Time Clocks After the Ruling
BIPA compliance for biometric time clocks comes down to three things you finish before anyone's first scan: a written notice, a signed written release, and a public retention and destruction policy. The Seventh Circuit's April 1, 2026 ruling changed how damages are counted in lawsuits (one recovery per person instead of one per scan, even in cases filed before the 2024 amendment). It didn't change a single one of those duties.
Who this is for: HR, payroll and operations leaders who run, or plan to run, fingerprint, hand or face scanning clocks for employees in Illinois.
Key takeaways
- The Seventh Circuit treated the 2024 damages amendment as a remedial change, so the one-recovery-per-person rule applies to cases that were already pending, not just new ones.
- Section 15 of BIPA, which holds the notice, release, retention, disclosure and security rules, was not touched. Your compliance checklist is the same as it was in 2023.
- A capped, predictable number per employee is easier for plaintiffs' firms to model across a whole workforce, so lower damages don't mean lower risk of being sued.
- Before rollout you need a standalone notice and release, a public retention schedule, vendor terms that match your promises, and a non-biometric way to clock in.
- If clocks are already live, audit consent records for every enrolled employee, not just recent hires.
What does BIPA compliance for biometric time clocks require?
It requires you to tell employees in writing what you're collecting and why, get a signed release, publish a retention and destruction schedule, and then protect, limit and eventually destroy the data. All of it sits in Section 15 of the Biometric Information Privacy Act.
First, a few plain definitions. A biometric identifier under BIPA is a retina or iris scan, fingerprint, voiceprint, or scan of hand or face geometry. Photographs are expressly excluded, which matters if you're comparing a face geometry clock with a clock that only snaps a photo at punch time. Biometric information is anything derived from those identifiers, such as the template a clock stores. A written release is informed written consent, an electronic signature, or, in the employment context, a release an employee signs as a condition of employment. Those definitions come from the amended Section 10 in Public Act 103-0769.
Under Section 15, a private employer must:
- Publish a written policy, available to the public, with a retention schedule and destruction guidelines. Data must be destroyed when the original purpose is satisfied or within three years of the person's last interaction with you, whichever comes first.
- Give written notice before collection that biometric data is being collected or stored, with the specific purpose and how long it will be kept.
- Get a written release from the employee before the first scan.
- Never sell, lease, trade or otherwise profit from the data.
- Not disclose it unless the employee consents, a law requires it, or a valid warrant or subpoena applies.
- Protect it with the reasonable standard of care in your industry, and at least as well as you protect other confidential and sensitive information.
One detail employers often miss: an employee doesn't have to show any real-world harm to sue. In its 2019 decision involving Six Flags, the Illinois Supreme Court held that a violation of the statute alone makes someone "aggrieved." The same court said the cost of following the law is "likely to be insignificant" next to the cost of ignoring it.
If you're still deciding between fingerprint and face scanning, our explainer on how facial recognition time clocks work and the laws that apply covers the hardware side.
What did the Seventh Circuit ruling change, and what didn't it?
It changed how damages are counted in lawsuits already filed. It didn't change what you have to do to comply.
Some history helps here. In February 2023, the Illinois Supreme Court's White Castle decision held that each scan collected without proper consent was a separate claim. For an hourly employee clocking in and out every shift for years, the numbers grew fast. As the Seventh Circuit's opinion recounts, White Castle argued its class-wide damages could exceed $17 billion.
The legislature responded with Public Act 103-0769 (SB 2979), effective August 2, 2024. It added Section 20(b): an employer that collects the same biometric identifier from the same person using the same method of collection, in more than one instance, has committed a single violation, with "at most, one recovery" for that person. Section 20(c) applies the same logic to repeated disclosures to the same recipient. The liquidated damages amounts stayed put: $1,000 or actual damages (whichever is greater) for a negligent violation, $5,000 or actual damages for an intentional or reckless one, plus reasonable attorneys' fees, costs and possible injunctions.
The amendment didn't say whether the cap applied to cases already filed, and district courts split. On April 1, 2026, in three consolidated appeals involving Union Pacific Railroad, Universal Intermodal Services and Central Transport, the Seventh Circuit held that it does. Two of those cases involved a biometric time clock; the third involved fingerprint scans to enter and exit facilities. The court reasoned that the legislature amended the remedy in Section 20 and left the liability rules in Section 15 alone. Under Illinois law a remedial change is procedural, so it applies to pending cases. In the court's words, the amendment "simply cabined the recovery available."
| Question | Before the 2024 amendment | After the amendment and the 2026 ruling |
|---|---|---|
| How are repeated scans counted? | Each scan could be a separate claim | One violation per person, per identifier, per collection method |
| Damages per violation | $1,000 negligent, $5,000 intentional or reckless | Unchanged |
| Notice, release and public policy duties | Required before collection | Unchanged |
| Electronic signature on the release | Not addressed in the statute | Expressly allowed |
| Applies to cases filed before August 2, 2024? | Not applicable | Yes, per the Seventh Circuit |
One limit worth knowing: the Seventh Circuit interprets Illinois law in federal cases. Illinois state courts aren't bound by it, so treat the retroactivity question as settled for federal cases and likely, but not certain, elsewhere.
How much exposure does a time clock without consent create?
Less than it did under the per-scan theory, but still enough to justify a lawsuit. Here's a worked example using the statutory figures, so you can run the same math for your own sites.
Say you run a 400-person distribution center in Illinois. Employees clock in and out on a fingerprint clock twice a day, about 250 shifts a year, for three years. Nobody signed a release.
| Counting method | Violations per employee | Negligent ($1,000) | Intentional or reckless ($5,000) |
|---|---|---|---|
| Per scan (the White Castle theory) | 1,500 | $600 million | $3 billion |
| Per person (2024 amendment) | 1 | $400,000 | $2 million |
Two caveats. Courts have discretion over damages, so neither row is an automatic judgment. And the per-person row excludes attorneys' fees, expert fees and your own defense costs, which the statute lets a winning plaintiff recover on top.
Now look at it from a plaintiffs' firm's side. The bottom row is a clean, predictable number they can calculate from your headcount before filing anything. Predictability tends to encourage filings, not discourage them. Here's where your situation puts you:
| Your situation | What the ruling means for you |
|---|---|
| Already sued over pre-2024 scans | Good news. Exposure is per person, which makes settlement talks more realistic. |
| Clocks live, paperwork uncertain | Exposure per person is smaller but easy to calculate across your workforce. Audit now. |
| Planning a rollout | Nothing in your compliance sequence changes. Get consent right before the first scan. |
How do you roll out a biometric time clock that complies?
Finish the paperwork, the public policy and the vendor contract before the first employee enrolls, then keep records that prove the order of events. This sequence works:
- Write and post the retention and destruction policy. Put it where employees and the public can find it, such as your careers site, not on an internal HR drive. Pick a concrete trigger, for example "templates are deleted within 30 days of separation," which comfortably beats the three-year outer limit.
- Draft a standalone notice and release. Don't bury it in an onboarding packet. Name the identifier (fingerprint, hand geometry or face geometry), state the purpose (timekeeping and attendance), say how long you'll keep it, and name who else will hold it, such as the clock vendor.
- Collect signatures before enrollment. Electronic signatures are expressly allowed now. Store each release with a timestamp and the employee ID.
- Match the vendor contract to your promises. Most clocks store templates in a vendor's cloud. Using a vendor doesn't transfer your obligations, so the contract should cover sub-processors, breach notification, encryption, no secondary use, and deletion on the same timeline your policy promises, with written confirmation.
- Offer a non-biometric option. A PIN, badge or QR punch for employees who decline or who request a religious or disability accommodation. Our comparison of alternatives to hardware time clocks covers the main options.
- Enroll, then log it. Record each employee's enrollment date so you can show the release predates the first scan.
- Destroy on schedule and keep a log. Record the date, the employee, the method and who confirmed it, including the vendor's deletion confirmation.
For the operational side of swapping out wall clocks, see our tablet time clock rollout plan. And because punches flow into payroll, check how the clock passes data to your HR system using our guide to time clock integration with HR software. Templates shouldn't travel with the punch data.
Questions to ask your time clock vendor
Competitors rarely give you this list, and it's where most gaps show up:
- Does the clock store a raw image or only a template, and where does the template live (device, vendor cloud, or both)?
- Which sub-processors can access templates, and will you notify us before adding one?
- How fast can you delete a single employee's template, and do you confirm deletion in writing, including backups?
- Can the clock run with biometrics turned off for specific employees?
- What is your breach notification window, and does it cover biometric data specifically?
- Will you sign contract terms that match our public retention policy word for word?
If your clocks are already live
Run an audit now rather than assuming the paperwork is fine:
- Match every active enrolled template to a signed release dated before that employee's first scan.
- Check that the retention policy is public and reflects what actually happens, including how the vendor deletes templates for former employees.
- Compare vendor contract terms with your public policy line by line.
- Confirm templates for people who left are being destroyed on your stated schedule, and never later than three years after their last interaction with you.
Biometric retention sits alongside every other HR records schedule, and those can conflict across states. Our guide to HR records retention for employees in multiple states shows how to reconcile them.
Common mistakes
- Re-papering new hires only. A company refreshes its consent form and collects signatures from new hires. Everyone enrolled under the old process stays uncovered, sometimes for years.
- A policy that lives on the intranet. Section 15(a) says "made available to the public." A page on your intranet doesn't meet that.
- Assuming the vendor handles it. The collecting employer owns the notice and release duties. Vendor marketing about "BIPA-ready" hardware doesn't change that.
- Reading the ruling as permission to relax. The cap affects damages only. The duties, the private right of action and the fee-shifting are all intact.
- Forgetting other states. Illinois is the strictest, but not the only one. Washington's biometric law (RCW 19.375) is enforced solely by the attorney general and excludes security purposes such as fraud and theft prevention. Multistate employers should map each location, and our overview of state AI employment laws in Colorado, Illinois and NYC covers related workplace technology rules.
FAQ
Does the Seventh Circuit ruling mean BIPA risk is low now?
No. It limits damages to one recovery per person per collection method and applies that limit to pending federal cases. The Section 15 duties are unchanged. An employer that never collected releases still faces up to $1,000 per employee for negligent violations and $5,000 for intentional or reckless ones, plus attorneys' fees.
Can employees sign the BIPA release electronically?
Yes. The 2024 amendment defines an electronic signature as an electronic sound, symbol or process attached to or logically associated with a record and adopted with intent to sign. Keep the release a clear, standalone document, store it with a timestamp, and make sure it was signed before the first scan.
Can we make signing the release a condition of employment?
BIPA's definition of written release includes a release executed by an employee as a condition of employment. That doesn't override accommodation duties under other laws, though. If an employee objects on religious or disability grounds, plan to offer a PIN or badge option rather than treating refusal as a resignation.
Does BIPA apply if our vendor stores the templates?
Yes. You're still the entity collecting the data, so notice and release are on you. Your release should tell employees the vendor will hold the data, and your contract should require the vendor to follow the same retention, security and disclosure limits.
What to do next
- List every Illinois location using or planning biometric clocks, with headcount, so you can run the worked example above for your own exposure.
- Have employment counsel review your notice, release and public retention policy against Section 15.
- Reconcile enrolled employees against signed releases and fix gaps before the next scan.
- Send the vendor questions above and update contracts so destruction and breach terms match your public policy.
- Revisit whether biometrics are worth it for your use case. Our piece on whether biometrics are better than passwords lays out the tradeoffs.
This article is general information, not legal advice. Confirm your program with employment counsel.
Sources
- 740 ILCS 14/15, Biometric Information Privacy Act: Retention, collection, disclosure and destruction, Illinois General Assembly
- Public Act 103-0769 (SB 2979), Illinois General Assembly
- U.S. Court of Appeals for the Seventh Circuit, No. 25-2185 (April 1, 2026), GovInfo
- Illinois Supreme Court, 2019 IL 123186 (Six Flags Entertainment Corp.), Illinois Courts
- RCW 19.375, Biometric identifiers, Washington State Legislature
Last reviewed: November 2026.

Comments
Post a Comment