InnerWeb
Skip to main content

Checklist: what to close before buying biometric readers

Ordering biometric readers is a decision that cannot be reversed without cost, because it involves data that does not stop being sensitive when the device is replaced. The checklist below organises the points that the purchasing department and the data protection officer should close before placing the order.

Why a list and not a conversation

Purchasing is guided by price and availability, the DPO by risk, IT by architecture, and HR by its relationship with the workforce. Without a shared list each department assumes that the points of the other departments are closed. The result is often a reader installed before the impact assessment is finished.

Law and the basis for processing

Biometric data is personal data resulting from specific processing of physical, physiological or behavioural characteristics of a person, which allows that person to be uniquely identified (Article 4(14) GDPR). Processing it for the purpose of unique identification is in principle prohibited (Article 9(1)), and the exceptions are listed in Article 9(2).

Article 22(1b) of the Polish Labour Code links the biometrics of employees with access control to particularly important information or to premises requiring special protection. Before buying, you must therefore identify which zones meet this condition.

Number of checklist points by area

Number of checklist points by areaHorizontal bar chart: 4 legal points, 3 technical points and 3 points on the alternative and evidence.01234pointsLaw and basisLaw and basis: 4 points4Technology and dataTechnology and data: 3 points3Alternative and evidenceAlternative and evidence: 3 points3
Source: Breakdown of the checklist structure

Technical and organisational purchasing points

Questions for the reader supplier concern where the template is stored (reader, server, card), encryption, deletion and export of data, and backups. Article 32 GDPR requires measures adequate to the risk, including encryption and access control, and Article 25 requires data protection by design.

It is also worth asking how the reader cooperates with the access control system and whether events can be passed on by webhook. InnerWeb does not produce or supply access control readers, so integration with the chosen system is a matter of the event specification: a person identifier and a timestamp.

Alternative and audit evidence

Employee consent raises doubts because of the imbalance between the parties, so before buying you must have a parallel path ready. For most areas of the plant a DESFire card or a QR code is sufficient. Biometrics is considered only for narrow zones of particular protection.

The audit evidence consists of: the necessity document, the DPIA, the information under Article 13 GDPR, the retention policy, the description of the alternative path, and a data processing agreement with the supplier if the supplier has access to the data.

Pitfalls that only surface after installation

The first pitfall is readers bought in advance for the whole plant, before the assessment shows that biometrics is needed in only one zone. Excess devices generate excess data, and in an inspection you must explain why a warehouse worker has a template in the system when a card would have been enough.

The second pitfall is the lack of a path for people who refuse. Employee consent raises doubts because of the imbalance between the parties, so on the day of launch some of the workforce will ask for a card. Without a ready pool of media, security improvises and employees wait at the gate.

The third pitfall is the lack of an event specification for external systems. If the reader sends only the recognition result to the access control system, while time records and the permit platform need a person identifier and a timestamp, the integration has to be added after the fact.

How to use the list in practice

Plan one meeting with purchasing, the DPO, IT, HR and security. Go through the list point by point, and for each item record the responsible person and the deadline. An item that nobody can close blocks the order.

Record the outcome of the meeting in the documentation of the purchasing project. In an internal audit or an inspection by the supervisory authority, this is evidence that the decision on biometrics was preceded by an assessment and did not result solely from the supplier's commercial offer.

If the plant already has an access control system, check whether the supplier can pass events on by webhook. InnerWeb integrates with the client's existing system and complements it, and the REST API with JWT and webhooks make this easier, provided the connector to the specific solution is built as part of the implementation work.

Checklist

Video

Frequently asked questions

Does the checklist replace the DPIA?

No. The checklist organises the points to be closed, while the DPIA is a separate document under Article 35 GDPR.

Who is responsible for closing the points?

The DPO for the law, IT for architecture and security, HR for communication, security for the entry process, and purchasing for the contract with the supplier.

Does InnerWeb need a template for its work?

No. The platform receives from the access control system an event with a person identifier and a timestamp.

Sources

Closing the list before the purchase?

We will help you check how events from your existing access control system feed attendance, permits and qualifications without templates. Book a conversation.

Let's talk