The fear most people bring to the table
Say "facial recognition" in a staff meeting and watch what happens. Someone mentions a movie. Someone mentions a government database. Someone jokes about being tracked. That reaction isn't irrational; it's just misplaced. Most people's mental image of facial recognition was built by dystopian films and news stories about mass surveillance, not by anything that actually resembles a workplace attendance tool. That gap between the fear and the reality is where this article lives. Facial recognition, as a category, covers everything from government surveillance networks to a phone unlocking when you glance at it. Lumping all of that together isn't fair to the technology, nor to the businesses trying to use a small, specific slice of it responsibly. The honest answer is: facial recognition isn't inherently invasive. What matters is which tool you pick, what it actually does to a face, and whether the people building it considered consent and privacy before they focused on features.How faceATT confirms a real person, not a photo
One of the quieter problems with basic face-based attendance systems is that they can be fooled. Hold up a photo of an employee, and a weak system might clock them in. That's not just a technical flaw; it's a fraud risk. faceATT uses liveliness detection to close that gap. In plain terms, liveliness detection checks that there's an actual living person in front of the camera at the moment of the scan, not a printed photo, not a video playback, not a static image pulled up on someone else's phone. It's the difference between "a face was shown to the camera" and "a real person was present and verified in real time." The important part for anyone nervous about this: liveliness detection is a verification step, not a recording step. It confirms presence and moves on. It isn't building a video archive of employees or storing footage of the check.What actually happens to a face scan
This is the part people usually get wrong, and it's worth being precise about it. When someone enrols on faceATT, the system doesn't keep a photo album of their face sitting in a database somewhere. It converts the face into a mathematical template, essentially a set of numbers that represents the geometry of that face. That template can't be reverse-engineered back into a photograph. There's no image to leak, because the image was never the thing being stored. On top of that template, some plans do capture and store a photo at each clock-in and clock-out; this is the point-in-time image that gives an employer auditable proof of attendance, and it's viewable by the employee themselves, not hidden from them. That's a deliberate design choice: transparency over secrecy. Nobody is scanning faces into a black box they can't see into. So the honest version of this point isn't "nothing is ever stored." It's: there's no reversible biometric image bank sitting behind the scenes, and any clocking images that are captured are visible to the person they belong to, not just to management.POPIA vs GDPR, and what South African businesses actually need to worry about
If you've read anything about facial recognition compliance, you've probably seen GDPR mentioned more than POPIA. That's understandable; GDPR gets more global press, but it's not the law that governs a South African business processing South African employees' data. POPIA (the Protection of Personal Information Act) classifies biometric data as "special personal information," which means it carries a higher standard of care than an email address or a job title. Under POPIA, two roles matter:- The employer is the responsible party. They onboard their own staff, they get consent directly from their employees, and they decide why the data is being processed and who inside the business can see it.
- faceATT is the operator. It processes attendance data because the employer instructed it to, not because it went out and collected consent on its own. It doesn't set the purpose, it executes on the employer's authority.
