Is a lost card a personal data incident?
A lost card decides nothing in itself. The assessment depends on what data the finder can read from it. A card that carries only an identifier with no descriptive content does not disclose personal data directly. A badge with a printed first name, surname and photo discloses more, so the assessment needs a different justification.
Regulation 2016/679 requires that a personal data breach be reported to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to the rights or freedoms of natural persons. The risk assessment is made by the data protection officer, not by the security desk officer or the system administrator. That is why every loss report should reach the DPO with a description of what the card and the badge contained.
What information about the loss should the DPO receive?
The DPO needs nine elements: who reported it, when it was reported, when the card may have been lost, the type of card, whether there was a badge with personal data, whether there was an active QR badge, whether and when the card was blocked, whether there were attempts to use it after the block, and who closed the case. Most of these fields are created automatically in the security and access control system, and HR only adds the circumstances.
What does the person who finds a card or badge see?
In the InnerWeb system the QR badge token is 64 hexadecimal characters, generated by a random generator and never from a counter, a person number or a date. No information about the owner can therefore be derived from the code, and the code is not a sequential number that could be guessed by changing the last digit.
The token is printed only on the label and does not appear in any response of the security panel interface. The panel returns only derived facts, for example whether the person has an active badge. As a result, a security officer browsing the personnel file does not see a code that could be copied or scanned on another device.
Will the finder see anything after scanning someone else's badge?
At the gate, an unknown code and a deactivated code produce the identical error response 404. The finder therefore cannot check whether the code belongs to anyone at all, or whether it has already been blocked. The same mechanism protects against guessing codes by trial.
Limits of the card holder account search
How does HR find the account of the person reporting the loss?
The account search for a card requires at least 3 characters, returns up to 13 results and does not reveal the card number. This limits the risk that someone with search rights browses the database of people by typing single letters. The result is sufficient to point to the correct account, but not to copy the card number.
What to do when the same person has two accounts?
When the same person has two active accounts, the system transfers the training result to the account holding the card, but never merges accounts on the basis of the surname alone. For HR this means that when a loss is reported, the account to which the card was assigned must be identified, not the first account with a matching surname. Merging on the surname alone would risk assigning the card to the wrong person.
What stays in the audit trail and who sees it?
The audit trail records who changed work permissions, the taxonomy of hazardous work, training records and automation rules, and when. For the lost card case this means that changes to the qualifications and authorisations of the person whose card was lost are reconstructible: the DPO can show who changed their permissions and when, after the report.
Deactivating a badge creates a new record instead of overwriting the old one, so the person's badge history stays in the system. This benefits the audit, but it means HR and the DPO must decide on the retention period for these records, which is covered on a separate page about the lost card report register.
How to combine the duty to inform with the loss procedure?
The employee reporting the loss should receive a short notice on what personal data the site processes in connection with the case: the report data, the record of card scans from the period before and after the loss, and the data on issuing the replacement card. The DPO prepares the template of this notice, and HR hands it over when the report is accepted. This gives the review of scans carried out by security after the report a clear basis and purpose.
- Purpose of the scan review: checking whether the card was not used by an unauthorised person.
- Scope: the period from the last confirmed use by the owner until the block.
- Recipients: security, IT, HR and the DPO, to the extent necessary for the case.
Video
Frequently asked questions
Can HR give the finder the details of the card owner?
No. The finder is only told where to return the card. The owner's details are disclosed only to persons authorised for the case, and the return is directed to security.
Does a card found after it was blocked go back into use?
No. After a block a new card is issued and the recovered one is destroyed. Reinstating the old card would raise the question of who had it in the meantime.
Is the record of scans from the period after the loss personal data?
Yes, if it can be linked to a specific person. That is why the scan review is carried out for a defined purpose and scope, and the result is kept in the case file.
Sources
Let us talk about data protection for cards
We will show how the security panel hides tokens and card numbers and what the audit trail looks like. Book a demo with the InnerWeb team.
Let's talk