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.
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.
