Situation: consents collected, but no exit designed
This is a conceptual scenario based on a typical situation in a production plant. Fingerprint readers were installed at gates and in several zones. Employees signed consents to collect a fingerprint, and the HR department archived the forms.
The problem appears when the first employees submit a statement withdrawing consent. It turns out the access control system has no path for a person without a template: either they enter through security with a temporary card, or they cannot enter at all. Nobody anticipated that withdrawing consent is a right that must be handled on the day it is reported.
Problem: consent in an employment relationship and its withdrawal
One of the exceptions in Article 9(2) GDPR is the explicit consent of the person. Consent must be freely given, specific, informed and unambiguous (Article 4(11) GDPR). In an employment relationship doubts arise because of the imbalance between the parties, so it requires particular care and a genuine alternative.
A genuine alternative means that an employee who refuses or withdraws consent suffers no negative consequences and gets an equivalent way of entry. If withdrawal means a longer route, a queue or no access to the workstation, the consent is not voluntary in practice.
- a consent form without a described alternative does not meet the requirement of awareness
- withdrawing consent should be as easy as giving it
- an employee must not lose access to their workstation because they refuse
- after withdrawal the template must be deleted, not merely deactivated
Consent withdrawals per year at different rates, example
Solution: a withdrawal procedure in five steps
The plant should have the procedure ready before the first employee submits a statement. Below is a scheme that the DPO and HR can adapt to their organisation.
Steps from the statement to issuing the card
The statement reaches HR, which the same day passes it to the DPO and the access control administrator. The administrator removes the template from the devices and the system database, and HR issues a proximity card or QR code as an equivalent way of entry.
Confirmation of deletion goes to the file, because Article 5 GDPR and the accountability principle require the plant to be able to demonstrate what it did with the data. The employee receives information that their fingerprint is no longer processed from that moment.
- accepting the statement and recording the date of receipt
- deleting the template from readers, controllers and the KD server
- issuing an encrypted card or QR code the same day
- confirming deletion signed by the administrator
- an entry in the record of processing activities and an update of the DPIA
InnerWeb's role: an event without a template
InnerWeb is a software producer and does not manufacture biometric readers. It integrates with the plant's existing access control system and receives access events via webhook. An event may contain only a person identifier and a timestamp, so biometric templates never reach InnerWeb.
As a result, withdrawing consent changes nothing on the side of permits, qualifications and attendance. A person who moved from a fingerprint to a card is the same person in InnerWeb with the same trainings. Only the identification method in the KD system changes.
Effect: an example calculation of the withdrawal workload
Assuming 400 employees covered by biometrics and a 15% withdrawal rate in the first year, 60 people need to be handled. At 20 minutes of HR and administrator work per withdrawal, this gives about 20 hours of work in a year. These are illustrative assumptions, not a measured result.
The cost of handling is low compared with the risk of having no procedure. An employee denied access after withdrawing consent is a ready complaint to the data protection authority.
Conclusions for the DPO and HR
Collecting consents only makes sense if a working alternative exists in parallel. The simplest test before launch: what happens tomorrow if half the workforce withdraws consent. If the answer is chaos, the system is not ready.
For most areas of the plant a card or QR code is enough, so it is reasonable to limit biometrics to narrow zones where its necessity has been justified. The fewer people covered by a fingerprint, the fewer withdrawals to handle.
Workload of the consent withdrawal procedure, example calculation
| Parameter | Value |
|---|---|
| Employees covered by biometrics | 400 people |
| Withdrawal rate in the first year | 15 % |
| Time to handle one withdrawal | 20 minutes |
Result: 60 withdrawals and about 20 hours of work per year.
Note: Example calculation based on illustrative assumptions, to be replaced with the plant's own data.
Video
Frequently asked questions
Can an employee withdraw consent at any time?
Yes, withdrawal should be possible at any moment and be as easy as giving consent. The plant must then stop processing based on that consent.
Is deactivating the account in the KD system enough?
No. The template must be deleted from the devices and the database, and the deletion must be documented.
Does InnerWeb delete templates from readers?
No, because InnerWeb does not store them. Templates are in the plant's KD system, and the administrator deletes them there.
Sources
Let us plan an alternative to biometrics
Let us talk about integrating access events with InnerWeb so that changing the way of entry does not affect permits and qualifications.
Let's talk