Skip to main content
Compliance · a working document

The careful version
of "we take security seriously."

No badges we haven't earned. No "bank-grade" prose. The architecture below is the argument — followed by the full vendor posture, the three-rail data flow, retention windows, incident-response tiers, and the audit-pack receipts.

Where we stand
SOC 2 Type I
Type I program · auditor in observation
HIPAA
HIPAA-eligible · BAA executed at pilot onboarding
ISO 27001
ISMS framework alignment
GDPR + BIPA
EU and Illinois posture
US data processing
Default region for every tenant
Two-party consent
IL · CA · FL · MA · MD · MT · NV · NH · PA · WA
The audio path

Three steps. One direction.

Audio enters as voice and exits as voice. In between: speech-to-text, translation, text-to-speech. Frames are processed in memory and discarded — the path is stateless.

The audio path
Three steps. One direction. Audio in, audio out.
audio in  →  audio out
never persisted in transit
Caller
any source
STT
Speech → Text
TRANSLATE
Translate
TTS
Text → Speech
Recipient
any sink
The vendor posture

Read by group.

Every vendor that touches a session, by function and flow group. The reading notes explain what each group sees — and what it doesn't. The named subprocessor list is available to your security team under NDA (see Receipts).

Audio path
Vendors on the audio path carry call audio in flight. Frames are processed in memory and discarded — no persistent storage at any audio-path vendor.
Infrastructure
Hosting, DNS, and database. These vendors hold encrypted state at rest (recordings, transcripts, consent records) and the keys to access it.
Observability
Error tracking and product analytics. Configured to drop PHI fields before transmission. No call audio, no transcripts, no PII payloads.
Operations
Email and payments. Never see call content. Listed for completeness so procurement can reconcile every line item on an invoice.
FunctionRoleBAADPASOC 2Region
Speech-to-text Audio path · transcription Under NDA Under NDA Yes US
Translation Audio path · LLM inference (+ fallback) Under NDA Under NDA Yes US
Text-to-speech Audio path · synthesis + voice cloning Under NDA Under NDA Yes US
Infrastructure Hosting · database · DNS · CDN Under NDA Under NDA Yes US (EU on Enterprise)
Observability Error tracking · product analytics (no PHI) Under NDA Under NDA Yes US
Operations Transactional email · payments (no call content) N/A — no call content Under NDA Yes US
The commitments

Made in code. Not in policy.

Compliance documents describe what should happen. These are the controls that make it actually happen — enforced where it's hard to bypass.

Append-only consent audit trail
Every consent decision (grant, revoke, expire) writes a new row. No UPDATE, no DELETE. Revocations supersede via reference, never overwrite — preserves audit integrity for BIPA, HIPAA, and state two-party-consent jurisdictions.
01 / 09
Service-role-only database access
Sensitive tables (call recordings, consent audit, call turns) enforce service-role-only Row-Level Security. The anonymous database key cannot read or write protected content — verified by curl probe after every migration.
02 / 09
Per-session affirmative consent
Voice cloning, recording, and biometric capture require fresh affirmative consent each session. Persisted preferences are never carried over for consent decisions — only for ergonomic defaults like language and theme.
03 / 09
Provider-abstracted ingress adapter
Every audio source (browser, telephony platform, SIP, AI agent) flows through a single canonical adapter that emits PCM16 mono 16kHz. Compliance attestations and subprocessor chains live with the adapter, not scattered through the pipeline.
04 / 09
Compliance-profile-aware provider selection
Provider eligibility is filtered at runtime against the session compliance profile, not at deployment time. A HIPAA-profile session cannot fall back to a non-BAA provider — enforced in code, not just policy.
05 / 09
Speaker-identity binding across the language boundary
Voice cloning preserves each speaker's acoustic signature into the translated output. Original AI translations are immutable; agent corrections append, never overwrite — so the record of what each speaker actually said survives translation, correction, and replay.
06 / 09
Content provenance on synthesized output
Every translated utterance ships with a C2PA-signed manifest binding it to the speaker, source audio hash, model version, and timestamp — a cryptographic record of who said what, in what language, signed by the platform that produced it.
07 / 09
Tenant-scoped terminology control
Glossary entries (locked translations, pronunciations, dialect variants) are scoped per tenant via Row-Level Security, versioned, and audit-logged. Entries are managed by TransVoix on each tenant's behalf today; term overrides take precedence over model output and never cross tenant boundaries. The audit trail captures who edited which entry, when, and which version was active for a given call.
08 / 09
Per-zone PII redaction policy
Compliance zones drive redaction rules per tenant. Healthcare zones are designed to redact identifiers like SSN, DOB, and MRN before persistence; other zones apply narrower rules per tenant configuration. Policy is configured per tenant and applied before data leaves the zone it was captured in.
09 / 09
Where audio goes · where it stops

In-flight. Persistent. Excluded.

The audio path is short and stateless. The persistent rail is small and encrypted. The excluded rail is the lines we don't cross.

In-flight
Transient
AUDIO Voice frames over WSS. Not stored. In-memory only for the duration of the call.
TRANSCRIPT Streamed to client; persisted only if recording enabled per tenant.
CLONES Speaker embeddings generated per call, deleted on call end (consumer profile).
If you cut the call, the audio is gone. There is no offline copy to subpoena.
Persistent
Stored, encrypted
CALL META 3 years; PII anonymized after 12 months.
RECORDINGS 30 days default; per-tenant configurable.
CONSENT 6 years (legal); append-only, never overwritten.
AGENT VOICE Retained per pilot agreement; never reused across tenants.
Encryption at rest is AES-256. Service-role-only access; the anonymous key cannot read these tables.
Excluded
Never leaves
TRAINING Customer call audio is never used to train models. Period.
EMAIL Transactional email content never contains call content or PHI.
PAYMENTS The payment processor never sees PHI. Payment flows are isolated from call data.
ANALYTICS Analytics and error tracking receive no call content. PHI scrubbed pre-emit.
Lines we don't cross. Verified by data-egress tests in CI, not just policy docs.
Stewardship

How it's protected. How long it lives.

Encryption
In transit
TLS 1.2+ on every endpoint. WebSocket audio frames carried over WSS.
At rest
Encrypted storage (AES-256). Recordings encrypted with per-call signed URLs (7-day expiry).
Database
Service-role-only access for sensitive tables. The anonymous key has no read/write privilege on call content.
Secrets
Provider API keys stored as encrypted platform secrets, never committed to source, never logged.
Retention
Voice audio (during calls)
Not stored. In-memory only.
Voice clones
Deleted on consent revocation or call end (consumer); per-pilot agent voices retained per pilot agreement.
Call recordings
30 days default. Configurable per-tenant for B2B contracts.
Call metadata
3 years; PII anonymized after 12 months.
Consent records
6 years (legal requirement; append-only).
Incident response

Severity. Then response time.

P1 — Critical
Active breach or data loss. Target: initial response within 1 hour.
P2 — High
Service unavailable or sensitive-data exposure risk. Target: within 4 hours.
P3 — Moderate
Degraded service, single-tenant impact. Target: within 1 business day.
P4 — Low
Tracked for remediation in normal sprint cadence.
Procurement asks

The questions that come up.

01 You say "SOC 2 Type I program" — what does that actually mean today? +
We're partway through a Type I audit with a recognized firm. The controls are designed and operating; the auditor's observation period is in progress. We'll publish the report (and start a Type II observation) the moment it's signed. We don't claim "SOC 2 certified" because we're not, yet.
02 Is there a BAA available for HIPAA-covered traffic? +
Yes. BAAs are executed at pilot onboarding for healthcare tenants, before any production traffic flows. Subprocessor BAAs are executed (or pre-signed) before the corresponding vendor sees any session tagged with a HIPAA compliance profile.
03 Where does call audio physically live? +
By default, US data processing for every tenant. EU residency is available as an Enterprise-tier contractual term. The audio path itself is stateless — frames are processed in memory and discarded.
04 Can a HIPAA session fall back to a non-BAA provider if the primary fails? +
No. Provider eligibility is filtered at runtime against the session's compliance profile. If the only available fallback is non-BAA, the session degrades (or fails) rather than silently routing through an ineligible vendor. Enforced in code, not policy.
05 What happens to a voice clone after the call ends? +
Consumer profiles: the clone is deleted on call end or on consent revocation, whichever comes first. Per-pilot agent voices are retained per the pilot agreement and are never reused across tenants. Voice cloning, recording, and biometric capture all require fresh affirmative consent each session.
06 How do you handle Illinois (BIPA) and other state-specific consent regimes? +
The append-only consent audit trail captures every grant, revoke, and expiry as a separate row — no UPDATE, no DELETE — so you can prove the state of consent at any past moment, in any jurisdiction. BIPA, two-party consent, and GDPR Article 7 records all use the same primitive.
Receipts

What you can ask for.

Audit packs go out one-to-one, scoped to the asking team. Each request lands at security@transvoix.ai with a subject line we can route.

Full subprocessor list
Named vendor list available under NDA
Request →
SOC 2 Type I report
Available on request after audit signoff
Request →
Pen test summary
Available on request under NDA
Request →
SBOM (Software Bill of Materials)
Available on request for Business-tier customers
Request →
BAA template
Available pre-pilot for healthcare tenants
Request →
Vulnerability disclosure
Responsible disclosure welcomed; no monetary bounty today; valid findings get recognition here as the program matures. Policy + contact also at /.well-known/security.txt (RFC 9116).
Disclose →
The address

security@transvoix.ai

Audit packs, pen tests, BAA negotiation, vulnerability disclosure. A real engineer reads it. We aim to acknowledge within one business day.