TTS
When enabled, all customer text inputs sent to our text-to-speech engine are processed in memory to generate audio. Once complete, both the text and the generated audio are immediately redacted from our logging systems. This applies to all text sent for speech synthesis, including requests using cloned voices.| Product | Type | Eligible for Zero Data Retention? |
|---|---|---|
| Text-to-Speech | Text Input | Yes |
| Text-to-Speech | Audio Output | Yes |
| Voice Cloning | Audio Samples | No |
| Voice Design | Voice Description/Script | No |
STT
When a request is processed, customer audio is sent to the selected provider and transcribed in memory. Once complete, both the original audio and the transcription output are immediately redacted from our logging systems. This applies to requests, both sync (file upload) and WebSocket (streaming), processed through the Inworld STT API. Each upstream provider maintains its own guarantees, which can be mode-specific, so see the per-provider details below.| Data | Type | Eligible for Zero Data Retention? |
|---|---|---|
| Audio Input | Customer-submitted audio (file or stream) | Yes |
| Transcription Output | Transcribed text returned by the API | Yes |
| Usage Metadata | Request duration, model ID, timestamps | No (retained for billing) |
| Provider | Models | Details |
|---|---|---|
| Inworld | inworld/inworld-stt-1 | Processed in memory; redacted from logs after completion |
| AssemblyAI | assemblyai/* | ZDR enabled for streaming (AssemblyAI docs) |
| Groq | groq/whisper-large-v3 | No customer inputs or outputs retained by default (Groq docs) |
| Soniox | soniox/stt-rt-v4, soniox/stt-rt-v5 | Processed in memory; redacted from logs after completion (Soniox docs) |
| Deepgram | deepgram/flux-general-en, deepgram/flux-general-multi | No customer audio retained by default (Deepgram docs) |
LLM Router
Zero Data Retention is currently available only for Inworld hosted LLM models. Requests routed to third-party model providers are not covered.
| Product | Type | Eligible for Zero Data Retention? |
|---|---|---|
| Inworld hosted LLM | Prompt / Input messages | Yes |
| Inworld hosted LLM | Model output / Completion | Yes |
| Third-party model providers | Prompt & Output | No |
Enterprise-level security
Inworld’s platform is SOC 2 Type II certified and HIPAA and GDPR compliant. For full details on our security posture, certifications, and data handling practices, see our Security page.Workspace Configuration
Zero Data Retention is configured at the workspace level, allowing customers with strict data privacy requirements to maintain compliance.
Production Scale
Whether you’re handling protected health information or sensitive financial data, you get the security guarantees needed for production deployment at scale.
FAQs
Can we enable Zero Data Retention for only specific workspaces?
Can we enable Zero Data Retention for only specific workspaces?
Yes. Zero Data Retention is configured per workspace. Contact our sales team to enable it for specific workspaces.
How does Zero Data Retention affect debugging?
How does Zero Data Retention affect debugging?
With Zero Data Retention enabled, original inputs and outputs cannot be retrieved. Debugging and troubleshooting capabilities are limited to non-sensitive metadata only.
How does Inworld TTS Zero Data Retention work?
How does Inworld TTS Zero Data Retention work?
TTS Zero Data Retention protects privacy by redacting all input texts from logs, including text sent to Cloned Voices, while only retaining the initial source audio required to build the voice itself. This is currently a workspace-level configuration managed by the Inworld Engineering team.
Does TTS Zero Data Retention affect audio output quality?
Does TTS Zero Data Retention affect audio output quality?
No. The TTS engine still receives the text to generate the audio. The redaction happens only at the logging layer, ensuring the record of what was said is not saved.
How does Inworld STT Zero Data Retention work?
How does Inworld STT Zero Data Retention work?
STT Zero Data Retention protects privacy by redacting all customer audio and transcription outputs from logs immediately after processing. Only non-sensitive usage metadata (request duration, model ID, timestamps) is retained for billing and service monitoring.
Does Zero Data Retention apply to all STT models?
Does Zero Data Retention apply to all STT models?
Yes. All models available through the Inworld STT API operate under Zero Data Retention. Each upstream provider’s specific guarantees are listed in the supported models table above.
Is my audio used for model training?
Is my audio used for model training?
No. Audio processed through the Inworld STT API is never used for training by Inworld or any upstream provider.
Does STT Zero Data Retention affect transcription quality?
Does STT Zero Data Retention affect transcription quality?
No. The STT engine still receives the audio to generate the transcript. The redaction happens only at the logging layer, ensuring no record of the audio or transcript is saved.
How does Inworld LLM Zero Data Retention work?
How does Inworld LLM Zero Data Retention work?
LLM Zero Data Retention protects privacy by never writing prompts or model outputs to our logs. It is currently available for Inworld hosted LLM models, and is a workspace-level configuration managed by the Inworld Engineering team.
Which LLM models support Zero Data Retention?
Which LLM models support Zero Data Retention?
Zero Data Retention is currently available only for Inworld hosted LLM models. Requests routed to third-party model providers are not covered.
Does LLM Zero Data Retention affect output quality?
Does LLM Zero Data Retention affect output quality?
No. The model still receives the full prompt to generate its response. Zero Data Retention applies only at the logging layer: the prompt and output are never written there, so no record of the conversation is saved.