Account, call, attribution, and optional recording data.
The service processes invited-user account details, provider and destination configuration, call and call-leg metadata, tracking numbers, campaign attribution, pseudonymous visitor sessions, audit evidence, and recordings only when an explicit policy enables them.
Route, attribute, report, secure, and support.
- Connect inbound calls to configured destinations.
- Associate calls with sources and visitor sessions.
- Provide reporting, diagnostics, exports, and audit history.
- Detect failures, validate webhooks, and reconcile provider state.
Workspace policy sets the operational window.
Client addresses are hashed, full browser fingerprints are not stored, diagnostics exclude caller and credential details, and playback links expire quickly. Visitor and recording data are retained under workspace policy and eligible data is removed by lifecycle jobs.
Connected processors follow the deployment.
Twilio processes telephony resources. The deployment may also use object storage and an email delivery provider. Authorized workspace administrators can export or request deletion; privacy questions should use the contact listed above without attaching recordings, credentials, or raw webhook data.