Skip to content
Security

Controls first. Claims second.

Here is exactly what the platform implements to protect your leads, recordings and customer conversations — in plain language.

Authentication

Google sign-in with optional two-factor for admins, signed session cookies, and server-side session revocation when access needs to be pulled.

Authorization

Role-based access: Admin, Branch Manager, Agent, Viewer and Developer — plus custom roles. Every API enforces permissions server-side, not just the UI.

Branch isolation

Branch-scoped data access enforced in SQL. Branch managers see and operate on their branch only; admins see everything.

Session security

Fail-closed session validation — a session that cannot be verified is rejected — with epoch-based revocation so old tokens stop working the moment access changes.

Webhook verification

Signature checks on Meta and Exotel webhooks. Requests that fail verification are rejected fail-closed, never processed.

Audit logging

Sensitive actions are recorded in an append-only audit trail, protected from tampering, so changes can always be traced to an actor.

Rate limiting

Public endpoints are rate-limited per client to blunt abuse and credential-stuffing attempts without touching real users.

AI controls

One-click AI pause (global or per branch), mandatory AI disclosure, recording consent, and DND enforcement before every dial.

Data protection

Call recordings are stored server-side and access-controlled by role. Provider keys and secrets live server-side only — never in the browser.

Data retention & backups

Retention is configurable to your policy, and backup procedures are documented in the deployment guide for your own operations.

Want to see these controls in the console? Book a Demo