How to use the list
The list does not replace a legal analysis. Its purpose is to make sure the most important questions are asked before the first codes are sent. Go through it with the DPO and HR in one meeting and record the answers in the pilot note. Each point has a comment, so it is clear where it comes from.
Data in the code and in the system
The first group of points concerns what the phone carries. The QR code contains the plant address with a random 256-bit token and no personal data. The first name, last name and company appear only on the server side, on the 'Is it you?' confirmation screen.
For the DPO it is important that the scan does not log the person in by itself: a human confirms whose account is opened. If the plant adds further data to the processing, it describes it separately in the register of processing activities.
Checklist points by group
Channels and privacy of contact
The second group concerns the sending channel. The code goes to an e-mail address and, if there is none, by SMS with a link to the phone number. Invitations can be sent to people without an e-mail address through their phone number or registration number. The plant must decide whether it uses a work contact or a private one, and record this in the documentation.
The message with the code is sent once per person and only after the required training has been passed, so the number of messages containing data is predictable. When a person has no channel at all, nothing is sent.
Alternative and revoking
The third group covers points on voluntariness. An employee who does not want to use a private phone should have a parallel route: a label with the code or a card. After a phone is lost, the plant issues a new code and the old one stops working, which limits the risk of entry by an unauthorised person.
For guests and contractors, registration at reception works well: the guest is created with only a first name, last name and phone number, and receives a printed label with the code in one action.
Evidence after the pilot
The fourth group concerns documents that will remain for the audit: the DPO note, the description of the data flow, the list of channels and the rules for the alternative. Attach to the note the findings of the test of employees' phones, because they show that the plant checked the devices before launch.
Commentary on the points most often skipped
The two points most often skipped are the decision on a work or private contact and the alternative for people without consent. The first causes the code to go to numbers that the plant did not plan to use. The second makes the pilot lose credibility when an employee feels pressured.
The third point is the role of the KD vendor. If the plant also uses the vendor's NFC mobile identifier, its processing is described separately, because InnerWeb is a software producer and accepts only tap events from the client's KD system. A joint DPO note should cover both data flows.
The fourth is the guest and the contractor. Their data differ from employee data: the first name, last name and phone number given at reception. Describe the scope of this data in a separate point, so that the DPO sees the full picture.
When to return to the list
The list should be repeated whenever the scope changes: a new group of people, a new sending channel, a new KD vendor, or an extension from guests to employees. After each change, update the DPO note and the review date.
A short review after the first quarter of the pilot also helps: how many people use the phone, how many use a label, and whether complaints about privacy have appeared. This review does not require new tools, only the event log and a conversation with the DPO.
Checklist
Video
Frequently asked questions
Does the list replace the analysis by the DPO?
No. The list organises the questions, and the legal assessment is carried out by the DPO together with the data controller.
Is the employee's consent required?
The legal basis is set by the controller with the DPO. Regardless of it, we recommend keeping an alternative for people who do not want to use a private phone.
Does InnerWeb collect the phone's location in access control?
Access control is based on scanning the code at the gate. The system does not need GPS for location, and the plant describes the scope of processing in the DPO note.
Sources
Let us go through the list with your DPO
We will prepare for your inspector a summary of data and channels, and show the flow of the code on an example plant.
Let's talk