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+
- sslmode=verify-full for the app-to-db link; HTTPS enforced at the edge.
- Staff authentication
- MFA enforced
- No staff access to production without a second factor.
- 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.

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).
Optional AI receipt scanning and expense auto-approval. Only receipt images and category names 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.
AI and Automation
Where AI touches your data, and the guardrails around each surface.
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.
