The Temp Signed With the Agency. The Scanner Belongs to the Client.
Contingent labour is the one arrangement where BIPA's plain wording and everyone's mental model come apart. The statute follows the identifier — who collected it, who holds it — while the paperwork follows the employment relationship. In a staffing placement those two chains point at different companies.
The Assumption That Creates the Exposure
The standard light-industrial placement works like this. A worker completes onboarding with the staffing agency, signs a stack that includes a biometric consent form, and reports to a warehouse or plant the agency never operates. At the client site the worker clocks in on the client's hand-geometry or facial-recognition terminal, wired to the client's timekeeping system, administered by the client's HR software. The agency invoices from hours the client's system produced.
Both sides read that arrangement as one where the agency owns compliance, because the agency owns the employment paperwork. The statute does not describe it that way. Its consent obligation is written against the entity that collects, captures, purchases, receives through trade, or otherwise obtains the identifier, and its policy, safeguarding, and retention obligations are written against any entity in possession of one. Neither phrase mentions employment. The client site collects at the terminal and possesses in the database, which makes it a regulated party in its own right.
Where Each Party Actually Stands
Client Site: Collector and Possessor, Usually Undocumented
HIGHEST EXPOSUREThe terminal at the door is a collection event, and the stored template is possession. That means the client owes its own informed written release identifying itself as the collector, its own stated purpose and length of use, and its own published retention and destruction policy. Most client sites have none of these because they never considered themselves the employer of the person at the clock.
Staffing Agency: Signed the Release, Named the Wrong Party
DEFECTIVE CONSENTAn agency release that describes only the agency's purpose and retention period does not supply what the client needs, and can be argued not to constitute informed consent for a collection the worker was never told about. A release also cannot be a blanket for a client roster the worker has not been identified to.
Timekeeping Vendor: In Possession, Sometimes Also Receiving
OVERLOOKED PARTYA hosted workforce-management platform holding templates is in possession, and a vendor that ingests templates from the client is arguably obtaining them. Vendor contracts frequently characterise this as mere processing, which is a data-protection concept BIPA does not use.
Gap: Destruction at End of Assignment
RETENTION GAPContingent placements end and restart constantly, and each ending satisfies the purpose for which the template was collected. Systems built for permanent headcount hold enrolment records indefinitely against a possible return, which converts a routine assignment completion into a retention violation running for years.
Mitigant: A Client-Named Release Executed Before First Shift
MITIGATES RISKA release that names the specific client site as a collector, states that site's purpose and retention period, and is signed before the worker touches the terminal closes the main defect without changing the operational model. It has to be per-placement rather than a general agency form.
Why Contingent Labour Concentrates the Claim
BIPA carries a private right of action with statutory damages and does not require any showing of downstream harm, so the size of a claim scales with the number of people enrolled under a defective process. Staffing is uniquely bad on that axis: a single client site can cycle hundreds of workers through one terminal in a year, every one of them enrolled by the same packet, every enrolment identical in its defect. There is no variation for a defendant to argue over.
The employment-relationship defence that feels intuitive here — we were not their employer — does not engage the statute's terms. It is also the wrong instinct strategically, because arguing about employment status invites the joint-employment analysis to be run for every other purpose too. The cleaner position is to accept the collection role and document it properly, which costs one form per placement.
The Compliance Set for a Staffing Arrangement
Issue a per-client release, not a general agency form
Name the client site as a collector, state that site's specific purpose for the scan and its retention period, and obtain the signature before the first shift. Build it into the placement workflow so a new client automatically produces a new form.
Have the client publish its own retention policy
The policy has to be publicly available and belong to the entity in possession. A client site relying on the agency's published policy has not satisfied its own obligation, and the omission is trivially provable from the website.
Wire destruction to the assignment-end event, not to a calendar
When a placement closes, the template's purpose is satisfied. Trigger deletion off the same system event that closes the assignment rather than a periodic sweep, and log the deletion so it is evidenced.
Inventory who holds a template, including the vendor
Terminal firmware, on-premise timekeeping servers, the hosted workforce platform, and any HRIS sync can each hold a copy. Every holder is in possession, so map them before writing any policy that claims a retention period.
Offer a non-biometric clock-in alternative and record who takes it
A badge or PIN path removes objectors from the enrolled population entirely, which shrinks the class and demonstrates that consent was genuinely optional rather than a condition of the shift.
Treat the indemnity clause as cost allocation only
Negotiate it, but do not let it substitute for a compliance programme on either side. The statutory duty stays with the collector and the possessor regardless of what the master services agreement allocates.
Frequently Asked Questions
If the staffing agency collected the BIPA release, is the client site covered?
Not automatically. The written-release requirement attaches to the private entity that collects, captures, or otherwise obtains the identifier, and the safeguarding and retention duties attach to any entity in possession. If the scanner sits at the client site and the client's system holds the template, the client is in that chain on its own footing — a release naming only the agency does not identify the client as a collector or state the client's purpose and retention period.
Does BIPA have a joint-employer doctrine like wage-and-hour law does?
It does not need one, and that is the point staffing counsel most often miss. Wage-and-hour analysis asks who controls the worker. BIPA asks who collects and who possesses the identifier. A client site can fail the control test for joint employment and still be squarely liable because the hardware and the stored template are its own.
Who has to publish the retention and destruction schedule for temp-worker biometrics?
Every entity in possession needs a publicly available written policy with a retention schedule and destruction guidelines, and the statutory trigger is the earlier of the purpose being satisfied or three years after the individual's last interaction. For contingent labour that trigger fires constantly — an assignment that ends is a purpose satisfied — so the practical failure is not the missing policy but a policy nobody executes at end of assignment.
Can the staffing contract shift BIPA liability to one party?
Indemnification can move the cost of a claim between the parties, but it cannot move the statutory duty. A client site that collects and possesses templates still owes its own release, policy, and safeguards to the worker no matter what the master services agreement says. Treat the indemnity clause as loss allocation between businesses and the compliance programme as non-delegable.
Does using a facial-recognition or hand-geometry clock instead of a fingerprint change the analysis?
No. Fingerprints, voiceprints, retina and iris scans, and hand and face geometry are all enumerated biometric identifiers, and a mathematical template derived from any of them is biometric information. Vendors sometimes market a template-only or hashed system as outside the statute; the derivation from a physical characteristic is what brings it in, not whether the raw image was retained.
Reviewing a Biometric Timekeeping Vendor
RatedWithAI covers workforce and identity-verification tools on the questions that decide statutory exposure: where the template is stored, who else holds a copy, and whether the platform can execute a deletion on an assignment-end event.
Explore Biometric Privacy Guides