InnerWeb
Skip to main content

Contractor employees and GDPR: FAQ

The Labour Code rules on monitoring do not cover subcontractor employees, because their employer is another company. Plant security may still locate people from external companies on the basis of Article 6(1)(f) GDPR, i.e. a legitimate interest. Below are answers on how to describe this interest, whom to inform and how to divide the roles of the administrators.

Art. 6(1)(f)
processing basis for employees of external companies
Source: card

Why is the Labour Code not enough for subcontractors?

The provisions of Article 22(2) and 22(3) of the Labour Code regulate the employer's relationship with its own employees: the internal act, written information, signage. An employee of an external company is not subject to the rules of the plant where they only perform work, so these provisions do not work for them. In addition, Article 22(1) § 1 limits the scope of data an employer may require from its own employees.

The lack of a statutory path is not a prohibition. It means the plant administrator must base processing on the GDPR, not on the monitoring rules, and document it as a separate processing activity in the register.

What is the legal basis for locating people from external companies?

A legal opinion points to Article 6(1)(f) GDPR (legitimate interest) read together with Articles 208 and 304 of the Labour Code. The first obliges the employer to cooperate and ensure safety for workers of different employers on the same premises; the second concerns duties towards people performing work on the plant premises on a basis other than an employment relationship with that plant. Together they justify the interest in protecting human life and health.

The interest must be written down and weighed. The balancing test has three steps: the purpose (e.g. finding a person after an alarm, an evacuation list), necessity (whether a milder measure, such as an attendance list, is sufficient) and the impact on the person (scope and duration of the data). The result is kept in the documentation and updated when the scope changes.

Scope of data: full location or narrowed (number of data categories)

Scope of data: full location or narrowed (number of data categories)Horizontal bar chart: full profile 6 data categories, risk zones 4, alarm and evacuation list 3.0246categoriesFull profile with historyacross the plantFull profile with history across the plant: 6 categories6Risk zones with authorizationperiodRisk zones with authorization period: 4 categories4Alarm and evacuation list onlyAlarm and evacuation list only: 3 categories3
Source: Sample calculation: categories are identifier, company, authorization period, area, passage history, position history; scope of 6, 4 or 3 depending on the variant

Who is the administrator: the plant or the external company?

Usually both parties are separate administrators of their own data. The plant decides on the purposes of location on its premises, while the external company remains the employer and the administrator of its own staff HR data. Where the plant and the subcontractor jointly determine purposes and means, they may be joint controllers, and then the arrangements from GDPR Article 26 are required.

It is worth settling this in the cooperation agreement or in an annex on security. Each InnerWeb client has an isolated instance with its own database and mail, in Docker containers, also on the client's server, which makes it easier to identify the administrator, the place of processing and the scope of access.

How to minimize data about people from outside?

The simplest way is not to register more than the purpose requires. The QR badge of an employee carries a random token; revoking it issues a new one, and the badge history is kept. For a person from an external company, an identifier, the company name, the period of authorization and the area they may enter are enough.

Location does not have to be permanent. Options for narrowing include enabling it only in high-risk zones, only for the duration of the work permit, or only for alarms. The narrower the scope, the easier it is to defend the balancing test and the retention period.

  • An identifier, company name and authorization period instead of a full profile of the person.
  • Location in risk zones, not across the whole plant.
  • A shorter retention period than for the company's own staff.
  • Badge revoked immediately after the work is finished.

How to inform people from external companies?

The information obligation under GDPR Article 13 covers the identity of the administrator, the purposes and legal basis, the retention period and the rights of the person, and for the basis under point f also the indication of the administrator's interest. The information is provided when the badge is issued or at registration, not only in the contract with the subcontractor, which the person may never have seen.

A good practice is a short version at the entrance (a QR code linking to the full information) and signage in the area. The plant keeps proof of delivery as an entry in the registration system.

Checklist

Video

Frequently asked questions

Is the consent of a subcontractor's employee required?

Consent is not the basis here. In the relationship with the plant consent is rarely voluntary; the basis is a legitimate interest described and weighed by the administrator.

Do the plant's trade unions have a say towards subcontractors?

The internal act concerns the plant's own staff. Rules for people from outside are best described in a separate document given to external companies.

Can an external company refuse location of its people?

The plant sets the conditions of entry to its premises. If location in a risk zone is a condition, refusing it means no access to that zone, not a GDPR violation.

How to end processing after the work is finished?

Revoke the badge, close the authorization and apply the retention period set in the documentation for this group.

Sources

Let's plan location for external companies

We will show how the QR badge, the work authorization and location in risk zones create consistent evidence for an audit. Book a demo with the InnerWeb team.

Let's talk