Worker reporting privacy notice
This plain-language draft explains the reporting channel to workers. The customer must complete the controller, contact, legal-basis, retention and local-rights details before putting it into use.
Free text or workplace context could still identify someone. Do not include names or details you do not want to share.
To receive concerns, identify repeated or serious patterns, prioritise human review, document follow-up and support the customer’s supply-chain due-diligence process. A report is a risk signal, not proof or an accusation.
Grouped counts by concern, supplier or site and resulting priority changes. It does not receive worker free text or evidence references through the current customer access model.
The reporting service stores the report to operate the channel. Any authorised operational access and purpose must be defined in the executed customer agreement and access procedure.
They process service data and may create limited technical security logs under their own service arrangements. This is why Libera does not promise perfect anonymity.
There is no configurable automatic retention schedule in the product today. The customer and Libera must agree a schedule and deletion procedure before production use. Supplier self-deletion and manual workspace deletion do not establish a worker-report retention period.
Read the retention template →Controller: To be completed before execution. Privacy contact and local supervisory-authority details: To be completed before execution. A request may be difficult to match to a report when the channel holds no identity field; that design limitation must be explained, not used to dismiss a valid request.
The channel is designed to minimise identifying data. To protect it against flooding and misuse, the network address of a web submission is processed briefly and turned into a one-way code that changes every day. That code is kept in short-lived counters (deleted within 48 hours) and is never stored with the report. Unusual timing or volume is flagged for human review as a “submission pattern anomaly”; reports are not discarded or treated as untrue because of it, since many workers may share the same site Wi-Fi. Workers are not fingerprinted or tracked across visits.
After sending, a worker can receive a random receipt code created on their own device. Libera stores only a one-way hash of it. The code shows a short, fixed status for the grouped concern — received, under review, action taken or closed — and never details, counts, identities or other people’s reports. Not every investigation can be fully disclosed while it is ongoing.
Workers can report a concern affecting themselves, another worker or a group. Share only what is needed, avoid names and personal details of others, and never put yourself in danger to gather evidence.
Uploaded files can contain faces, voices, name badges, locations or other identifying details. On the web form, image location and camera metadata are removed before upload, but the picture itself is unchanged. Unsent answers are kept only in the open browser tab and uploaded media is not stored on the device. Sending requires a connection; there is no offline submission.
Libera does not accept worker reports through WhatsApp. Libera Europe's WhatsApp number is for business and customer-service enquiries only. To raise a concern, use the QR code or the confidential web form — it does not involve WhatsApp or Meta.
Libera is not a crisis line and is not monitored around the clock. If someone is in immediate danger, use the appropriate local emergency or safeguarding route. The customer must establish and communicate suitable local routes; Libera does not claim an NGO or safeguarding response partner.
