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. A workspace request may also retain a bounded source path, audience segment, request intent, partner code, and submitted UTM values so the operator can understand which acquisition path created the request. Billing records include billing contact details, selected plan and interval, Stripe customer and session identifiers, and payment, invoice, and subscription status. Full card numbers are not stored by Advanced Call Tracking.
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.
- Measure workspace requests against their declared acquisition source.
- 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. Registration attribution accepts only named, length-bounded fields and does not persist an arbitrary query string. Visitor and recording data are retained under workspace policy and eligible data is removed by lifecycle jobs.
Connected processors follow the deployment.
Our telephony carrier, currently Twilio, processes phone-number and call resources; a change of carrier is reflected in a new version of this notice. Stripe processes payment details and billing events. 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.