Assistant and cloud data

High-level map of what leaves your device when you use Oasis versus what stays in your local browser profile.

What this is

Cloud (Kahana-operated services): chat prompts and model completions, voice audio for transcription, training submissions when you explicitly submit feedback on a reply (anonymous or personalized), and limited usage/telemetry when enabled.

On-device (your Oasis profile): imported and native bookmarks, browsing history, saved passwords (encrypted login vault), autofill data, IndexedDB chat threads, optional on-device embeddings, and local training-gallery progress.

Password vault vs assistant

Your saved-password vault is on-device only and encrypted at rest in the profile. Importing passwords from another browser copies them into that local vault—it does not upload them to Kahana.

The trainable assistant does not receive vault contents in documented interaction payloads. It processes what you send in chat (and limited tab context). Training is a separate voluntary upload on Submit—anonymous means no user ID on the training record, not on-device-only storage. See Training — does data leave the device?. Do not paste passwords into the assistant or training comments. Full boundary table: Import data — assistant boundary.

How to use it

• Assume cloud processing for signed-in assistant chat unless an in-product banner says otherwise.
• Voice audio is transmitted for transcription; do not dictate highly sensitive secrets.
• Clear browsing data to remove local IndexedDB threads; manage logins in the password manager UI.

Notes and limits

Exact data practices evolve; trust the privacy policy and interaction data breakdown over this summary.

Related topics

• Import Data From Other Browsers
• How Oasis Collects Interaction Data
• On-device Embeddings
• Chat History Indexeddb
• Training And Bonus Tokens