By Presentee Team · July 14, 2026 · 3 min read
Location verification answers where a check-in happened. It says nothing about who actually performed it. A geofenced check-in from the office parking lot is just as valid, technically, whether the employee's own phone did it or a coworker borrowed it for thirty seconds on the way in. Selfie verification is the control that closes that specific gap — it ties the check-in to a real, present face rather than just a device and a set of coordinates.
The meaningful distinction is between a photo taken at the moment of check-in through the app's own camera flow, versus a photo picked from the phone's gallery. The second option defeats the entire purpose — an employee takes one photo once, saves it, and 'verifies' every future check-in with the same static image regardless of whether they're actually there.
A correctly built check-in flow opens the device camera directly inside the app, captures the image in that moment, and uploads it immediately — there's no gallery picker step available in the flow at all, so there's no path to reusing an old photo even if someone wanted to.
This is where a lot of the legitimate hesitation about selfie verification comes from, and it's a fair concern — employees are being asked to hand over a photo of their face regularly, and that data needs to be handled carefully. A responsible implementation stores the image securely, restricts who can view it (typically a Company Admin reviewing attendance, not every user in the system), and has a defined retention period rather than keeping every check-in photo indefinitely.
This should be spelled out plainly in whatever privacy policy or security page a company shows its employees — not just as a compliance formality, but because employees who understand exactly how the photo is used and stored are the ones who don't push back on the requirement.
It's easy to assume selfie verification means automated facial recognition matching every check-in against a stored reference photo. That's one way to build it, but it's not the only useful version, and for many companies it's more infrastructure than the problem needs. A simpler, effective pattern is: the photo is captured and stored against the attendance record, and a supervisor can review it — either routinely for a sample of check-ins, or specifically when something about a record looks worth checking, like a dispute or an unusual pattern.
On its own, a selfie proves a face was present for the photo — it doesn't prove where, and a determined employee could in theory take it anywhere. That's exactly why it's meant to run alongside geofencing and device restriction rather than instead of them. Each control answers a different question, and an attendance record that passes all three at once is genuinely hard to fake without real, sustained effort — which is the actual goal, since no verification system needs to be unbreakable, only expensive enough to defeat that nobody bothers.
This should be a policy decision an admin controls per company, not a fixed rule — some teams require it for every check-in, others only for check-in and not check-out, and some make it optional for trusted roles. What matters is that whichever setting is chosen is applied consistently, not case by case.
Every attendance system will need corrections eventually. The question is whether yours handles them honestly — appended and auditable — or as a quiet backdoor around every check you just built.
A spreadsheet is a perfectly fine attendance system for a while. Here are the specific signs it's stopped being one, and what a growing team actually gains by switching.
Leave tracked in a group chat works for exactly as long as everyone remembers to check it. Here's what to put in place before that stops being true.
Set up your workspace now and add your team as you grow. No card, no sales call.