Sub-processors
These services handle Open Calls data on our behalf. We update this list before adding a processor that would receive customer content. Reviewed September 16, 2026.
| Processor | What it does for us | Where | What it can see |
|---|---|---|---|
| Cloudflare | Website, API, call engine, queues, private file storage, email delivery | Global edge; storage in the United States and European Union | Account, workspace and call data in transit and at rest |
| Supabase (AWS) | Authentication and the application database | Frankfurt, Germany | Accounts, workspaces, call records, transcripts, billing ledger |
| Twilio | Telephony, caller numbers, optional call recordings | United States | Phone numbers dialled, call audio, recordings when enabled |
| OpenAI | Voice conversation and reasoning during calls, result extraction | United States | Call audio and transcripts during a call, the objective and approved context |
| Stripe | Payments, cards, invoices, tax where enabled | United States | Payment details (never stored by Open Calls), billing email |
| Better Stack | Uptime monitoring, operational alerts, optional browser diagnostics | European Union | Operational events; browser diagnostics only with your consent, no call content |
| GitHub | Source code, continuous integration, encrypted backup artifacts | United States | Encrypted backup bundles |
| Google, GitHub (sign-in) | Optional social sign-in | United States | Your basic profile when you choose that sign-in |
Experimental voice providers (Google Gemini, xAI) are used only for internal benchmarks with owned test numbers, never for customer calls, until they are listed here.
Questions or a data-processing agreement: privacy@opencalls.dev.