Import data from other browsers

When you switch to Oasis, you can bring bookmarks, passwords, history, extensions, and autofill from another browser. This page explains the import flow and—if you care about password safety when moving browsers—where imported data lives and what the assistant can see.

What you can import

The import flow can pull typical browser profile data from installed browsers (for example Chrome, Edge, Safari, or Brave) or from profile files on disk:

• Bookmarks
• Passwords (saved logins)
• Browsing history
• Extensions (where supported)
• Autofill (addresses, cards, and related form data)

Exact availability depends on the source browser and platform. The other browser should be installed or its profile data readable when you run import.

How to run import

• Onboarding: The assistant checklist can guide you through import when you first set up Oasis. See Onboarding checklist.
• Later: Open Settings and use Import browser data (migration) if you skipped import earlier. See Import opt-out if you chose to skip on first run.

Where imported data lives: on-device vs cloud

Oasis is built on Firefox core browser technology. Imported profile data stays on your device in your Oasis profile unless you separately use a cloud feature (for example Kahana account sign-in for sync or assistant chat).

Imported passwords: storage and encryption

If you choose to import passwords, they are written into Oasis’s built-in login manager for your profile—the same class of storage Firefox uses for saved logins, not a Kahana cloud password database.

• On-device only: Import copies credentials from the source browser into your local Oasis profile. Kahana does not receive your password vault as part of the import step.
• Encrypted at rest: Saved logins are stored in the profile’s login database and protected with the browser’s NSS-based encryption (profile key material such as key4.db together with login records). On macOS and Windows, access to reveal or autofill passwords is additionally gated by the OS (for example Touch ID, Windows Hello, or a primary password if you set one).
• Autofill vs vault: When you sign in on a site, Oasis may offer to fill a saved password locally in the page. That is separate from sending your vault to the assistant.

For breach monitoring on saved logins, see Password breach alerts. For addresses and payment autofill (distinct from the login vault), see Autofill.

Is the password vault walled off from the trainable assistant?

Yes, by design. The assistant and Kahana interaction telemetry are not a general-purpose export of your browser profile. They do not include your saved-password vault contents.

• Assistant cloud processing: Chat prompts and model replies are processed by cloud services to run the assistant. Kahana’s documented interaction payloads include fields such as prompt text, response text, and limited tab context (for example active tab URL/title)—not a dump of stored logins. See the payload explorer on How Oasis collects interaction data.
• Training submissions: If you submit training feedback on a reply, you send the prompt and reply text you choose to rate (and related training fields). That flow does not attach your password vault. Do not paste passwords into the assistant or training comment fields. See Training and bonus tokens.
• What you control: Anything you type or paste into the assistant composer may be sent to the cloud model like any other prompt. Keep credentials out of chat.

Notes and limits

• Some extensions or login formats may not transfer perfectly; retry import or add critical logins manually if needed.
• Import does not replace backing up your machine or using a dedicated password manager if your threat model requires it.
• Clearing Oasis profile data removes imported items stored in that profile.

Related topics

• Onboarding Checklist Assistant Panel
• Import Opt Out
• Assistant And Cloud Data
• How Oasis Collects Interaction Data
• Manage Oasis Browser Profiles