DPA & Compliance
Certifications
- ΕΛΟΤ EN ISO/IEC 27001:2023 (ISO/IEC 27001:2022) — ΣΔΑΠ/00141/01 (UCERT (ΕΣΥΔ accredited, no. 1224)), valid 2026-05-20–2029-05-19
- ΕΛΟΤ EN ISO/IEC 27701:2021 (ISO/IEC 27701:2019) — ΣΔΠΙ/00120/01 (UCERT (ΕΣΥΔ accredited, no. 1224)), valid 2026-05-20–2029-05-19
Data retention
| Category | Default | Configurable | Deletion mechanism |
|---|---|---|---|
| Call recordings and transcriptions (AI and human legs) | 30 days | Per customer and per AI agent, 0–180 days; stricter policies additionally anonymize the caller phone number and clear conversation content | Automated daily retention job; permanent deletion from object storage |
| Protected caller identifiers and their voice clips (when enabled on the agent) | Same as the call recording | Per AI agent, a shorter limit for the encrypted values (1–365 days); CVV and PIN are never stored | Refused from the moment they expire; encrypted values and clips removed by an automated nightly job; erased with the call and on data subject erasure |
| Call summaries and call analysis | Duration of the subscription | Stricter per-agent policies delete or anonymize them; after termination kept at least 30 days, deleted within 60 days | Automated daily retention job; deletion after account termination per the DPA |
| Security logs (audit, activity changes) | 30 days | Extended retention available by specific agreement | Automatic deletion via database TTL indexes |
| Call and technical logs (call, SIP, system, activity reads) | 7 days (SIP registrations: 2 days) | Extended retention available by specific agreement | Automatic deletion via database TTL indexes |
| Database backups (MongoDB platform data) | 30 days | Extended retention available by specific agreement | Automatic deletion from AWS S3 after 30 days (intra-day backups after 7 days), by the backup job cleanup |
| All customer data after contract termination | Return and/or destruction within 60 days (reversibility window); minimum 30 days post-termination retention | Per the Data Processing Agreement | Company purge — permanent deletion of all stored objects and records |
Technical & organizational measures
| Area | Measure |
|---|---|
| Encryption in transit | TLS 1.3 with hybrid post-quantum key exchange (X25519 + ML-KEM-768) on the web application, API and website, and HTTP Strict Transport Security. SIP over TLS and SRTP for voice where supported by the interconnected carrier/PBX; otherwise UDP/RTP restricted at network level (IP allowlisting, firewall). Traffic between our own servers — database replication and the application’s database and cache connections — is also encrypted with TLS and authenticated against our own certificate authority; unencrypted connections are refused. Outgoing connections to mail servers (IMAP/SMTP) and SMS providers verify the server’s TLS certificate. |
| Encryption at rest | Files (recordings, transcriptions, attachments) stored in AWS S3 eu-north-1 with AES-256 server-side encryption. Sensitive credentials and integration tokens encrypted at application level with AES-256-GCM. User passwords stored as bcrypt hashes only. API keys are stored only as SHA-256 hashes and shown once, at creation. Two-factor (TOTP) secrets are encrypted with AES-256-GCM under a purpose-separated key that can be rotated, and two-factor backup codes are stored only as keyed hashes (HMAC). Telephony (SIP trunk) passwords are never returned by the API; only a masked value is shown. Protected caller identifiers (see below) are encrypted one by one with AES-256-GCM under versioned, purpose-separated keys that can be rotated without downtime. |
| Protection of callers’ identifiers | Optional per AI agent. Identifiers callers dictate (Greek AMKA and AFM, Personal Number, IBAN, ID card, passport, GEMI and card numbers) are replaced by placeholders before any text reaches an AI model; the AI never receives the value. The agent speaks only the last four digits. Real values are used only for the tools the agent calls and, if the customer enables it, for non-AI post-call actions (API calls, integrations, webhooks); AI steps always receive placeholders. CVV and PIN codes are never stored. The caller’s side of the recording is replaced by a tone where a protected value was spoken; the original seconds are kept only as a separately encrypted clip. Values and clips expire with the agent’s retention or an earlier per-agent limit and are then removed. |
| Access to protected values | Only company members granted the “Reveal sensitive data” permission, and company administrators, can display a protected value or play its clip; Voice Logica staff do not obtain it through their staff role. Revealing through an AI assistant requires a separate company opt-in and a stated reason, and the assistant receives an expiring listening link, never the audio. Every reveal, playback and real-value transfer is recorded in the audit log and visible to the customer on its privacy page, exportable to CSV; the value itself is never logged. |
| Customer code isolation | Custom code that customers add to workflows runs in an isolated sandbox with no network, file-system or server access, under time and memory limits; it never sees the platform’s credentials or other customers’ data. Addresses that customers configure for integrations and for their own MCP servers pass server-side request forgery (SSRF) checks before the platform connects to them. |
| Tamper-evident audit log | Every audit entry is chained to the previous one with a keyed hash (HMAC-SHA256), per company, so an edited, removed or re-ordered entry is detected on verification. Every night the state of all chains is timestamped by two independent RFC 3161 Time Stamping Authorities; the signed receipts can be verified with standard tools and prove that the log has not been rewritten since. Customers can verify their own chain from the privacy page. |
| Data subject requests by phone | Optional per AI agent: a caller can ask the agent to erase their personal data. The agent files a request for the caller’s own number only; nothing is erased during the call. A company administrator approves it (erasure of that number’s calls, contact details, messages and files) or rejects it with a reason, and every step is recorded in the audit log. |
| Hosting | Primary infrastructure (application servers, self-hosted MongoDB/Redis, voice stack) on Hetzner dedicated servers in Nuremberg (Germany) and Finland — EU/EEA, ISO/IEC 27001 certified data centers. Speech-to-text and text-to-speech default to third-party EU providers; self-hosted AI models on EU dedicated machines are used only on customer selection. Databases are not internet-exposed. |
| Access control | Named per-user accounts, company-scoped data isolation, MFA for privileged remote access and source-code platforms, formal privileged-account lifecycle. Access revoked within 1 month of departure (immediately for privileged access). Sign-in is protected by rate limiting, temporary account lock after repeated failures and two-factor codes with a limited number of attempts. Each internal service uses its own narrowly scoped credentials (least privilege). |
| Incident response | Customer notification without undue delay (service-level alert at 48 hours of detection). Where NIS2 applies: early warning within 24 hours and a detailed notification within 72 hours. For personal-data breaches the customer as controller notifies the competent supervisory authority within 72 hours (GDPR) and Voice Logica provides the necessary assistance. Root Cause Analysis within 2 weeks. Incident subject prefix: [Voice Logica Security Incident]. |
| Database backups | Automated full database backup every 4 hours, encrypted before it leaves our infrastructure (public-key encryption: the servers hold only the public key, the decryption key is kept offline) and stored in AWS S3 eu-north-1 with AES-256 server-side encryption on top. Backups are write-once for their first 7 days: they cannot be modified or deleted, including by Voice Logica administrators. Backup jobs use write-only credentials that cannot read or delete backups. The daily backup is retained about 30 days and intra-day backups about a week, then auto-deleted, with no backup files kept on the production servers. Large operational log collections (call, activity, SIP, audit and system logs, emails) are excluded from backups and instead expire via database TTL (30 days for security logs, 7 days for call, SIP and technical logs). |
| Business continuity | RTO 4 hours, RPO 4 hours (offsite database backups every 4 hours); a 3-node database replica set protects against the loss of a single server; backup restore tested (most recent: October 2026, full database restore in 32 minutes); disaster recovery plan reviewed at least annually. |
| Vulnerability management | Daily monitoring of vendor advisories. Remediation: critical 4 hours, high 48 hours, medium 2 months, low next release. Periodic internal security reviews of authentication, access control, encryption and outbound requests, with findings tracked to remediation. |
| Audits | Annual third-party security audits including ISO/IEC 27001 and 27701 surveillance audits. Customer audit right with 10 business days notice (72 hours in emergencies). |
| Payments | PCI-DSS not applicable — payments processed exclusively by Stripe (PCI DSS Level 1); cardholder data never touches Voice Logica systems. |
Sub-processor register
| Name | Role | Data categories | Location | Transfer mechanism | Default |
|---|---|---|---|---|---|
| Hetzner Online GmbH | Infrastructure (dedicated servers: applications, self-hosted databases, voice stack; self-hosted AI models only on customer selection) | All hosted service data | Nuremberg (Germany) + Finland, EU/EEA | n/a (EEA) | yes |
| Amazon Web Services EMEA SARL | Object storage S3 (recordings, transcriptions, attachments) + email SES | Call recordings, transcriptions, attachments, email content | eu-north-1 (Stockholm), EU/EEA | n/a in-region; AWS DPA SCCs + DPF for any non-EEA access | yes |
| Yuboto Telephony | Telecom interconnection (call routing, numbering, SMS) only for numbers or SMS arranged through Voice Logica; otherwise calls use the customer's own telephony provider, contracted by the customer | Phone numbers, call/traffic metadata, voice content in transit | Greece, EU/EEA | n/a (EEA) | on request |
| OpenAI (OpenAI Ireland Ltd) | LLM — default dialogue/analysis provider (signed DPA); optionally Whisper STT / TTS / embeddings | Conversation text, transcriptions, prompts, call metadata | EU contracting entity; processing may occur in the US | DPA with SCCs; EU-US Data Privacy Framework | yes |
| Soniox Inc. | Speech-to-text — default provider; optionally TTS | Real-time call audio stream, transcriptions; voice-clone samples and cloned voices when the customer creates a clone (stored until deleted) | EU data residency (default); US/JP selectable | n/a for EU residency; otherwise SCCs/DPF | yes |
| Google (Google Ireland Ltd / Google Cloud) | Speech-to-text fallback (EU region); optionally Cloud TTS, Search API, Maps/Places for in-call location tools (location text only) | Real-time call audio stream, transcriptions; location text from location tools | Google Cloud EU regions (Maps/Places: Google global infrastructure) | Google Cloud DPA; SCCs/DPF where applicable | yes |
| Google (Gemini API) | Image analysis — default provider; optionally Gemini LLM on customer selection; not used on agents where the customer enables core-providers mode | Images and attachments submitted for analysis, prompts | Google global infrastructure (processing may occur outside the EEA) | Google DPA; SCCs/DPF where applicable | yes |
| ElevenLabs Inc. | Text-to-speech — default provider (EU data residency); optionally STT | Agent response text to be spoken (transient); voice-clone samples and cloned voices when the customer creates a clone (stored until deleted) | EU data residency (default) | n/a for EU residency; otherwise SCCs/DPF | yes |
| Microsoft Ireland Operations Ltd (Azure Speech) | Text-to-speech fallback (EU region); optionally STT | Agent response text to be spoken (transient) | Azure EU regions | Microsoft DPA (EU Data Boundary); SCCs/DPF where applicable | yes |
| Stripe Payments Europe Ltd | Billing/subscriptions (largely independent controller; card data never touches Voice Logica) | Customer billing details | EU/US | SCCs in Stripe DPA + DPF | yes |
| Anthropic PBC | LLM (on customer selection only) | Conversation text, prompts | US | DPF and/or SCCs | on request |
| xAI Corp. (Grok) | LLM (on customer selection only) | Conversation text, prompts | US | DPF and/or SCCs | on request |
| Groq Inc. | LLM — default for auxiliary in-call processing (knowledge lookup and distillation, in-call assistant, unanswered-question capture, analytics enrichment); not used on agents where the customer enables core-providers mode | Conversation excerpts, knowledge and tool results, prompts | US | DPF and/or SCCs | yes |
| Together AI Inc. | LLM (on customer selection only) | Conversation text, prompts | US | DPF and/or SCCs | on request |
| MiniMax | LLM/TTS (on customer selection only; SCCs/TIA review required before activation for EU data) | Conversation text | Non-EEA | SCCs + Transfer Impact Assessment | on request |
| Deepgram Inc. | Speech-to-text (on customer selection only; no data retention configuration) | Real-time call audio stream | US | DPF and/or SCCs | on request |
| Speechmatics Ltd | Speech-to-text (on customer selection only) | Real-time call audio stream | United Kingdom | EU adequacy decision for the UK | on request |
| Fireworks AI Inc. | Speech-to-text (on customer selection only) | Real-time call audio stream | US (us-virginia-1) | DPF and/or SCCs | on request |
| Murf AI Inc. | Text-to-speech (on customer selection only) | Agent response text (transient) | US | DPF and/or SCCs | on request |