Subprocessors

Voice AI deployments touch telephony, speech, language, storage, and downstream systems. This page makes the vendor surface explicit for security and procurement review.

ProviderPurposeData categories
Microsoft AzureCloud hosting, storage, networking, monitoringCustomer workflow data, logs, media, metadata
Twilio or ExotelTelephony, call routing, phone numbersPhone numbers, call metadata, audio routing
Deepgram, Sarvam AI, or equivalentSpeech-to-text and Indian-language speech processingAudio snippets, transcripts, language metadata
ElevenLabs, Sarvam AI, or equivalentText-to-speech and recorded voice generationAgent prompts or generated speech text
Anthropic, OpenAI, Groq, or equivalentLanguage understanding and structured extractionTranscript text and workflow context as configured
SendGrid or equivalentEmail notifications and staff alertsRecipient email, notification content, delivery metadata
Plausible AnalyticsPrivacy-conscious website analyticsPage views, referrer, browser, coarse location
Customer-authorized integrationsERP, CRM, EHR, spreadsheet, WhatsApp, webhook, or support-tool pushApproved captured outcomes and integration logs

How this list is used

This page describes common subprocessor categories for VoiceAxis AI deployments. The exact vendors, regions, data types, and retention rules should be finalized in the customer order form, data processing agreement, and security exhibit before production launch.

Some deployments use only a subset of these vendors. Some enterprise deployments may use customer-selected providers or private integrations.

Typical subprocessors

The table below is a practical overview for procurement and security review. It is not a replacement for the signed subprocessor schedule in a customer agreement.

Change notice

Customers can request subprocessor change notices through privacy@vaanios.com. Production contracts should define the notice period, objection process, and emergency replacement rules.