Trust Center
How CLVR Benefits hosts, encrypts, governs, and shares the data you put in our hands: with the receipts that prove it.
- Data residency
- EU / EEA only
- Azure & AWS EU regions. No customer data leaves the bloc.
- Encryption at rest
- AES-256
- Azure storage encryption with platform-managed keys.
- Encryption in transit
- TLS 1.2+
- HTTPS enforced at the edge; the database is reachable only from the application over a private network.
- Staff authentication
- SSO only
- No password path to the back office; our identity provider's policies apply to every staff sign-in.
- Incident notification
- 72 hours
- Documented breach process; reviewed after significant changes.
- Compliance posture
- GDPR aligned
- Vendors hold ISO 27001 & SOC 2 Type II. Records on request.
Authentication and Security
How we make sure the right people, and only the right people, get in.
Data Hosting and Location
Where your data lives, and the certifications underneath it.
Data at Rest
How customer data is protected once it has landed in our systems.
Data in Transit
How traffic between you, our app, and our database stays sealed.
Data Governance
The paper trail, the retention rules, and the contracts behind the controls.
Data Subject Rights
Your rights under GDPR, and how to exercise them with us.
Sub-processors
The vendors we share data with to operate the service, and what each one is used for. This list is updated here, and customers are notified at least 30 days before a new sub-processor goes live.
Cloud storage for uploaded files and encrypted database backups, hosted in EU regions.
Hosting infrastructure and the identity provider used for organisational sign-in (OAuth via Entra ID).
Payroll integration for companies that use Kleer as their payroll system. Employee records and salary data are exchanged so benefit choices are reflected in payroll. Only active for companies that connect the integration.
HR system sync. For companies that connect Twine, employee records are imported to keep the platform in sync with their HR system. Only active for companies that connect the integration.
Optional AI receipt scanning, expense auto-approval and the CLVR Assistant, which answers employees' questions from their company's uploaded policy documents. Only receipt images, category names, those documents and the questions asked are sent. Data is not used to train models.
Product analytics used to understand and improve how the platform is used.
Marketing CRM only. Holds leads captured on our website (form submissions, demo requests). No customer, employee, or payroll data is ever sent to HubSpot.
Sales CRM only. Holds marketing leads captured on our website (form submissions, demo requests). No customer, employee, or payroll data is ever sent to Close.
AI and Automation
Where AI touches your data, and the guardrails around each surface.
Optional, and off until a company turns it on. Three switches, each off by default:
- the assistant itself, which answers from the documents HR has uploaded and cites the document and page
- whether it may read the asking employee's own benefit data
- whether it may ask to see the page the employee is on
Only what those switches allow reaches Claude (Anthropic): the question and the documents, that employee's own figures and any receipt they attach, and a page snapshot sent once after they press Allow. An employee's assistant sees their own data and nobody else's; an HR user's also answers about their own company, from the records the HR pages already show them.
Conversations belong to the employee:
- The employer sees only the questions the documents could not answer, grouped by wording and without names, and never the text, not even in the export at the end of a contract.
- CLVR staff may read a conversation only to check the answers and improve the assistant, and every read is logged.
- Nothing is used to train models, and conversations are deleted 90 days after the last message.
Product Security
How the code that runs your benefits gets built and shipped.
Security Operations
Day-to-day operations: who can do what, what we log, and what happens when something breaks.
Availability and Support
Numbers we can stand behind, measured externally, not a promise on paper.