Questions that come up.

Real-time, two-way speech translation on a live phone call. Your agent speaks; the customer hears it in their own language, sub-second latency, on the same call leg — no third human on the line. Both sides understand each other directly.

The pipeline (STT → translate → TTS) runs at the SIP boundary. See How It Works for the full anatomy of a call.

A human interpreter is one scheduled person, one call at a time, at roughly $2–4/min — and you wait on availability. TransVoix is real-time and always-on across every call and language pair, in each speaker's own voice, at roughly 1/3 to 1/5 that cost.

It's built for the full range of conversations — not a low-stakes carve-out. Teams that still want a human in the loop for a specific moment can keep one, but that's their choice, not a platform limit. See Pricing.

Audio is intercepted at your SIP boundary, processed in our US region, and returned to the call leg. No audio leaves the US. The audio path itself is stateless — frames are processed in memory and discarded.

The full subprocessor path (which vendors touch audio vs. metadata only) is documented on Compliance.

Inbound and outbound today. Multi-party / conference is on the roadmap and works in pilot deployments today with a single target language. If you need it, mention it during your discovery call.

Six languages live in production today — English, Spanish, French, Mandarin, Arabic, Hindi — for 30 bidirectional pairs. Tagalog, Vietnamese, Korean, and Portuguese are in beta. New languages ship on a published roadmap.

The full matrix — quality and speaker-count notes per language — lives on Languages.

An LLM-judge benchmark across the 30 production language pairs — average 4.72/5, scored 1–5. The methodology and the per-pair scores are on Languages.

Yes. Voice cloning, recording, and biometric capture all require fresh affirmative consent each session — never carried over from a stored preference. Consumer voice profiles are deleted on call end or consent revocation, whichever comes first; per-pilot agent voices are retained per the pilot agreement and are never reused across tenants.

The consent and provenance posture is detailed on Compliance.

Translation routes to dialect-aware variants where it matters (e.g. MX vs. ES Spanish, Brazilian vs. European Portuguese, Mandarin vs. Cantonese). Code-switching mid-utterance is detected at the phrase level and translated in place.

By default the audio path is stateless — frames are processed in memory and discarded, not written to disk. Recording is opt-in per tenant; when enabled, recordings are encrypted (AES-256) with per-call signed URLs that expire in 7 days.

The full retention matrix is on Compliance.

No. Customer call content is never used to train models. It's a hard line — verified by data-egress tests in CI, not just a policy doc. See the “Lines we don't cross” block on Compliance.

Sensitive tables (call recordings, consent audit, call turns) enforce service-role-only Row-Level Security, scoped to the originating tenant. The anonymous database key cannot read or write protected content — verified by a curl probe after every migration.

Consent and access events are written to an append-only audit trail — every grant, revoke, and expiry is a separate row, no UPDATE, no DELETE — so the state of access at any past moment is provable.

TLS 1.2+ on every endpoint, with WebSocket audio frames carried over WSS. AES-256 at rest; recordings encrypted with per-call signed URLs (7-day expiry). Provider API keys are stored as encrypted platform secrets — never committed to source, never logged.

Encryption and key-management posture is on the Compliance page.

We sign BAAs and operate under HIPAA-aligned controls — encryption, access logging, breach notification, minimum-necessary data handling. BAAs are executed at pilot onboarding for healthcare tenants, before any production traffic flows; subprocessor BAAs are executed (or pre-signed) before that vendor sees any session tagged with a HIPAA compliance profile.

We don't claim “HIPAA certified.” The full posture is on Compliance.

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.

The report and pen-test summary are available under NDA — request via the receipts list on Compliance.

Yes to both. The BAA is executed at pilot onboarding for healthcare tenants. The DPA covers GDPR-scoped customers; custom redlines are accepted on Enterprise. Email security@transvoix.ai.

By default, US data processing for every tenant. EU residency is available as an Enterprise-tier contractual term. Other regions are on the roadmap — if you have a non-US deployment requirement, raise it during discovery.

Call metadata (timestamps, duration, language pair, agent ID, tenant ID, error codes) for billing and debugging. Recording is opt-in per tenant. Voice-profile embeddings for any enrolled agents.

We do not keep transcripts, translation outputs, or user PII unless explicitly contracted into a retention plan.

Yes — per-tenant deletion controls, with the deletion event captured in the append-only audit trail. Full-tenant export and purge on contract termination is documented in the DPA.

Advance notice goes to your primary security contact before a new subprocessor that touches audio or PHI. The current named-vendor subprocessor list is available under NDA via the receipts list on Compliance.

On contract termination there's a contractual export window, then a purge across primary, replicas, and backups. The exact mechanics and timelines are in the standard DPA.

SIP-native architecture. Live today on Amazon Connect; designed to integrate with Genesys, Five9, NICE CXone, and other SIP-capable contact centers per customer engagement.

Provisioning timing scales with the agreed-upon scope and size of the pilot. We need SIP credentials, one disclosure script, and a list of pilot agents.

The pilot is free — no fee, no credit card, no commitment. See Pricing.

A REST + WebSocket API for session control, agent enrollment, and audit-pack retrieval. No client SDK is required for the standard SIP deployment; the SDK/SIP surface expands on a published roadmap.

The audio segment on your agent's side of the call — distinct from the customer leg. Billing is metered on audio processed end-to-end on the agent leg only; idle time and silence over 500ms aren't billed.