Service Providers & Data Processing
Service providers and the current data-processing chain.
This public register identifies operational providers involved in delivering the current service without asserting unverified contractual processor or subprocessor classifications.
Last updated: 20 August 2026
How to read this register
The table identifies providers in the current customer-data and service-processing chain. Exact locations, contractual terms, retention, security settings and downstream-provider roles require deployment-specific review.
Development suppliers that are not intended to receive customer data are kept separate from this table. Optional or dormant code integrations are not presented as current service-processing providers.
Provider register
| Category | Provider | Purpose |
|---|---|---|
| Hosting / deployment | Vercel | Public application hosting and deployment. |
| Authentication / data services | Supabase | Application authentication and configured organisation data services. |
| Phone bridge / services | Railway | Hosting for the current Ava phone bridge. |
| Communications | Twilio | Voice, ConversationRelay and SMS where enabled; direct Logicl account relationship. |
| Routed speech-to-text | Deepgram (via Twilio) | Flux speech-to-text for Ava calls; no direct Logicl Deepgram account. |
| Routed text-to-speech | Google TTS (via Twilio) | Text-to-speech for Ava calls; no direct Logicl Google account. |
| AI model routing | Hugging Face Inference Providers | Direct Logicl routing and billing relationship for the governed Qwen model path. |
| Routed model inference | DeepInfra (via Hugging Face Inference Providers) | Downstream inference for the selected Qwen model; no direct Logicl DeepInfra account or credential. |
Related trust pages
Questions or concerns? Use the dedicated privacy and security contact path.
Contact privacy & security