SECURITY AND DATA HANDLING

Built to be trusted with a phone line.

Call tracking sits between your customers and your phone. These are the specific things the service does to keep that connection working, private, and yours.

ISOLATION01

Every workspace is walled off in the database.

Row-level security scopes every query to one workspace, and the application connects with a least-privilege role that cannot bypass it. Carrier credentials live in a separate secret store and never enter ordinary records.

RECORDINGS02

Consent first, then short-lived access.

Recording is off until you turn it on, callers hear the notice you configure, and each call keeps a record of the policy that applied. Playback uses a link that expires in seconds, only for roles you allow, and every play or denied attempt is written to the audit history.

CONTINUITY03

An outage in the app does not take down your calls.

A separate fallback service on its own host holds the last known routes and forwards calls if the main application cannot answer the carrier. Migrations run forward only, and every release is pinned to an image digest with an automatic rollback if its health check fails.

BUILT FOR REAL-WORLD CALLS

What we keep, and what we deliberately do not.

Attribution needs some visitor data. The service keeps the least it can and throws away the rest before it is stored.

What does the website script store about visitors?

Token digests, an immutable first-touch and session snapshot, a site-scoped keyed hash of the address, and a coarse device summary. Query strings and fragments are stripped after the supported attribution fields are read. No fingerprint is built, and visitors who decline storage are tracked for the page only.

Who can see call data and recordings?

Roles from viewer to administrator control every screen and action. Recordings can be played by analysts and above, deleted only with an elevated permission and typed confirmation, and expire on the retention period you set. Transcripts, where enabled, are encrypted at rest with a rotating key.

Can I take my data and leave?

Administrators can export the workspace and start a guarded deletion that releases numbers first, then removes recordings from storage and the carrier, and records the cleanup. Billing state never releases a number or interrupts inbound routing on its own.

PLAN WITH CONFIDENCE

Operating practices you can check.

The service is run as an operated platform; these are standing practices rather than one-time promises. Ask for the details that matter to your review.

04

START WITH ONE TRACKED CALL

See what makes the phone ring.

Create your workspace, choose a plan, and follow the guided setup to your first answered tracking call.

Request access