Organisation and account records
Workspace name, account email, role and authentication/session records handled by the managed authentication service.
Data processing
This page is the procurement-facing summary of the data processing agreement. The clauses that depend on the contracting entity, hosting region, retention schedule and notification window are listed as outstanding at the bottom rather than filled with plausible-looking values.
Draft for pilot review
Draft for pilot review. This document describes how the product works today and is not a signed agreement. The final terms, data processing agreement and company details are provided and signed during onboarding.
Last revised September 2026
| Processing | Controller | Processor | Note |
|---|---|---|---|
| Supplier and site records, cases, evidence metadata, remediation actions | Customer | Libera | The customer decides which suppliers and sites to enter and why. |
| Workspace user accounts and roles | Customer | Libera | The customer invites users and assigns roles. |
| Worker reports submitted through the confidential channel | Customer | Libera | Reports are scoped to the customer's workspace. The design deliberately avoids collecting worker identity data, and the customer receives aggregated indicator counts rather than individual narratives. |
| Website enquiry and pilot request data | Libera | — | Libera decides the purpose: responding to the enquiry. |
The subject matter is the customer’s use of Libera for supply-chain screening, confidential worker signals, human review, case documentation and remediation follow-up. Duration follows the service agreement plus the agreed return/deletion period. Frequency and scope depend on the selected pilot or subscription.
Workspace name, account email, role and authentication/session records handled by the managed authentication service.
Names, country, sector, workforce and recruitment context entered or imported by the customer.
Case status, timelines, evidence titles/sources/references and investigation notes. The case layer does not copy worker narratives.
Actions, owners, due dates, completion state and verification notes.
Material actions, actor details, timestamps, score changes and neutral descriptions without worker message content.
Selected concerns, optional free text, language, time, linked workplace/site or supplier and optional image evidence.
Data subjects may include customer workspace users, supplier or site contacts entered by the customer, and workers using the confidential reporting channel. Precise categories and any special-category data handling must be completed in Annex I before execution.
Supabase
Managed Postgres database, authentication and data API for organisation accounts, supplier records and worker reports.
Confirmed per deployment during onboarding — not stated here without verification.
Cloudflare
Application hosting, content delivery and execution of server functions for the website and console.
Confirmed per deployment during onboarding — not stated here without verification.
Resend
Transactional email delivery for pilot and access requests submitted through the website forms.
Confirmed per deployment during onboarding — not stated here without verification.
A workspace owner can delete supplier records from the console. Full-workspace deletion is handled manually on written request. Return/export, linked-record scope, backups, worker-report treatment and timing must be fixed in the signed DPA.
The executed DPA must define customer contacts, available information and notification timing. Cooperation with regulatory obligations and data-subject requests is subject to applicable law, the agreed scope and legal assessment; this draft promises no hour count.
Libera processes customer data only to provide the scoped supplier screening, worker reporting, case, remediation and documentation services, on the customer's documented instructions, except where applicable law requires otherwise.
Access is limited by assigned product roles and operational need. Binding personnel confidentiality terms, access-review procedure and authorised operational roles must be confirmed in the executed agreement.
Libera will provide reasonable product and record assistance so the customer can assess requests. Identity-minimised worker reports may be difficult to match to a requester because the report has no identity field; this limitation must be handled transparently.
The parties will define contacts, information flow and a notification window in the executed DPA. Notification and regulatory duties remain subject to applicable law and legal assessment; this template promises no fixed hour count.
Supplier deletion exists in the console; full-workspace handling is manual on written request. Return/export, deletion scope, timing, backups, legal holds and worker-report treatment must be agreed. No automated retention schedule exists today.
Libera can provide current owner-authored security information, named infrastructure providers and relevant product records or questionnaire responses. This does not amount to a certification, independent audit, penetration test or unrestricted infrastructure inspection right.
The executed DPA must list approved providers and set notice and objection terms for changes. Service regions and transfer arrangements remain to be completed; no EU-only hosting or implemented SCC mechanism is claimed here.
Any restricted transfer must use the lawful mechanism selected after the actual hosting and processing locations are confirmed. The applicable mechanism and supplementary measures are annex placeholders, not current claims.
Outstanding before signature
Company details
Libera Europe is the operating brand of the platform. The verified legal entity details below are not published yet. Rather than showing an unverified value, each outstanding item is marked — procurement receives the completed set before any contract is signed.