Security and governance
Controls you can check, not badges
Every statement on this page describes a control that exists in the platform. Where we have no certification to show, we say so rather than imply one.
What is in place
Six controls, each of them the platform's own
- 01
Tenant isolation
Each customer is an organisation. Every record, secret, cache key and knowledge-base collection is scoped to it; nothing is shared between customers by default.
- 02
Roles and sign-in
Roles and permissions decide what each user, agent and integration may read and change. Single sign-on with Google, Microsoft Entra ID or Okta.
- 03
Human approval
Workflows carry approval gates. A sensitive, financial or irreversible step pauses until a named person approves or rejects it, and the decision is recorded.
- 04
Audit trail
Conversation events, tool calls, approvals, outcomes and errors are written to an audit service with the actor, the time and the organisation.
- 05
Data handling
Encrypted in transit and at rest on AWS. Credentials live in a managed secrets store, never in code or configuration files. Call recordings and transcripts are kept under the customer's own retention setting.
- 06
Where it runs
AI Assist runs in AWS Asia Pacific (Mumbai). This website and its own admin console run under the same rules: roles, an audit log and encrypted settings.
Plain speaking
What we do not claim
We hold no third-party security certification today, and we do not describe the platform as compliant with any regulation by assertion. Customers in regulated sectors get the controls above, a written description of how data flows, and our answers to their questionnaire.
Consent capture, do-not-contact lists and calling windows for outbound campaigns are designed and being built; until they are live, outbound calling is configured per deployment with the customer.
Questions we are asked
The usual ones
Can our data be used to train models?
No. Conversations and documents are used to answer within your workspace. Models are reached through providers under your own key or ours, with no training on your data.
Who can listen to a recording?
Only people with a role that allows it in your organisation, and every playback is logged.
What happens when the AI is unsure?
It hands over to a person with a summary, or stops at an approval gate. It is not allowed to invent an availability, a price or a status; those come from the connected system or not at all.
Can we delete a person's data?
Yes. Erasure removes the person from conversations, records, recordings and the knowledge base, and a report lists each store that was cleared.
Send us your questionnaire
We answer security and data-protection questionnaires in writing, with the engineers who built the controls.
Book a time instead