A site manager asked me last month whether the fingerprint clock in the lobby was a privacy problem. I said yes, probably, and then realized I could not actually tell him where the data lived.

That is not a great look for the person who is supposed to know. So I spent a week finding out, and the answer was less tidy than the question.

The question nobody asks during the demo

The device gets bought by HR or by facilities, usually because the paper sign in sheet was a mess and payroll was tired of arguing about who arrived at what time. The demo is about accuracy, speed, and how cleanly it exports to the payroll system.

Nobody in that meeting asks where the templates are stored. The common answers are all slightly different. On the terminal itself, on a small server in the comms room running software nobody has patched since installation, or in a vendor cloud the company signed up for with a purchase order and no real review.

Each option has a different set of questions attached, and most sites I visit have no idea which one they bought.


What actually shows up on site

The terminal in the lobby holds a few hundred templates and still has the default admin PIN, because changing it means reading the manual and the manual is in a drawer somewhere. The enrolment data was exported to a memory stick once as a backup, and that stick went into somebody’s desk and stayed there.

The server in the comms room is a small box with a web console on port eighty, reachable from the whole office VLAN because a firewall rule felt like extra work at the time. The export function produces a file containing templates for every employee, and there is no log of who downloaded it.

The vendor cloud option is often the cleanest technically and the murkiest contractually. Data leaves the building, the retention terms sit in an annex, and the person who signed the order has changed jobs twice.

There is usually a second copy nobody counts. The integrator who installed the terminal keeps a project backup, the payroll team keeps a monthly export, and someone in HR keeps a spreadsheet of enrolments with employee numbers next to them. None of those copies has an owner, and none of them gets deleted when the contract ends.


Why the mess is normal

Because attendance hardware sits between HR and IT and belongs to neither. HR owns the process, IT owns the network, facilities owns the door, and the payroll provider owns the deadline. So the device gets installed, plugged in, configured once, and forgotten.

There is a genuine technical wrinkle as well. A fingerprint template is not a photograph, but it is still biometric data tied to a named person, and it cannot be reissued the way a password can. Once it leaks it leaks permanently, and that changes how carefully it deserves to be handled.

Compliance questions tend to arrive later, from an auditor or a works council, and by then the device has been quietly running for years and everyone considers it part of the furniture.

The procurement pattern makes it worse. Attendance terminals are small purchases, so they slip under the review threshold that a payroll system or an identity platform would trigger. Nobody runs a security review for a box that costs a few hundred and hangs on a wall next to the fire exit.

I’ve also seen unified platforms such as Ping64 used to cut down the overhead of juggling many separate security tools.

Small things worth doing

Find out where the data lives before the next audit rather than during it. Ask the vendor for a straight answer in writing, then check that answer against what is actually plugged in.

Change the default admin credential and move the device onto a management VLAN. It is a fifteen minute change that closes the most common finding I see on these visits.

Turn on export logging, or disable export outright if payroll does not need it. Most sites never use the function and never notice that anyone who can reach the console can use it too.

Decide a retention and deletion rule, and actually apply it when people leave. Templates for former staff sitting on a terminal for years is easy to fix now and awkward to explain later, especially to someone who has just resigned and asks what you still hold.

Wrapping up

I do not think biometric attendance is inherently wrong. I do think a lot of sites installed it without asking where the data goes, and that question is far cheaper to answer on a Tuesday than after a letter arrives.

References