Different providers, different roles
Open Voice Agent Ltd normally processes a business’s receptionist records on that business’s instructions. Suppliers performing that processing for Open Voice Agent are subprocessors. The DPA governs authorisation, advance change notices, objections and Open Voice Agent’s responsibility for their processing obligations.
A supplier can also act as an independent controller for specified account, security, telecommunications or payment purposes. That role requires its own assessment and information; listing a company does not turn all its activities into subprocessing.
Standard electronic supplier agreements can incorporate the required written data-processing terms. Open Voice Agent does not automatically contract directly with every hosting or model provider in a supplier’s onward chain.
Providers and processing functions
Providers are used according to the feature, service configuration, customer instructions and applicable privacy choices. The functions below cover customer services and Open Voice Agent’s own business activities. The applicable processing schedule identifies which providers act as subprocessors for customer records.
Scroll sideways to read the full table.
| Service | Relevant processing |
|---|---|
| Google Cloud, Amazon Web Services (AWS), Cloudflare and Neon | Application and tools hosting, database/file storage, network delivery, security and necessary operational processing, according to the selected service |
| ElevenLabs; OpenAI; Anthropic; Google; xAI/Grok; DeepSeek; Z.ai/GLM; Mistral; and the hosting providers used for Meta/Llama models | AI-assisted onboarding, website/document extraction and knowledge organisation; text/voice processing, speech, analysis and configured conversation/audio storage, according to the feature |
| Twilio, where used for the receptionist | Telephone routing and enabled, authorised messaging or transfers |
| Resend | Authentication and notification emails; submitted enquiries/applications to the authorised Open Voice Agent reviewer, with your email as reply-to where appropriate |
| Proton | Open Voice Agent's business email correspondence, including general/privacy and billing enquiries |
| Stripe, when billing is used | Payment and subscription administration under its applicable processor and independent-controller roles |
| Google Calendar, Microsoft 365/Outlook, Apple/iCloud and CalDAV calendar hosts | Authorised availability, calendar and scheduling actions |
| Calendly, Cal.com, Acuity Scheduling, SimplyBook.me, Square Appointments and Fresha | Authorised booking, scheduling and related records for the selected connection |
| HubSpot, Salesforce, Pipedrive, Zoho CRM and Microsoft Dynamics 365 | Authorised customer/contact, enquiry and workflow records |
| Zapier, Make and hosted automation services; the infrastructure used for self-hosted n8n | Selected integrations, authorised action payloads and necessary connection/execution information |
| Google/YouTube, Meta/Facebook/Instagram/Threads, X, LinkedIn, TikTok, Reddit, Pinterest, Snapchat and Bluesky, according to the platform function used | Company profiles and communications, lead forms, advertising and applicable measurement/audience functions; platform availability and privacy choices determine the relevant processing |
Better Auth runs within Open Voice Agent’s application; it is not a separate hosted authentication subprocessor.
The approved schedule identifies the actual response, analysis, speech and backup processing/hosting roles. A model name alone does not identify its receiving legal entity: a model may be hosted by ElevenLabs rather than sent to its original developer. The separate Open Voice Agent marketing assistant is not automatically part of a customer’s receptionist chain.
Open Voice Agent’s own business services and customer recipients
Open Voice Agent uses Proton for its own company correspondence and Stripe for payment/subscription administration when billing is used. Its own forms and assistant handle sales, custom-integration and affiliate enquiries; Resend can deliver submissions to the authorised Open Voice Agent reviewer with the applicant’s email as reply-to. These are Open Voice Agent-controller purposes, distinct from processing a customer’s receptionist records.
Company-domain DNS through Cloudflare, registration through Spaceship, company administration and developer tools concern Open Voice Agent’s own business. They are included in a customer’s processing schedule only where an actual instructed customer-data flow requires that role.
A customer’s chosen mailbox, CRM or calendar is its instructed recipient, not automatically Open Voice Agent’s subprocessor. Direct integrations are included only where the order identifies the supported function and its processing arrangements.
Entities, locations and changes
The approved supplier schedule supplied with the order identifies each actual legal entity, enabled function, processing and support countries, applicable UK transfer route and relevant onward processing. It is supplied before that processing begins. This function-level directory is not customer authorisation of unspecified entities or countries.
A London application or database region does not locate all logs, backups, support access, AI, telephone or email processing there. Resend’s sending-domain region is Ireland; its documentation states that account data, email metadata, logs and API records are stored in the United States regardless of that region. UK service availability is not a promise of UK-only processing.
Restricted transfers need a valid applicable adequacy route or binding safeguard, such as the UK Addendum or IDTA, with the required assessment and additional protection. An EU clause or a supplier’s advertised region alone is insufficient.
Open Voice Agent gives written advance notice of a proposed subprocessor addition or replacement, with a meaningful opportunity to object on reasonable data-protection grounds. The DPA process applies before the affected processing starts.
Provider questions
Contact team@openvoiceagent.com for the provider details and safeguards applicable to your account or interaction. The privacy notice explains Open Voice Agent’s separate controller activities.