InnerWeb
Skip to main content

DPIA for biometric readers: best practices of a data protection officer

Article 35 GDPR requires a data protection impact assessment before starting high-risk processing, and employee biometrics falls into that category. A well-made DPIA is prepared before the readers are bought, because its result can change the specification. Below are practices that help the DPO write a document that is useful, not merely formal.

6
blocks of the DPIA document described on the page
Source: Article 35 GDPR

Why the DPIA is done before purchase

Article 35 GDPR requires an impact assessment before starting processing that is likely to result in a high risk to the rights of individuals, including large-scale processing of special categories of data. Biometric data used for unique identification is such a category.

If the DPIA is prepared after the purchase, its result becomes the justification for a decision already taken. If it is prepared before, it can change the scope, the location of templates, or even lead to the conclusion that biometrics is not needed.

What to describe: six blocks of the document

The document should answer the questions an auditor or supervisory authority will ask. Below are the blocks that organise the DPO's work.

Description of the processing and its purpose

Specify the zones, the number of people, the type of reader, the place where the template is stored and the retention period. State the purpose as access control to specific rooms, not generally as security.

Necessity and proportionality

An employer who wants to apply biometrics to employees must demonstrate that the solution is necessary for the access control purpose. Describe the alternatives considered, such as an encrypted card, QR code and PIN, and the reason they were rejected for a given zone.

The data minimisation principle in Article 5(1)(c) GDPR requires data to be limited to what is necessary. If an alternative achieves the purpose, biometrics does not pass this test.

Legal basis and consent

Indicate the exception in Article 9(2) GDPR and the link with Article 22(1b) of the Labour Code. If you rely on consent, record how voluntariness and a genuine alternative are ensured, because the imbalance of the parties in an employment relationship raises doubts.

Risks for individuals

The most important risk is irreversibility: a body feature cannot be changed after a leak. Add secondary risks, such as using the template for other purposes, discrimination through wrong rejections and the lack of a genuine alternative.

Technical and organisational measures

Articles 25 and 32 GDPR require data protection by design and measures appropriate to the risk. Describe encryption, network segmentation, control of administrator access, an access log and the procedure for deleting templates.

Conclusion and review

Record whether the residual risk is acceptable, who approved the decision and when the document will be updated. A DPIA is not a one-off, because a change in the number of people, zones or supplier changes the assessment.

Example time needed to prepare a DPIA before purchase

Example time needed to prepare a DPIA before purchaseHorizontal bar chart: 4 hours for the description, 8 for necessity, 8 for risks and measures and 3 for the conclusion.02468hoursDescription of processingDescription of processing: 4 hours4Necessity and alternativesNecessity and alternatives: 8 hours8Risks and measuresRisks and measures: 8 hours8Conclusion and approvalConclusion and approval: 3 hours3
Source: Example calculation: illustrative assumptions of the DPO's work time, to be replaced with the organisation's data.

Typical mistakes in a biometric DPIA

The most common mistake is a description without alternatives. The second is omitting backups and external services where the template may end up. The third is the lack of a decision on what happens to templates after an employee leaves.

  • no comparison with an encrypted card and QR code
  • omitting the location of templates in backups
  • a general wording of the purpose instead of naming the zones
  • no review date for the document

InnerWeb's role in the documentation

InnerWeb is a software producer and integrates with the plant's existing KD system. Biometric templates do not reach InnerWeb, because an access event can consist of a person identifier and a timestamp. In the DPIA it is worth stating this as an element limiting the number of systems that process special category data.

Each client has an isolated instance with its own database, in Docker containers, also on the client's server. This architectural fact can be described in the section on technical measures as a limit on the places where personal data is stored.

Checklist

Video

Frequently asked questions

Is a DPIA mandatory for employee biometrics?

Article 35 GDPR requires it for high-risk processing, including large-scale processing of special categories of data. For employee biometrics it is in practice always carried out.

Who signs the DPIA?

The controller bears responsibility for the processing, while the DPO advises and monitors. Approving the decision belongs to the plant management.

Does changing the reader supplier require updating the DPIA?

Yes, because the place of template storage and the protective measures change. The document must be reviewed and updated.

Sources

Let us include InnerWeb in the architecture description

We will prepare a short description of the access event flow from your KD system to InnerWeb, which you can attach to your DPIA.

Let's talk