What the platform does to keep data safe, what we can and cannot yet claim, and how to ask for the documents your procurement team needs.
We list an attestation here when it has been issued, and not before. Until then, ask for our security questionnaire.
These are capabilities that help an organisation meet its own obligations. They do not make an organisation compliant by themselves: policies, training and contracts remain the customer's to put in place.
Staff get roles instead of passwords to everything: 14 shipped roles over 109 separate permissions, with optional limits to certain assistants or calls, explicit denials that always win, and a record of every change.
Finished calls are sealed into a hash chain with daily signed roots, checked on a schedule, with a retention lock and an optional external timestamp authority.
Reviewers see masked personal information unless they choose to unmask it, and every view is recorded. Card numbers are captured on the keypad and never reach the transcript or recording.
Credentials the platform holds for other services, such as carrier and payment accounts, are stored encrypted and are never shown again after they are entered.
Every record belongs to one account, assistants and tools can only read their own account, and a lookup that names another account is refused.
Spoken and typed input is screened for prompt injection, tool use is locked down, and a call is refused if its system prompt was altered outside the application.
Retention periods, legal holds, single-call erasure, an erasure tool for personal data with a dry run, and a signed, expiring export of an account's own data.
Capability, prompt and knowledge-base changes are versioned, so a mistake can be found and undone.
We answer from the product, not from a template. Our sub-processor list is provided on request.
Email tech.support@support-services-one.com with what you found. We acknowledge every report.