Skip to content

Platform · Security

Nothing leaves your
perimeter that you did
not decide to send.

The runtime, the models and the observability store run where you deploy them. No third-party model hears your callers, and no transcript trains a model anyone else uses.

Book a Demo Request the security package
  1. Where your data goesAudio, models and records, all of them yours
  2. Risks and controlsEvery risk your review raises, its control
  3. EvidenceEvery framework, and its own mark
  4. DocumentsWhat your review team receives when it asks
Your perimeter, with the Voicing runtime inside itYour perimeter drawn as a system diagram. Telephony enters through a dock on the left edge and people work through a dock on the right; both join the Voicing runtime, where Voice AI Agents, Real-Time Translation, Knowledge Mesh and Agent Assist run. Under the runtime, the models run on your compute and the observability store keeps transcripts, traces and evaluations. Your systems of record dock on the bottom edge and the runtime reads and writes them by policy. Nothing leaves the perimeter.Your perimeterEgress: noneVoicing runtimeVoice AI AgentsAnswers and completes callsReal-Time TranslationBoth directions, mid-callKnowledge MeshCited answers, your recordsAgent AssistThe same answer, for peopleModelsProprietary LLMsSpeech to textText to speechCPU inferenceObservability storeTranscriptsTraces and tool callsEvaluationsRetention you setTelephonySIP and CCaaSSystems of recordCRM, core, ticketsPeopleHuman agentsRead/writeThe boundary you chooseOn-premises, cloud or regionAudio and transcriptsRetention is yours, to zeroModel weightsYours to tune, never sharedEvery turn on recordExports to your monitoringYour roles, your APIsWrites only what you permit
Your perimeter, with the Voicing runtime inside itYour perimeter drawn as a system diagram. Telephony enters through a dock on the left edge and people work through a dock on the right; both join the Voicing runtime, where Voice AI Agents, Real-Time Translation, Knowledge Mesh and Agent Assist run. Under the runtime, the models run on your compute and the observability store keeps transcripts, traces and evaluations. Your systems of record dock on the bottom edge and the runtime reads and writes them by policy. Nothing leaves the perimeter.Your perimeterEgress: noneVoicing runtimeVoice AI AgentsAnswers and completes callsReal-Time TranslationBoth directions, mid-callKnowledge MeshCited answers, your recordsAgent AssistThe same answer, for peopleModelsProprietary LLMsSpeech to textText to speechCPU inferenceObservability storeTranscriptsTraces and tool callsEvaluationsRetention you setTelephonySIP and CCaaSSystems of recordCRM, core, ticketsPeopleHuman agentsRead/write
  1. The boundary you chooseOn-premises, cloud or region
  2. Audio and transcriptsRetention is yours, to zero
  3. Model weightsYours to tune, never shared
  4. Every turn on recordExports to your monitoring
  5. Your roles, your APIsWrites only what you permit
  • Inside your perimeter
  • No third-party model
  • Zero-retention mode
Where your data goes01 / 05

Everything a call produces stays on your side of the boundary.

Audio, models and records share one deployment boundary, drawn where you deploy. Retention, training and access are your settings, not ours.

  • Audio and transcripts

    Processed inside your boundary, kept as long as you decide.

  • Model weights and training

    Tuned on your side. Your calls improve no one else's model.

  • Systems of record

    Read and written through your APIs, under your own roles.

One detail, followed

A caller reads out a card number. Here is everywhere it goes.

Your perimeterSpokenon the callMasked inthe capture pathThe transcript holdsthe outcome onlyThe payment system,through your APIThe trace, stampedwith actor and toolThe modelThe digits never reach itYour perimeterSpokenon the callMasked inthe capture pathThe transcript holdsthe outcome onlyThe payment system,through your APIThe trace, stampedwith actor and toolThe modelThe digits never reach itYour perimeterSpokenon the callMasked inthe capture pathThe transcript holdsthe outcome onlyThe payment system,through your APIThe trace, stampedwith actor and toolThe modelThe digits never reach itYour perimeterSpokenon the callMasked inthe capture pathThe transcript holdsthe outcome onlyThe payment system,through your APIThe trace, stampedwith actor and toolThe modelThe digits never reach itYour perimeterSpokenon the callMasked inthe capture pathThe transcript holdsthe outcome onlyThe payment system,through your APIThe trace, stampedwith actor and toolThe modelThe digits never reach it
Illustrative
Risks and controls02 / 05

One risk, one control, and its proof.

Each row is a risk your review will raise, in the words it uses. The control beside it is the one we deploy, and the evidence line names what we send.

  1. A card number is in a transcript
  2. Call data leaves your perimeter
  3. An agent acts without authority
  4. A vendor's model hears the call
  5. You cannot prove what happened

RiskA card number is in a transcript

Sensitive details are masked at capture, and regulated call types retain nothing.

How it is enforced

Masking runs in the capture path, before a transcript is written, and the retention rule for each call type is a setting you hold.

EvidenceRedaction policy on request

Evidence03 / 05

Every framework your review names, and the mark beside it.

The frameworks your questionnaire asks about, each with its own mark beside it. The reports come under NDA.

  • ISO 27001:2022

    Information security

  • SOC 2 Type 1

    How controls are designed

  • SOC 2 Type 2

    How controls run over time

  • PCI DSS

    Cardholder data

  • HIPAA

    Protected health information

  • GDPR and CCPA

    EU and California privacy

  • ISO 42001:2023

    Management system for AI

  • DORA

    Operational resilience

  • ISO 17442:2020

    Legal entity identifier

Your review team needs the paper, not the logo. The scope, the issuer, the reference and the expiry for each one travel in the package, beside the answers to your questionnaire.

Request the security package
Documents04 / 05

Your questionnaire, answered in your format.

The package is the architecture diagram, the data-flow inventory and the attestation context, the same documents we deploy from, not a marketing deck.

Send the questionnaire you already use. It comes back answered line by line.

Book a DemoRequest the security package

The security package, opened

Eight documents, each one answering a question above.

How it is deployedHow it is provedDeployment architecture diagramDoes call data leave your perimeter,or stay in the one region you name?Data-flow inventoryDoes everything a call producesstay on your side of the boundary?Redaction policyIs a card number in a transcript,or masked before one is written?Model inventoryDoes a vendor's model hear the call,or does every model run inside?Guarded-execution methodCan an agent act without authority,or is policy checked before it runs?Redacted trace exportCan you prove what happened,on every turn, action and write?Attestation contextWhich frameworks does your review name,and what scope does each one carry?Your questionnaire, answered line by lineDoes the questionnaire you already usecome back answered, in your format?How it is deployedHow it is provedDeployment architecture diagramDoes call data leave your perimeter,or stay in the one region you name?Data-flow inventoryDoes everything a call producesstay on your side of the boundary?Redaction policyIs a card number in a transcript,or masked before one is written?Model inventoryDoes a vendor's model hear the call,or does every model run inside?Guarded-execution methodCan an agent act without authority,or is policy checked before it runs?Redacted trace exportCan you prove what happened,on every turn, action and write?Attestation contextWhich frameworks does your review name,and what scope does each one carry?Your questionnaire, answered line by lineDoes the questionnaire you already usecome back answered, in your format?How it is deployedHow it is provedDeployment architecture diagramDoes call data leave your perimeter,or stay in the one region you name?Data-flow inventoryDoes everything a call producesstay on your side of the boundary?Redaction policyIs a card number in a transcript,or masked before one is written?Model inventoryDoes a vendor's model hear the call,or does every model run inside?Guarded-execution methodCan an agent act without authority,or is policy checked before it runs?Redacted trace exportCan you prove what happened,on every turn, action and write?Attestation contextWhich frameworks does your review name,and what scope does each one carry?Your questionnaire, answered line by lineDoes the questionnaire you already usecome back answered, in your format?How it is deployedHow it is provedDeployment architecture diagramDoes call data leave your perimeter,or stay in the one region you name?Data-flow inventoryDoes everything a call producesstay on your side of the boundary?Redaction policyIs a card number in a transcript,or masked before one is written?Model inventoryDoes a vendor's model hear the call,or does every model run inside?Guarded-execution methodCan an agent act without authority,or is policy checked before it runs?Redacted trace exportCan you prove what happened,on every turn, action and write?Attestation contextWhich frameworks does your review name,and what scope does each one carry?Your questionnaire, answered line by lineDoes the questionnaire you already usecome back answered, in your format?How it is deployedHow it is provedDeployment architecture diagramDoes call data leave your perimeter,or stay in the one region you name?Data-flow inventoryDoes everything a call producesstay on your side of the boundary?Redaction policyIs a card number in a transcript,or masked before one is written?Model inventoryDoes a vendor's model hear the call,or does every model run inside?Guarded-execution methodCan an agent act without authority,or is policy checked before it runs?Redacted trace exportCan you prove what happened,on every turn, action and write?Attestation contextWhich frameworks does your review name,and what scope does each one carry?Your questionnaire, answered line by lineDoes the questionnaire you already usecome back answered, in your format?
Closing05 / 05

Bring one call type. Leave with an architecture.

A ring of three segments, blue, sage and sand, on a stand inside a drawn perimeter; a cloud and a server rack wait at docks outside it.
Security

One perimeter, drawn where your data lives

A working session with an engineer who has deployed inside a bank’s perimeter. We map your telephony, data boundary and handoff rules, and tell you what we would not automate.

Book a Demo