Data & Privacy
Subprocessors
Third-party services that process data on behalf of DialerBee. This list is maintained for transparency and to support our customers' GDPR and data governance obligations.
Quick answer
What does the DialerBee subprocessor list cover? It names the third-party services that process data on behalf of DialerBee. For the platform it gives the purpose, the data processed and the processing location of each: Hetzner for infrastructure hosting in the EU, Cloudflare for CDN, DDoS protection and DNS, Google Cloud Platform for the speech-to-text used in AMD classification, Postmark for transactional email delivery, Sentry for error monitoring, and GitHub for source code hosting and CI/CD. Customers are notified by email at least 30 days before a new subprocessor begins processing data, and customers who object may contact us to discuss alternatives. The Meet Layla live demo on this website also uses Deepgram and Munsit for speech recognition, Google's Gemini API for Layla's replies, ElevenLabs for her voice and Vultr to host the demo server; they are listed separately below with the purpose and the data processed.
| Subprocessor | Purpose | Data Processed | Location |
|---|---|---|---|
| Hetzner | Infrastructure hosting | Application data, databases, recordings | EU (Germany, Finland) |
| Cloudflare | CDN, DDoS protection, DNS | Web traffic, static assets | Global edge network |
| Google Cloud Platform | Speech-to-text for AMD classification | Short audio segments (first 3s of call) | EU / US (configurable) |
| Postmark | Transactional email delivery | Email addresses, notification content | US |
| Sentry | Error monitoring and alerting | Error logs, stack traces (no PII) | US |
| GitHub | Source code hosting, CI/CD | Source code (no customer data) | US |
Live demo (Meet Layla)
These services process data only for the Meet Layla live demo on this website (dialerbee.com/talk/), not for the DialerBee platform. What the demo keeps, and for how long, is set out in our AI Data Policy.
| Subprocessor | Purpose | Data Processed |
|---|---|---|
| Deepgram | Speech recognition for English demo calls | The visitor's voice during the call |
| Munsit | Speech recognition for Arabic demo calls | The visitor's voice during the call |
| Google (Gemini API) | Writes Layla's replies | The words recognised from the visitor's voice and the conversation so far |
| ElevenLabs | Layla's voice (text to speech) | The text of Layla's replies |
| Vultr | Hosts the demo server and its relay (TURN) server | Call audio in transit, IP addresses, technical logs |
| Cloudflare | The demo's sign-up step and bot check (Turnstile) | Name, email address and IP address; browser signals for the bot check |
This table does not give processing locations for the demo services; for questions about them, contact legal@dialerbee.com.
Change notification
We notify customers of subprocessor changes via email at least 30 days before a new subprocessor begins processing data. Customers who object to a subprocessor change may contact us to discuss alternatives.
To subscribe to subprocessor change notifications or request our full Data Processing Agreement, contact legal@dialerbee.com
Last updated: November 2026