Data Controls

Content you do not keep is not retained. Anything we keep for you is encrypted history we cannot read. The controls below let you decide what is kept, and where.

History has three modes. Cloud sync, the default, saves your encrypted history and syncs it across the devices you sign in to. Manual keeps history on your device and uploads only the entries you choose. Off keeps everything local: the server rejects cloud history writes, so nothing reaches the cloud.

You can switch modes at any time in Settings, and whatever is stored is always encrypted on your device before it leaves.

New history entries, documents, and saved audio are encrypted on your device before upload and stored as ciphertext we cannot read. Messaging is end-to-end encrypted between participants.

Messages are end-to-end encrypted and we store only ciphertext.

There are exactly two exceptions, and both require you to use the feature:

• Group polls. The server has to read a poll to tally votes and show results, so polls are not end-to-end encrypted. They are disabled in healthcare conversations.
• Voice-message translation. Translating a voice message requires decrypting that one message on our servers. We ask for your consent first, record the consent, and audit the access. It never happens unless you choose it.

Live call and conference translation is processed for the session and is not stored as history unless you record or save it. Recordings follow your history sync setting.

The Vavus Keyboard has its own history control with off, on-device, and cloud modes. Off stores nothing. On-device keeps history on that device only. Cloud mirrors encrypted history to your account for cross-device access.

To produce a result, your content is processed by third-party speech, translation, and AI services. We configure these to keep your content out of their model training and to minimize retention, wherever the service supports it. Those services receive only the content needed to produce your result - never your name, account, or identity. Payment and app-store providers necessarily do receive identifying and transaction data.

You can export your data, delete individual entries or your whole history, manage active sessions and security settings, and delete your account. Website cookie consent is managed from the Cookie Policy page, and we honor the Global Privacy Control signal sent by your browser.

Healthcare accounts run under an executed Business Associate Agreement with stricter session, audit, and PHI controls, and use only BAA-covered services. These protections apply only to accounts approved for healthcare use under a signed BAA.

Enterprise customers can request organization policy review, SSO, regional or dedicated managed cloud deployment, and on-premises options. HIPAA audit logs hold metadata only and are retained for six years.

Set History to Off in Settings. With sync off, the server rejects cloud history writes, so nothing new leaves your device. You can also choose Manual to upload only the entries you pick.

Yes. Messages are end-to-end encrypted and we store only ciphertext. There are exactly two exceptions: group polls, because the server has to read them to tally votes; and voice messages you choose to have translated, because translating one requires decrypting it on our servers - we ask for your consent first and audit the action. Neither applies unless you use that feature.

Yes. You can export your data, delete individual history entries or your whole history, manage your security settings, and delete your account from the product controls.

Speech, translation, and AI providers receive only the content needed to produce your result - never your name, account, or identity - and are configured to keep your content out of their model training and to minimize retention where supported. Payment and app-store providers necessarily receive identifying and transaction data.