HomeAvA LeadsAvA Orders & PaymentsAvA ProspectNewAvA Social CanvasThe engineCustom AI solutionsAvA for AndroidAvA for iPhoneBetaAvA for desktopBetaTalk to AvAVidya, the AI tutorBFSI & lendingNewHealthcareNewReal estateNewAll solutionsEvery industryIndiaUnited Arab EmiratesUnited KingdomUnited States
Products
Three products, one engine
For you
Your own AvA
Solutions
By industry and by country
Trust · current as of 8 October 2026
Sub-processors
The companies that process customer data on our behalf to run AvA, what each one does, and where we can say where. When this list changes, the date above changes with it.
Hosting, storage and data
| Vendor | Purpose | Data | Location |
|---|---|---|---|
| Amazon Web Services | Application servers; storage of call recordings, documents and exports; outbound email from verified sending domains (SES) | All customer data classes | India (Mumbai, Hyderabad) |
| MongoDB Atlas | Primary database | Account, contact, conversation and configuration records | On request |
| Redis Cloud | Caching, rate limiting and live message fan-out | Short-lived session and message metadata | On request |
| Google Cloud | The calling service (Cloud Run), its call queue (Cloud Tasks, Firestore) and the knowledge-base search service | Call audio in transit, call metadata, knowledge-base content | On request |
| Netlify | Hosting the console and this website | Request metadata; console traffic passes through | Global edge |
AI models and speech
| Vendor | Purpose | Data | Location |
|---|---|---|---|
| Google (Gemini, Cloud Text-to-Speech) | Realtime voice conversations, meeting notes and speech synthesis | Conversation audio and text | On request |
| Groq | Language model for calls and assistant generation | Conversation text | On request |
| OpenAI | Assistant writing, document and image reading | Prompts, uploaded documents and images | On request |
| Deepgram | Speech-to-text on calls | Call audio | On request |
| Sarvam AI | Speech-to-text in Indian languages | Call audio | On request |
| Cartesia | Cloned-voice speech synthesis | Text to be spoken; voice samples for cloning | On request |
Channels
| Vendor | Purpose | Data | Location |
|---|---|---|---|
| Meta (WhatsApp Cloud API) | WhatsApp messaging on numbers AvA hosts | Message content and phone numbers | On request |
| Infobip | WhatsApp messaging for accounts connected through Infobip | Message content and phone numbers | On request |
| Twilio | Phone numbers, calls and SMS outside India | Call audio, message content and phone numbers | On request |
| Licensed Indian telephony carriers | Phone numbers and calls in India | Call audio and phone numbers | India · named in the DPA |
| ImprovMX | Relay for platform email (sign-in, alerts, invoices) | Recipient address and message content | On request |
Billing and security
| Vendor | Purpose | Data | Location |
|---|---|---|---|
| Razorpay | Wallet top-ups in India | Payer name, contact and payment reference (card details stay with Razorpay) | India |
| Stripe | Card top-ups outside India | Payer name, contact and payment reference (card details stay with Stripe) | On request |
| ipwho.is | Approximate location of a new sign-in, for the security page and alerts | IP address at sign-in | On request |
| Cloudflare (Turnstile) | Bot check on this website’s demo-call form | Browser signals on that form only | Global edge |
Connected by you
Not our sub-processors.
These are accounts you connect yourself. They process data under your own agreement with them, not ours.
- Your own Razorpay, Cashfree or Stripe account, for payment links you send
- Your own Google, Microsoft or IMAP mailbox
- Your own Twilio account, if you bring one
- Your own WhatsApp Business account, if you connect it
- Your CRM (HubSpot, Zoho), store (Shopify), logistics (Shiprocket), accounts (Zoho Books, Tally) and Google Sheets
- Any MCP server or REST API you connect
Locations marked “on request”, and the names of our Indian telephony carriers, are given in the data processing agreement.