What does the plant pass to the portal about contractor work?
The integration works in two directions, but work data flows in one mode only: read-only. The plant exposes the work history of a person to the portal, and the portal has no way to write anything into the plant's system through this channel. The history is built from real hot work permits and time records, not from declarations made by the contractor, so the professional profile of a worker is based on what actually happened on site.
Only work that was actually carried out counts toward risk exposure, meaning permits that were approved, opened, monitored and closed. Submitted but not accepted permits and rejected permits do not enter the history. For the DPO this distinction matters: the portal does not learn about attempts that the plant stopped, only about jobs that took place.
The plant does not sum working hours in the history it passes on. On a live installation 0.8% of time records lasted longer than a week, and almost all of them were closed automatically, so a sum of hours from such entries would be misleading. That is why the rule for limiting hours sits with the portal, which has a wider view of a person's work across many clients.
How does the portal find the right person, and is the phone number safe?
Searching the work history is based on the phone number stored in international format with the country code. The number is compared in full. A number without the plus sign is rejected rather than assumed to be Polish, because such a default assumption could assign the work history of one person to another person with a similar number from another country.
This is a practical safeguard against identity mix-ups: it is better for a query to return nothing than to return the data of the wrong person. In companies that employ foreign workers, where numbers from different countries often have similar lengths, this matters in practice.
Access to the history itself is protected by a machine token in the request header. The token is never accepted in the URL, because addresses end up in the access logs of servers and intermediaries. If the token is not set on the server side, the installation shares nothing: no integration enabled means no path to the data.
Time records on a live installation: share longer than a week
What happens to the QR badge issued at the plant?
Each QR badge issued at the plant is reported to the portal as the identity of a person, but the report does not contain the token itself. What is passed on is a hash of the badge token, from which the code shown at the gate cannot be reconstructed. Revocations of badges also carry no personal data: the portal only receives the information that a given hash has stopped being valid.
The report to the portal is deferred until after the database write and is verified just before sending. In practice this means that a portal outage or a rolled back transaction will not stop badges from being issued at the gate. A contractor's employee does not wait in a queue because an external service is temporarily not responding.
What does this mean for GDPR documentation?
In the record of processing activities it is enough to describe two streams: the work history provided on the portal's request, and the badge hashes and revocations. Neither contains full contact data or the access code itself, which makes it easier to justify the data minimisation principle under Article 5(1)(c) GDPR.
Who decides which permission data reaches the plant?
The contractor's employee decides this when submitting the access request in the portal. The request accepts data on permissions, trainings and medical examinations only when the relevant consent scope is ticked. Without consent there is no such data in the request: the plant operator does not receive it as a default add-on.
The data the applicant chooses to share is not confirmed automatically. Permissions from the request are created in the plant with a status pending verification, while trainings and examinations remain in the content of the request. The plant still checks the documents itself under its own admission procedure, and the portal is a convenient channel for delivering the data; it does not replace the decision.
From the employee's perspective this means separating two things: consent to share information, which depends on the employee, and the plant's decision to admit the person, which always belongs to the plant.
Can the worker see what is known about them, and access their own trainings?
The person interface for the portal shows the worker a list of their trainings at the plant with a status: to do, completed, expires within 30 days or less, and expired. Each training has a personal link, and together with the list the worker receives a QR pass and information on whether a health declaration is required today.
In this way the contractor sees the same data the plant holds about their admission, and can fill gaps before arriving instead of finding out at the gate. The 30-day window before expiry lets the company plan the renewal of a training before work is blocked.
Video
Frequently asked questions
Can the portal write anything into the plant's system through the work history endpoint?
No. This channel is read-only and protected by a machine token in the header. If the token on the server side is empty, the installation shares nothing.
Does the work history include permits that the plant rejected?
No. Only hot work permits that were approved, opened, monitored or closed count toward risk exposure. Submitted and rejected permits do not enter the history.
What if the employee does not tick the consent scope in the request?
The request goes through without these data. The operator sees the company and the person, but not permissions, trainings or examinations, so they verify them under their own procedure, for example on the basis of documents shown at registration.
Will a phone number without the country code be treated as Polish?
No. A number without the plus sign is rejected. This is a deliberate safeguard against assigning the work history to the wrong person.
Sources
Let's talk about contractor data at your plant
We will show in a demo which data goes to the portal and which stays at the plant, and prepare a description of the data flows for the record of processing activities.
Let's talk