InnerWeb
Skip to main content

Checklist: removing biometric templates after an employee leaves

After the employment contract ends, the biometric template is no longer needed for the purpose for which it was collected, and keeping it risks a GDPR breach. HR and IT should have a shared checklist that proves the template has disappeared from every place where it existed.

Why deleting a template requires a separate procedure

Article 5(1)(c) GDPR introduces the principle of data minimisation: data must be adequate, relevant and limited to what is necessary for the purposes of processing. After employment ends, the purpose of access control lapses, so the template should be deleted.

A biometric template is a mathematical representation of features, not a picture of a fingerprint, but it is still personal data. Unlike a password or a card, it cannot be changed after a leak, because a body feature is permanent. Leaving it on a server or in a backup is therefore a lasting risk.

Where the template may exist

The template is stored in the reader, on the access control system server or on the employee's card, and in addition it ends up in backups and export logs. Each of these places must be checked separately, because deletion from one does not remove it from the others.

Article 32 GDPR requires measures adequate to the risk, including encryption and access control. Backups should have a retention policy that allows templates to expire within a set period, because selective deletion from an archive is technically difficult.

The roles of HR, IT and security

HR reports the end of employment and indicates the date. IT deletes the template from the access control server and console and verifies the backups. Security collects the card and confirms the deactivation of the reader.

InnerWeb does not store templates: it receives check-in events from the access control system in the form of a person identifier and a timestamp. The REST API with JWT authentication and webhooks can pass information about account deactivation to other systems, while connectors to specific solutions require implementation work. The client's instance is isolated, with its own database, in Docker containers, including on the client's server, which limits the number of places with personal data.

Audit evidence

Proof of deletion is a record of the date, the person performing it, the places and the result of the check. For an audit there is no need to keep the template or a picture of it; a protocol is enough. Good practice is a quarterly review: comparing the list of active employees with the list of templates in the access control system.

Typical mistakes when deleting templates

The most common mistake is deleting the employee's account in the HR system without deleting the template in the access control system. The account disappears from the payroll list, but the fingerprint pattern stays on the server, because nobody linked both events into one procedure.

The second mistake is assuming that a card without a template is safe. If the template was stored on the card, returning it without destroying or reformatting it leaves the data with an employer who no longer has a purpose for processing it.

The third mistake is overlooking backups. Selective deletion from an archive is often difficult, so it is better to set the backup retention period in advance and describe it in the documentation.

Quarterly review procedure

Once a quarter IT exports the list of templates from the access control system, and HR provides the list of active employees. The difference is the set of templates to delete. The dated result goes into the protocol.

Such a review supports compliance with the minimisation principle and provides audit evidence, but it does not promise compliance with the law. It remains the controller's decision how long and on what basis data is kept.

Checklist

Video

Frequently asked questions

Can the template be kept in case the employee comes back?

Not without a new basis. The minimisation principle in Article 5(1)(c) GDPR requires limiting data to what is necessary, and after departure the purpose lapses.

What about backups?

Set a retention policy that makes templates expire within a defined period, and describe it in the documentation. Restoring from a backup must not reactivate the templates of former employees.

Does a QR scan or an access control event in InnerWeb contain a template?

No. The platform receives a person identifier and a timestamp.

Sources

Organising the lifecycle of access data?

We will show how deactivating an account in the platform connects with permits, attendance and time records without processing templates. Book a conversation.

Let's talk