Privacy Mode & Data Retention

Zero data retention or encrypted history. Once Vavus has processed what you said or typed, the result follows one of two paths: it is not retained at all, or it is kept as encrypted history that we cannot read. There is no third path where Vavus holds your translation content in readable form, and we never use your content to train AI models.

To translate or transcribe your speech and text, Vavus and the speech, translation, and AI services that power the result have to process it. That processing is unavoidable - it is how the feature works.

Retention is a separate question: what happens after the result is produced. The controls described here are about retention, not about pretending cloud processing never happens.

When something becomes part of your history - a saved translation, a transcript, a recording, or an AI conversation - it is encrypted on your device before it leaves it and stored in your account as ciphertext Vavus cannot decrypt. Documents and saved audio are encrypted the same way, and messages are end-to-end encrypted between participants.

By default, your encrypted history syncs across the devices you sign in to, so your work follows you. You can change that any time - see Data Controls.

One point worth being precise about: when you ask Vavus to re-transcribe or re-translate a saved recording, your app supplies the key so that recording can be processed for that request. Vavus cannot read your stored content on its own - only when you ask it to act on it.

Content you do not keep is not stored as history. Live conversation translation, dictation you do not save, and AI turns you discard are processed to produce your result and then dropped. If you set History to Off, cloud history writes are rejected at the server, so nothing new leaves your device.

Vavus never sells your data and never uses your content to train its models.

Your content is processed by Vavus and by third-party speech, translation, and AI services solely to produce your result. We configure these services to keep your content out of their model training and to minimize what they retain, wherever the service supports it.

These services receive only the content needed to produce your result - never your name, account, or identity. Vavus makes the calls on your behalf, so a provider cannot link a request back to you.

Running an account requires records that are not your translation content: account and authentication details, billing and subscription history, security and abuse-prevention logs, support conversations, and - where the law requires it - audit and compliance metadata.

Saved files, documents, generated images, messages, and projects are retained when you use those features, until you delete them or close your account. Healthcare audit logs are metadata only - they never contain PHI or translation content.

Healthcare accounts operate under a signed Business Associate Agreement, with stricter session limits, audit logging, and PHI-handling controls, and use only services covered by a BAA. Features that cannot be end-to-end encrypted, such as group polls, are disabled in healthcare conversations.

Enterprise customers can request organization-level review of history, storage, data residency, dedicated managed cloud deployment, or on-premises deployment.

You can delete individual history entries or your whole history, switch sync off, export your data, or delete your account from the product controls. Billing records, fraud-prevention logs, and required audit and compliance records may be retained where law or a signed agreement requires.

Live translation, dictation, and AI content is processed to produce your result and is not kept as cloud history unless you save or sync it. Anything you do keep is stored only as encrypted history that Vavus cannot read.

Everything follows one of two paths: content you do not keep is not retained at all, and content you keep is stored only as history that is encrypted on your device before it reaches us. There is no third path where Vavus holds your translation content in readable form.

No. Vavus never uses your content to train its own models, and the third-party speech, translation, and AI services it uses are configured to exclude your content from training theirs and to minimize retention where supported.

No. Saved history is encrypted on your device, so the server stores only ciphertext. The one exception is when you ask Vavus to re-transcribe or re-translate a saved recording - then your app supplies the key so that recording can be processed for that request.