Legal
Sub-processors
The third parties that may process customer data on our behalf, along with what they do, where they sit, and how transfers are safeguarded.
Last updated: August 4, 2026
1. What this page is
A sub-processor is a third-party service that VocUI engages to help deliver the platform and that may process customer personal data as part of that delivery. This page is the canonical list. It supplements (and is referenced by) our Privacy Policy and Terms of Service.
Sub-processors listed below are engaged under written agreements that require them to protect customer data, limit its use to the services they provide to us, and apply the transfer safeguards noted in each entry. Customer-side integrations that you connect yourself (e.g., your own Slack workspace, your own CalDAV calendar, your own Twilio account) are not VocUI sub-processors.
2. Current sub-processors
DeepSeek
- Service
- Large language model — default chat generation
- Data processed
- Customer chat input and the retrieved knowledge-base context sent to the model at request time
- Location
- People’s Republic of China
- Transfer safeguards
- Governed by DeepSeek’s published API terms. EU/UK customers with data-residency or provider requirements should review the cross-border AI processing notice below (§3) and contact [email protected] before sending chat traffic.
Google (Gemini)
- Service
- Large language model — automatic fallback for chat generation when the default provider is unavailable
- Data processed
- Customer chat input and the retrieved knowledge-base context sent to the model when fallback routing engages; knowledge-source text if a Gemini embedding model is configured
- Location
- United States
- Transfer safeguards
- EU/UK transfers under Google’s data-processing terms, which incorporate Standard Contractual Clauses where required.
Anthropic (Claude)
- Service
- Large language model — held in reserve; not in the current chat routing path
- Data processed
- Customer chat input and the retrieved knowledge-base context, only if Anthropic is activated in the platform-level routing path
- Location
- United States
- Transfer safeguards
- EU/UK transfers under Standard Contractual Clauses per Anthropic’s Data Processing Addendum.
- Notes
- Listed here so a platform-level activation can occur without adding a new sub-processor; any routing change is communicated per §4.
OpenAI
- Service
- Embeddings (all plans); chat models held in reserve
- Data processed
- Knowledge-source text submitted for vectorization; chat input only if OpenAI is activated in the platform-level routing path
- Location
- United States
- Transfer safeguards
- EU/UK transfers under Standard Contractual Clauses per OpenAI’s Data Processing Addendum.
Stripe
- Service
- Payment processing for subscriptions and add-ons
- Data processed
- Billing identifiers, payment method tokens, transaction metadata
- Location
- United States
- Transfer safeguards
- EU/UK transfers under Standard Contractual Clauses. Stripe acts as an independent controller for payment data.
OVH
- Service
- Infrastructure — Postgres database, application servers, object storage
- Data processed
- All application data at rest, including accounts, chatbots, knowledge bases, chat sessions, and billing records
- Location
- France (EU)
- Transfer safeguards
- Provider is EU-based. No additional cross-border transfer mechanism is required for EU/UK customer data stored on EU regions.
Telnyx
- Service
- Managed SMS, RCS, and voice (only for customers who enable these channels)
- Data processed
- Phone numbers, SMS contents, call audio, call metadata
- Location
- United States
- Transfer safeguards
- EU/UK transfers under Standard Contractual Clauses per Telnyx’s Data Processing Addendum.
- Notes
- Customers can bring their own Twilio account instead of using our managed Telnyx relationship; in that case Twilio becomes the customer’s direct sub-processor, not ours.
3. Notice on cross-border AI processing
DeepSeek, our default LLM sub-processor, is incorporated in the People’s Republic of China. Transfers of personal data to DeepSeek are governed by DeepSeek’s published API terms.
LLM routing on VocUI is configured at the platform level: every customer’s chat traffic uses the same default provider (currently DeepSeek), with automatic fallback to Google Gemini (United States) when the default is unavailable. VocUI does not currently offer per-customer routing to an alternative LLM provider. If your organisation has residency or provider requirements that this routing does not satisfy, contact [email protected] before sending chat traffic — we will confirm the current routing in writing and discuss whether VocUI can meet your requirement.
4. How we communicate changes
Material changes to this list — adding a new sub-processor, retiring one, or changing the jurisdiction in which a sub-processor processes customer data — will be communicated to customers at least 30 days before they take effect, by email to the account billing contact and by updating this page.
To subscribe to sub-processor change notifications without being a paying customer, email [email protected].
5. Contact
Questions about a specific sub-processor, transfer safeguards, or data-subject requests:
Email: [email protected]