Security and data handling
How recordings, transcripts, scores, and extracted data are stored, protected, and deleted.
Security Standards
- -
Encryption: AES-256 at rest, TLS 1.3 in transit
- -
Access: RBAC
Regulatory requirements
- -
Voice profiles are biometric data and are handled as such; see our privacy policy.
- -
GDPR: data processing agreement, retention and deletion controls, support for data-subject requests.
- -
Discuss your security and regulatory requirements with our team before uploading regulated data.
Data Protection
- -
Voice profiles: stored as numeric vectors used for speaker matching. They remain biometric data and are protected accordingly; storing a vector instead of audio does not by itself rule out voice reconstruction.
- -
Secure uploads: Recordings are encrypted in transit via TLS and stored with automated replication to S3-compatible object storage (Cloudflare R2).
Infrastructure
- -
EU-Hosted: Runs in European data centers (Hetzner, Finland) with the database isolated on a private network.
- -
Containerization: Services run in Docker containers with strict resource isolation and regular image updates.
- -
Vector database: voice profiles are stored in PostgreSQL with pgvector on the private network.
Access Control
- -
RBAC: Granular Role-Based Access Control (Owner, Admin, Member) ensures users only access data relevant to their role.
- -
Policy enforcement: authorization is checked per record at the controller level (Pundit policies).
- -
Authentication: Secure session management via Devise with support for Multi-Factor Authentication (MFA) and Google OAuth 2.0.
Infrastructure
EU-Hosted: Runs in European data centers (Hetzner, Finland) with the database isolated on a private network.
Questions about security
Discuss your security and regulatory requirements with our team at info@identitycall.ai.
Secure your insights
Small teams: sign up and analyze 5 of your own calls free, no credit card. Larger teams: book a 30-minute consultation and we analyze 3–5 of your recordings together.
