You cannot reset a fingerprint. If a password leaks you change it; if a face template leaks, it belongs to that person for life. That is why POPIA treats biometric information as special personal information, and why an estate manager about to enrol hundreds of residents, or a factory putting in clocking terminals, should do some homework first. This page is not legal advice. It sets out the practical questions to settle, the things to demand from installers and software suppliers, and the honest risks to weigh, so your POPIA practitioner has less to fix later.
A sequence to follow before the first enrolment
- Write down why you need biometrics and why a card or PIN alone will not do.
- Identify the lawful basis with your adviser, such as consent, or a legal obligation like keeping records of time worked.
- Draft a plain notice: what is collected, why, who sees it, how long it is kept.
- Choose the alternative for people who refuse, usually a card or tag or a PIN.
- Confirm your information officer is registered with the Information Regulator.
- Only then book enrolment day with the installer.
Templates, encryption and who can export the database
Most readers store a template, not an image, and that is a real protection: a template cannot easily be turned back into a fingerprint. But some systems also keep enrolment photos or event snapshots, especially face terminals. Ask which, and switch off what you do not need.
Then look at the database. Templates should be encrypted at rest and in transit, administrator accounts should be named, not shared, and exporting users should need a senior login and leave a log entry. The installer's technician should not walk away with a copy on a laptop.
Questions to put to the installer and the software supplier
- Where exactly are templates stored: on the reader, a local server or a cloud service, and in which country?
- Is the data encrypted, and who holds the keys?
- Who at your company can see or export our users, and is that logged?
- How do we delete a leaver from every reader at once?
- What happens to our data if we cancel the cloud subscription?
- Will you sign an operator agreement that covers POPIA duties?
The honest risks, and what reduces each one
- A breach is permanent: keep templates only, encrypted, on as few systems as possible.
- Function creep: data collected for the door ends up used for disciplinary tracking. Stick to the stated purpose.
- Forgotten leavers: resigned staff and sold units stay enrolled for years. Delete them on the day they go, as part of maintenance.
- Pressure to consent: an employee or resident who feels they cannot say no has not really agreed. Make the alternative genuine.
What to put in your request
- Ask where templates are stored and encrypted
- Ask how leavers are deleted from all readers
- Ask for an operator agreement covering POPIA
- Ask what a cloud supplier does on cancellation
- Ask for sample notice and consent wording
Biometric Data and POPIA for homes, estates, offices, factories and schools
- Homes: a family fingerprint lock stores few templates, but the app account still needs care
- Estates, complexes and body corporates: residents get a notice and a card option before the body corporate enrols any faces
- Offices and practices: staff consent forms, named admins and leavers deleted on their last day
- Factories, warehouses and mines: clocking templates kept only for active workers, with records of time worked retained
- Shops, restaurants and filling stations: staff templates on the back door reader removed when each casual worker leaves
- Schools, colleges and creches: parents' written consent before any learner biometrics, and staff on a separate group
- Clinics, hospitals and pharmacies: dispensary templates encrypted and the event log reviewed with the records policy
- Farms, smallholdings and lodges: seasonal workers' templates deleted at the end of the harvest, not left for years
