Why the division of roles must be settled before rollout
The controller decides on the purposes and means of processing, and the processor acts on its behalf. In a location system for employees the controller is the employer, because it sets the purpose, the scope of the area, the retention period and announces the internal act under Article 22(3) of the Labour Code in conjunction with Article 22(2) §§ 6-10. The software vendor does not decide who is located and why.
The question of the vendor's role depends on whether it has access to personal data at all. This depends on the architecture, not on commercial clauses, so the IT department should describe the architecture before the lawyer starts drafting the contract.
The architecture that simplifies the division of roles
Every InnerWeb client has an isolated instance with its own database and its own mail service in Docker containers, also on the client's server. For the division of roles this has concrete effects: one client's data does not mix with another's, the place of processing is known, and the scope of access can be identified.
When the instance runs on the client's server, the data physically remains in the client's environment. The vendor's access is limited to service activities that the client can control: timing, the method of connection and scope. This changes the character of the contract from a broad processing agreement to a contract for limited service access, which must be assessed case by case.
Importantly, InnerWeb is a software producer and integrates with the client's existing systems, such as 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 access control vendor is therefore a separate entity in the processing chain and has its own role.
Vendor access to personal data: shared cloud setup versus an instance at the client
- Shared setup, broad access
- Instance at the client, service access
Six recommendations for the plant director and IT
The recommendations below are organisational in nature. The legal assessment of roles in a specific implementation is carried out by the controller with the data protection officer and legal counsel.
1. Name the controller in one sentence in the act
In the internal location act and in the information under Article 13 GDPR, name the controller. Article 13 requires, among other things, the identity of the controller, the purposes, the legal basis, the retention period and information on rights. The wording must be consistent with the register of processing activities under Article 30.
2. Describe the architecture before the contract
The IT department prepares a one-page description: where the instance runs, what the database is, who has administrator accounts, and how service access works. The description is an annex to the contract and the basis for assessing roles.
3. Sign a contract under Article 28 if the vendor has access to data
If the vendor may gain access to personal data as part of the service, for example during maintenance, a contract meeting the requirements of Article 28 GDPR is needed. If there is no access, the role must be described separately and assessed with a lawyer.
4. Limit service access
Service access should be explicit, limited in time and recorded in a log. The data protection by design principle in Article 25 and the measures in Article 32 require that access follows from need, not from convenience.
5. Separate the roles in the access control chain
The access control system vendor, the integrator and InnerWeb have different tasks. Record them in the register: who collects badge events, who passes them on, who processes them further. Each link is entered in the register of processing activities with the appropriate role.
6. Set the incident reporting path
The processor, where it exists, informs the controller of a breach without undue delay. It is worth setting in advance who on the client's side receives the report and what it contains.
External contractor staff: a separate processing activity
For employees of external companies the Labour Code provisions on monitoring do not apply. The basis is Article 6(1)(f) GDPR (legitimate interest), in conjunction with Articles 208 and 304 of the Labour Code, as a separate processing activity. For the division of roles this means a separate entry appears in the register, and the relationship with the external company requires its own records on informing its employees.
Evidence worth keeping in the binder
The inspector will ask three things: who is the controller, who has access to the data, and on what basis. The answer should follow from documents, not from memory. The complete set is the internal act, the register of processing activities, the architecture description, the contracts and the log of service access.
A simple table of roles works well: party, role, scope of data, basis, place of processing. Update it with every change to an integration.
Video
Frequently asked questions
Who is the controller in a location system?
The employer, which sets the purposes, the scope and the retention period and announces the internal act. The software vendor does not decide who is located and why.
Is a processing agreement always needed?
A contract under Article 28 GDPR is needed when an entity processes data on behalf of the controller, including through access to it. With an instance on the client's server, whether and how the vendor has service access decides this. The controller assesses it with a lawyer.
Where is the data physically?
The instance runs in Docker containers with the client's own database, also on the client's server. The place of processing is therefore known and is entered in the register of processing activities.
Sources
Let's describe the architecture before the contract
We will prepare a one-page description of the instance, service access and integrations for your IT, to make the role assessment with a lawyer easier.
Let's talk