Subprocessors and Service Providers

adaptlive uses subprocessors and service providers to operate the service. These providers may process customer data, personal information, account information, call audio, transcripts, logs, support content, billing details, or usage data depending on the service they provide.

Provider use may vary by customer plan, enabled feature, region, integration, consent choices, and deployment configuration.

• Vercel: marketing site and app hosting, preview deployments, edge delivery, deployment pipeline, analytics, performance insights, and related infrastructure.
• Fly.io: media gateway hosting, including always-on machines that hold the Twilio Media Streams WebSocket for the duration of each live call.
• Twilio: programmable voice, phone-number provisioning, call routing, call recording (when enabled), media streams, and call status callbacks.
• Deepgram: streaming speech-to-text provider used to produce live transcripts of phone calls.
• Anthropic, OpenAI, and Google (Gemini): AI providers used for live extraction, summarization, signal detection, and other AI-assisted product features. The active model is configurable per-purpose.
• ElevenLabs: text-to-speech provider used for voice agent personas and synthesized audio playback when enabled.
• Managed PostgreSQL provider: tenant-aware database services for adaptlive records (call sessions, transcripts, slots, drafts, audit events).
• Managed Redis provider: live pub/sub bus that ferries transcript and slot events from the media gateway to the live cockpit.
• S3-compatible object storage provider: storage for call recordings, transcript exports, and attachments when enabled.
• Inngest: durable function platform for post-call work (summaries, draft creation, recording transcode, CRM sync).
• Clerk: authentication, organization membership, and user identity for the adaptlive product workspace.
• Merge.dev and native CRM adapters (Jobber, Housecall Pro, others): connect approved drafts to customer CRMs and job systems on the customer's instruction.
• Ably: realtime presence and event delivery between the media gateway, server, and live cockpit clients.
• Stripe: checkout, billing, invoices, subscription management, and payment processing.
• Google: Google Tag Manager, Google Analytics, and advertising or conversion measurement when enabled by consent and tag configuration.
• Sentry: error monitoring, performance troubleshooting, diagnostics, and reliability investigation.
• Email and communications providers: transactional messages, contact requests, account notices, workflow notices, reminders, and product communications.
• Customer-configured integrations: Zapier, Make, webhook endpoints, or other systems connected by or for a customer.

We select providers based on the function they perform, the sensitivity of information involved, reliability, security posture, contractual terms, and business need.

Where appropriate, providers are restricted to processing information for the services they provide to adaptlive and are subject to confidentiality, security, or data protection obligations.

Some integrations are enabled, configured, or supplied by the customer (e.g. a CRM connection, a Zapier flow, or a generic webhook). Customers are responsible for the credentials, endpoints, permissions, data mapping, downstream use, and security of customer-controlled integrations.

adaptlive is not responsible for third-party systems that a customer connects to adaptlive or for how those systems process exported or transmitted data.

We may add, remove, or replace subprocessors and service providers as adaptlive evolves. Material changes will be reflected in this legal center, customer agreements, or procurement materials where required.

Enterprise customers that need advance notice, objection rights, region restrictions, or a signed subprocessor exhibit should address those requirements in a written agreement.

Questions about subprocessors may be sent to privacy@adaptlive.app or to the customer's account contact.