InnerWeb
Skip to main content

Register of processing activities for employee location: implementation notes

The register of processing activities under Article 30 GDPR is the first document a controller reaches for. For employee location, one entry called 'security system' is not enough. Below are notes on how to split the activities, what to enter in the fields and which traps to avoid during the pilot.

5
recommended register entries for the location pilot
Source: example calculation

Rule: one purpose, one activity

The most common error in the register is putting everything into one entry. Processing purposes have different legal bases and different retention periods, so each is described separately. Article 30 GDPR requires a register of processing activities kept by the controller, and Article 13 requires information for data subjects that is consistent with that register.

For employee location during the pilot we recommend four entries: location of own employees, the SOS alarm and motionlessness detection, location of external contractor staff, and visitor registration and entries. A fifth entry concerns integration with the access control system, if card events feed the system.

Entry 1: location of own employees

Employee location is a different form of monitoring under Article 22(3) § 4 of the Labour Code, and under § 3 Article 22(2) §§ 6-10 applies to it accordingly. The basis in the register is therefore the provision of the Labour Code together with the internal act, not the employee's consent.

The entry covers: the purpose (work organisation and permits in the selected area), the categories of people (pilot hall employees), the categories of data (identifier, position in the zone, time), the recipients (roles in the plant), the retention period, security measures and the place of processing.

Retention period

The three-month limit from Article 22(2) § 3 does not apply directly to location, because Article 22(3) § 3 refers only to §§ 6-10. The controller sets the period in line with the minimisation principle, so the register contains a specific value and its justification. An entry 'until withdrawn' will not pass an inspection.

Register entries by legal basis

Register entries by legal basisChart: one entry based on Article 22(3) of the Labour Code, one on Article 207 § 2, two on Article 6(1)(f) GDPR (external contractor staff and visitors), one for access control integration.012number of entriesLabour Code art. 22(3) and22(2)Labour Code art. 22(3) and 22(2): 1 number of entries1Labour Code art. 207 § 2Labour Code art. 207 § 2: 1 number of entries1GDPR art. 6(1)(f)GDPR art. 6(1)(f): 2 number of entries2Access control integration(purpose from events)Access control integration (purpose from events): 1 number of entries1
Source: Example calculation: the recommended layout of five entries for the pilot, without statistical data

Entry 2: SOS alarm and motionlessness detection

The purpose 'security' is listed in Article 22(2) § 1 for video monitoring, not in Article 22(3) § 1. For this reason the SOS alarm and motionlessness detection are described as a separate purpose based on Article 207 § 2 of the Labour Code. Model acts for wearable devices contain a separate paragraph on the alarm function, which helps keep the register consistent with the act.

In the register this entry has its own data categories and its own retention period. Alarm event history is often kept longer than ordinary position data, and this must be justified by the need to analyse events, not by convenience.

Entries 3 and 4: external contractor staff and visitors

For employees of external companies the Labour Code provisions on monitoring do not apply. The basis is Article 6(1)(f) GDPR in conjunction with Articles 208 and 304 of the Labour Code, as a separate processing activity. In the register this is a separate entry with a different group of people and its own information.

Visitors have another entry: registration, a QR code in the invitation and a scan at the gate. If the plant enables the health declaration of a visitor at entry (a BRCGS requirement), it must be included in the register as an additional purpose. The function is switched off by default. Once enabled, a visitor without today's declaration does not enter and no entry is recorded. Health data requires special care, so its scope and retention period are assessed together with the inspector.

Entry 5: integration with the access control system

InnerWeb is an independent system that complements the client's existing systems: access control, time and attendance, HR and ERP. It receives card-badge events from the client's access control system and does not manufacture readers. The register must therefore state where the data comes from, who passes it on and for what purpose it is used in InnerWeb.

The division of purposes for card events is described in a separate page on data from the access control system and GDPR.

Pilot traps

The pilot is sometimes treated as a stage without documentation duties. This is an error: personal data is processed from the first day, so the register, the act and the information must exist before the pilot starts. Three traps recur most often.

  • The register is completed after the start, not before it.
  • The scope changes during the pilot without updating the register, the act and the information.
  • The register and the Article 13 information are inconsistent: different purposes, different retention periods.

Video

Frequently asked questions

How many entries does the register need for location?

We recommend separating the purposes: employee location, SOS alarm, external contractor staff, visitors and access control integration. The controller and the inspector finally decide the number.

Does the pilot require a register?

Yes. Personal data is processed from the first day, so the register under Article 30 GDPR, the internal act and the information must be ready before the pilot starts.

What retention period should be entered?

A specific one, resulting from the purpose. The three-month limit from Article 22(2) § 3 does not apply directly to location, but the minimisation principle requires the period to be justified.

Does the visitor health declaration have to be in the register?

If the function is enabled, yes, as an additional purpose with its own scope of data and retention period. The function is switched off by default.

Sources

Prepare the register before the pilot

Together with your data protection officer we will set five entries of the register and describe the data the system actually processes.

Let's talk