InnerWeb
Skip to main content

GDPR checklist for guest registration

Guest registration at a kiosk with a health declaration required by BRCGS is processing of data that must be described as precisely as the location of employees. The declaration concerns health, so plant security must check the scope of data, the basis, the information for the guest and the retention period. Below is a checklist with comments for the practitioner.

disabled by default
guest health declaration, enabled on request
Source: card
random token
QR badge; revoking issues a new one
Source: card

Scope of data: only what is needed to enter

The minimization principle of GDPR Article 5(1)(c) means that registration collects only the data needed to admit a guest: first and last name or identifier, company, host, purpose and time of the visit. For people who enter the plant on a basis other than an employment relationship, the monitoring rules of the Labour Code do not apply, so the basis is Article 6(1)(f) GDPR read together with Articles 208 and 304 of the Labour Code.

The requirement of Article 22(1) § 1 of the Labour Code limits the scope of data an employer may demand from its own employees. GDPR applies to guests, but the practical conclusion is similar: the list of fields in the kiosk should be short and justified.

  • Identification of the guest and company: needed for the list of persons present and for evacuation.
  • Host and purpose of the visit: needed for responsibility for the guest.
  • Time of entry and exit: needed for the evacuation list.
  • Additional fields: only with a justification in the documentation.

Health declaration: optional function and special category data

The guest health declaration at entry (a BRCGS requirement) is a function that is disabled by default. Once enabled, a guest without today's declaration does not enter and no entry is recorded. This matters for data protection: the plant does not collect entries of people who did not meet the condition, so it collects less data.

The declaration contains information about the state of health, which is a special category of data, so it requires a basis under Article 9 GDPR in addition to the basis under Article 6. The choice of basis belongs to the administrator and its adviser. Record it in the register of processing activities and in the DPIA if the scope is broad. Make sure the content of the declaration is limited to the questions required by the standard.

Checklist points by area

Checklist points by areaHorizontal bar chart: three checklist points each for scope of data, health declaration, information and badge, retention and access.0123pointsScope of dataScope of data: 3 points3Health declarationHealth declaration: 3 points3Information and badgeInformation and badge: 3 points3Retention and accessRetention and access: 3 points3
Source: Sample calculation: number of points in the areas of this checklist

Information for the guest and marking

Article 13 GDPR requires giving the guest the identity of the administrator, the purposes and legal basis, the retention period and information about rights. In practice the information is a short version on the kiosk screen with a QR code linking to the full document, preferably in the guest's language. For foreign guests this means language versions.

The QR badge issued for the duration of the visit has a random token; revoking it issues a new one, and the history of badges is kept. As a result, after the visit the badge stops working, and the plant has proof of when and to whom it was issued.

Retention period and access

The administrator sets the retention period for guest data in line with the storage limitation principle of GDPR Article 5(1)(e). The health declaration is usually kept for a shorter time than the register of entries, and the periods are recorded in the register of processing activities under Article 30. Plant security checks whether the system configuration matches these records.

Access to guest data is given only to persons named by function: security, reception, and hosts in respect of their own guests. Changes made by a person, such as a correction of an entry, are recorded in the audit log together with the author and the time. This proves accountability.

How to use the checklist in plant security

Go through the list when the kiosk is launched, after every change to the registration fields and once a quarter. Record the date of the check and the person for each item. If the data protection officer or a BRCGS auditor asks questions, you have ready proof that guest registration has a described purpose, scope, basis and retention period.

Checklist

Video

Frequently asked questions

Must a guest consent to registration?

The basis for registration is usually the legitimate interest of the plant, not consent. For the health declaration, the basis under Article 9 GDPR is assessed by the administrator.

What happens when a guest does not submit a declaration?

With the function enabled, a guest without today's declaration does not enter and the entry is not recorded.

Do the same rules apply to employees of external companies?

The basis is similar, Article 6(1)(f) GDPR, but the scope and retention periods are worth describing separately in the register of processing activities.

Who is responsible for the guest on plant premises?

The host indicated in the registration. The host's function is recorded in the documentation, not their name.

Sources

Let's check guest registration at your plant

We will show the kiosk, the invitation with a QR code and the configuration of the health declaration, as well as the retention period settings. Book a demo with the InnerWeb team.

Let's talk