Stop Buddy Punching With Face ID and Geofencing Safely

Face ID stops buddy punching because a coworker cannot lend their face the way they lend a badge or PIN, and geofencing stops punches from the parking lot or from home. Both collect sensitive data, so the program only works if you pair the technology with written consent, a published retention schedule and a non-biometric fallback.

Disclosure: The author works at CloudApper, which makes CloudApper AI TimeClock, which is discussed in this article.

Key takeaways

  • Badges, PINs and shared codes can all be handed to a coworker. A face match at the point of punch removes that option.
  • Geofencing answers a different question: whether the punch happened at the work location, not who made it.
  • In Illinois, the Biometric Information Privacy Act requires a public retention policy, written notice and a written release before you collect face data.
  • Design the policy, consent flow and fallback method before you enroll the first employee, not after.

What is buddy punching and why do badges and PINs fail?

Buddy punching is when one employee records time for another, usually clocking in a late coworker or clocking out someone who left early. It is hard to detect because the punch looks normal in the timecard. Supervisors notice only when they see someone arrive after their recorded start time, and few want to confront a team about it.

Every credential that can be carried can be shared. Badges are lent, PINs are written on the back of a phone, and QR codes can be screenshotted. Our earlier piece on addressing employee time theft covers the culture side: most buddy punching is a favor between friends rather than organized fraud, which is why controls should be routine and impersonal rather than accusatory.

How do face ID and geofencing stop time theft?

The two controls answer different questions, and many organizations need both.

ControlQuestion it answersStopsDoes not stop
Face ID at a shared tabletIs this the right person?Buddy punching with lent badges or PINsPunching from the wrong site if devices are portable
Geofencing on a phone or tabletIs the punch at an approved location?Clocking in from the car, home or another siteOne employee punching for another on the same phone
Face ID plus geofencingRight person, right place?Both patterns aboveOff the clock work, which is a scheduling and culture issue
Badge or PIN onlyWas a valid credential presented?Simple mistakesShared credentials

For example, CloudApper AI TimeClock lists a Face ID Agent for touchless check-in that "prevents buddy punching" and a Location Verification Agent that combines geofencing with face biometrics. It also supports QR code, barcode and NFC punches, which matters for the fallback method discussed below. UKG customers can compare how these controls fit their platform in our guide on stopping employee time theft in UKG Ready, Dimensions and Pro.

What does Illinois BIPA require before you use face ID?

The Illinois Biometric Information Privacy Act (740 ILCS 14) is the most demanding biometric statute employers deal with, and it applies to scans of face geometry. The statute text published by the Illinois General Assembly sets out these duties for private entities in Section 15:

  • Public written policy (15(a)): a publicly available retention schedule and destruction guidelines. Biometric data must be destroyed when the initial purpose for collecting it has been satisfied or within 3 years of the individual's last interaction with the entity, whichever occurs first.
  • Notice and release before collection (15(b)): inform the person in writing that the data is being collected or stored, state the specific purpose and length of term in writing, and receive a written release.
  • No profiting (15(c)): the entity may not sell, lease, trade or otherwise profit from the data.
  • Limited disclosure (15(d)): disclosure only with consent or under the narrow exceptions the statute lists, such as a legal requirement or a valid warrant or subpoena.
  • Reasonable security (15(e)): protect the data using the reasonable standard of care in your industry, and at least as carefully as your other confidential information.

Section 20 gives aggrieved persons a right of action with liquidated damages of $1,000 for negligent violations and $5,000 for intentional or reckless ones, or actual damages if greater. Public Act 103-769, effective August 2, 2024, amended the Act so that repeatedly collecting the same person's biometric data by the same method counts as a single violation, and it added electronic signatures to the definition of a written release. That narrows exposure but does not remove it: a missing consent is still a violation. Our analysis of the BIPA ruling every HR leader should read covers the litigation background.

Illinois is not the only jurisdiction with biometric rules, and city ordinances and other state laws can apply too. Have counsel review your policy for every state where you operate. This article is practical guidance, not legal advice.

How do you build a compliant face ID time clock program?

Step 1: Write the policy first

Publish a biometric retention and destruction policy that names the purpose (timekeeping and identity verification), the retention period, the destruction trigger at separation, and who can access the data. Post it where employees and applicants can find it, such as your careers site or employee handbook portal.

Step 2: Build consent into enrollment

  • Show the written notice and purpose on the device or on paper before the camera turns on.
  • Capture a signed release, electronically or on paper, and store it with the employee record.
  • Record the date of consent so you can prove it preceded the first scan.

Step 3: Offer a fallback

Give employees who decline biometrics a non-biometric option such as a badge, QR code or PIN, combined with geofencing or supervisor verification. A fallback keeps the program voluntary in practice and avoids a stalled rollout when a few people object.

Step 4: Wire destruction into offboarding

Add a step to the termination checklist that deletes the face template and logs the deletion. Ask your vendor to show you how that deletion works and whether it reaches backups.

Step 5: Scope geofences narrowly

Collect location only at the moment of the punch, draw the fence around the work site rather than a whole town, and say so in the policy. Employees accept location checks far more readily when they know the app is not tracking them all day.

What should you ask vendors about biometric data?

  • Do you store a face image, a mathematical template or both, and where?
  • Is biometric data ever shared with or processed by third parties, and under what contract terms?
  • Can we configure consent screens and capture the signed release in your app?
  • How do we delete one employee's template, and how is deletion logged?
  • Can each site use a different punch method, including a non-biometric fallback?
  • How does geofencing behave when GPS is weak indoors, and what does the supervisor see when a punch falls outside the fence?

Frequently Asked Questions

Is facial recognition legal for employee time clocks?

Generally yes, but some states regulate how biometric data is collected, stored and destroyed. In Illinois, BIPA requires a public retention policy, written notice of the purpose and term, and a written release before collection. Review the rules in every state where you operate and get legal review of your consent forms before enrollment begins.

Does geofencing count as tracking employees?

It depends on how it is configured. A geofence that checks location only at the moment of a punch is far less intrusive than continuous tracking. Limit collection to punch events, draw fences tightly around work sites, explain the purpose in writing, and check whether state or local privacy laws impose additional notice requirements.

What should we do if an employee refuses to enroll their face?

Offer a documented alternative such as a badge, QR code or PIN paired with geofencing or supervisor confirmation. A fallback keeps the program workable, reduces friction, and fits privacy laws that require informed consent. Track the fallback group's exceptions separately so you can see whether the alternative method is being misused.

How long can we keep employee face templates?

Under Illinois BIPA, biometric data must be destroyed when the initial purpose is satisfied or within 3 years of the person's last interaction with the employer, whichever comes first. For timekeeping, the purpose usually ends at separation, so build deletion into offboarding rather than waiting for the outer limit.

Next steps to stop buddy punching

  1. Pull a month of punch data and flag patterns that suggest shared credentials, such as consecutive punches seconds apart for people who arrive separately.
  2. Draft your biometric retention policy and consent language, and send them to counsel before you choose a vendor.
  3. Decide per site whether you need face ID, geofencing or both, using the comparison table above.
  4. Run a pilot that includes enrollment, a declined consent and an offboarding deletion, so you test the whole lifecycle.

For related wage and hour rules, browse our payroll compliance guides. To see how face ID, geofencing and fallback punch methods are configured in practice, review the CloudApper AI TimeClock product page.

Last reviewed: October 2026.

Sources

Comments

Popular Posts

Why Workday Onboarding Breaks Down for Frontline Employees

How to Improve the Customer Experience (CX)

Infor HCM Software Engineer Jobs: Salary Factors and Skills

UKG Union Contract and Overtime Rules for Multi-Site Food Plants

How Do I Log In and Sign In to Workday HCM

How to Search in Workday: Find Reqs, Reports, People and Tasks

New Apple Watch Health Features Will Be Available This Year, but Blood Pressure and Blood Sugar Sensors Will Not Be Available Until Next Year

The Future of Employee Healthcare Key Concerns and Strategies for 2024

How Digital Marketing Helps Your Business Grow: A Practical Plan

ERP Solution Guide: How to Choose the Best ERP for You