Voice is customer data.
We treat it that way.
Everything your security review will ask, on one page: the controls, the regions, and what is not in place yet.
The control surface.
Your region. Your rules.
Platform data runs in three regions today. New regions are stood up per contract, and once yours is pinned, audio, transcripts and records stay inside it.
What is true today. What is not.
- Each customer's data is separated at every query.
- Every field the agent writes into your systems is checked on our server first.
- Every call gets a recording, a transcript, a written summary and a sentiment.
- Encrypted in transit with TLS 1.3 and at rest with AES-256.
- Platform data stays in the region your account is pinned to: the UK, the UAE or India today.
- Role-based access with admin and client roles.
- Card payments in US dollars and UAE dirhams; other currencies are charged in US dollars.
- SSO and SAML.
- SOC 2. Planned, not certified.
- Retention periods you set yourself. Retention is fixed by us today.
- Self-serve signup. A person sets your line up within one working day.
- Card billing in pounds, euros or rupees.
- A quality score on each call. Calls get a summary and a sentiment, not a mark.
Updated as each item ships.
How we operate.
We do not train models on your customer data. Conversation content is never used for our own purposes. Retention periods are set by us today; customer-set retention is not in place yet.
Multi-tenant isolation enforced at the database layer, with per-tenant encryption keys and isolated audio pipelines.
Production access is role-based, time-boxed and logged. Customer data access requires a ticketed reason.
Multi-region autoscale, 99.9% uptime SLA, documented disaster-recovery runbooks with annual exercises.
Published subprocessor list with change notifications. DPA available for every customer.