🔒 Authentication and Security
| Control | Status |
|---|---|
Multi-Factor Authentication (MFA)Enabled for all admin and staff accounts. | |
Password policiesAligned with the standards of the relevant provider (e.g., Microsoft for Azure accounts). | |
Certificate and key rotationAll certificates and keys are rotated regularly, with many handled automatically by cloud providers. Manual credentials updated every 90 days. | |
BankID integrationStronger user authentication and identity verification in user application. | Planned |
🌍 Data Hosting and Location
| Control | Status |
|---|---|
Primary infrastructureCLVR Benefits runs on Microsoft Azure for virtual machines and managed storage. | |
Database backup and file storageDatabase backups and file storage managed through Amazon AWS S3. | |
Geographic restrictionsAll servers and data hosted exclusively within Europe. No customer data ever leaves the EU/EEA. | |
Compliance certificationsBoth Azure and AWS hold industry-leading certifications (ISO 27001, SOC 2, GDPR compliance). |
📦 Data at Rest
| Control | Status |
|---|---|
Database encryptionAll customer data encrypted at rest using Azure built-in storage encryption (AES-256 with platform-managed keys). | |
Database backupsAutomated every 24 hours, retained for 7 days. Stored in Amazon S3 with SSE-S3 server-side encryption. | |
Application-level encryptionAES-GCM encryption for highly sensitive fields using keys in Key Vault. | Planned |
🔒 Data in Transit
| Control | Status |
|---|---|
Network isolationAll app–database traffic restricted to internal network only. Postgres not exposed to internet; port 5432 blocked at Azure NSG. | |
Database TLS connectionsAll application–database traffic uses TLS with full certificate verification (sslmode=verify-full). | |
HTTPS enforcementAll web traffic encrypted using HTTPS. | |
Secure cookiesAll cookies set with HttpOnly, Secure, and SameSite=strict flags to protect session integrity. |
📋 Data Governance
| Control | Status |
|---|---|
Records of Processing Activities (RoPA)Documented internally in codebase and reviewed during each release cycle. | |
Data retention policiesDeletion and anonymization rules documented internally and reviewed on each release cycle. | |
Data Processing Agreements (DPAs)Tracked internally with all third-party vendors; documentation exists and is maintained, pending formal signatures. | In Progress |
👤 Data Subject Rights
| Control | Status |
|---|---|
Data subject request processesEstablished processes for access, correction, deletion, and portability requests with 30-day response time. Contact hello@clvrbenefits.com for any requests. | |
Privacy PolicyOur privacy policy page is available here. |
🔗 Sub-processors
| Control | Status |
|---|---|
Amazon Web Services (AWS)Cloud storage for uploaded files and encrypted database backups, hosted in EU regions. | |
Microsoft (Entra ID and Azure)Hosting infrastructure and the identity provider used for organisational sign-in (OAuth). | |
Anthropic (Claude)Optional AI receipt scanning and expense auto-approval. Only receipt images and category names are sent, and your data is not used to train models. | |
PostHogProduct analytics used to understand and improve how the platform is used. | |
CloseCustomer relationship management for sales and marketing contacts. |
🤖 AI and Automation
| Control | Status |
|---|---|
AI receipt scanningOptional feature for expense report uploads. When enabled by the company, receipt images are sent to Claude (Anthropic) for extraction of vendor, date, amount, and VAT. Only the receipt image and benefit category names are sent. No employee names, emails, or other personal data. We do not use your data to train models. We retain only what is necessary for the feature and for audit compliance. Companies can disable this feature in AI Settings. | |
AI automated expense evaluationOptional feature that evaluates wellness expense reports (e.g. gym memberships) for automatic approval or decline. When enabled, the AI reviews uploaded receipts and form data against category-specific criteria. HR retains full oversight: all AI decisions are visible to HR with confidence scores and reasoning, and any decision can be reverted at any time. Employees are notified when AI declines an expense and can edit and resubmit. Expenses where AI confidence is below 85% are automatically deferred to human review. If enabled, the AI may also read company policy documents (PDFs, Word files) uploaded to Company Files to better understand company-specific expense policies. We do not use your data to train models. We retain only what is necessary for these features and for audit compliance. All decisions are logged with full audit trail. |
🛠️ Product Security
| Control | Status |
|---|---|
Secure source code accessAccess restricted to authorized team members only. GitHub used with enforced account security. | |
Version control and release processStructured Git workflow (git-flow). All changes tracked, reviewed, and merged into dedicated branches. | |
Environment separationSeparate development and staging environments ensure thorough testing before production deployment. | |
Test data managementTest data carefully selected, anonymized, and managed to avoid sensitive personal information in non-production. | |
Modern secure technology stackBuilt with industry-standard web technologies, containerized infrastructure, and managed cloud services. Regularly updated with security patches. | |
Dependency and package vettingAll external packages reviewed before adoption. Monitor for vulnerabilities and update promptly. |
🛡️ Security Operations
| Control | Status |
|---|---|
Access controlInternal access limited to authorized staff using principle of least privilege. Administrative access restricted. | |
Secrets managementCredentials injected as environment variables, never committed to code or stored in plaintext. | |
System patchingRegular patching of OS, Docker images, and PostgreSQL. | |
Application-level monitoringReal-time error detection and anomaly monitoring via PostHog. | |
System-level monitoringPostgres authentication logs, firewall events (UFW), and system security logs with alerts for suspicious activity. | Planned |
Incident response plan72-hour breach notification process documented internally, available on request, reviewed after significant changes. |