Sub-processor Register
ExpertEase AI uses a small set of vetted third-party sub-processors to deliver the platform. This page discloses every one — what data they receive, and where it is processed. Last updated: 07 July 2026. To subscribe to change notifications contact privacy@experteaseai.com
No Conversation, Document, or Voice Content Leaves Australia
All AI model inference is performed within Microsoft Azure's Australian regions under Azure OpenAI, or on ExpertEase AI's own self-hosted open-weight models on ExpertEase AI-controlled Australian infrastructure. Under Azure OpenAI, conversation content is processed in-region by Microsoft — it is not sent to OpenAI, not retained, and not used for training.
Voice call audio is routed through Twilio's Australian region (AU1) and remains onshore. The single offshore exception is SMS — disclosed in the table below.
Infrastructure & AI
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Microsoft Azure | Cloud hosting, database, file storage, vector search, AI model inference (Azure OpenAI), document processing (Document Intelligence), speech recognition and synthesis, application monitoring | All platform data at rest; documents, conversation content, and voice audio during processing | Australia East (Sydney) Australia Southeast (Melbourne) |
| Self-hosted AI: ExpertEase AI also operates open-weight AI models on its own Australian infrastructure. Digital employees configured for self-hosted AI involve no third-party processor — conversation data never leaves ExpertEase AI-controlled infrastructure. | |||
OpenAI, Anthropic, and Google Cloud are not sub-processors. All AI inference runs via Azure OpenAI in Australian regions or ExpertEase self-hosted models. No conversation content is transmitted to any AI provider outside Australia.
Communications & Payments
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Twilio — Voice | Voice calls and phone numbers | Phone numbers, call audio, call metadata | Australia (Twilio AU1 region) Call audio processed onshore for AU numbers |
| Twilio — SMS | SMS messaging | Phone numbers, SMS message content | United States ⚠ SMS content transits Twilio US infrastructure — disclosed offshore exception |
| Twilio SendGrid | Transactional email (notifications, OTP codes) | Email addresses, email content | United States |
| Stripe | Payment processing and subscription billing | Billing name, email, subscription details. Card data processed solely by Stripe — never stored on ExpertEase systems | United States |
Operational
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Supadata | YouTube transcript retrieval for customer knowledge bases | Publicly accessible video transcript content designated by the customer | ⏳ To be confirmed |
| Better Stack | External uptime monitoring — independent endpoint availability checks only | Public endpoint response status and latency only — no customer data, logs, or content | United States |
| ProxyCheck.io | Security screening — detection of anonymised traffic (VPN/proxy/Tor) and known malicious sources | IP addresses of inbound requests only — no account data, names, or content | United Kingdom |
- Langfuse — AI interaction tracing and quality monitoring (prompts, responses, tool call traces)
- Firecrawl — website content retrieval for customer knowledge bases
- Jina — web content retrieval and processing for customer knowledge bases
Application logs and security telemetry are retained within Microsoft Azure Log Analytics (already listed under Microsoft Azure above) — no third-party log management service receives customer or operational data.
Customer-Directed Integrations
The platform also connects to third-party systems at the customer's direction and under the customer's own accounts — for example Zoho CRM, Zoho Desk, Salesforce, Shopify, Sandwai, Cliniko, Google Calendar, Google Drive, Microsoft Outlook, Calendly, WhatsApp Business, Facebook Messenger, and Zapier.
Data flows to these services only when a customer actively connects them, is governed by the customer's own agreement with each provider, and can be disconnected at any time. These are not sub-processors of ExpertEase AI.
Questions About Our Sub-processors?
Contact our privacy team for sub-processor contracts, data processing agreements, or change notification subscriptions.
privacy@experteaseai.com →Trust Centre · Security · Privacy · AI Safety