Adam Kershner

Tracking protection is one of the main reasons people pick a Firefox-based browser. Oasis ships Enhanced Tracking Protection on by default.

Insight for other users: ETP blocks known trackers that follow you across the web: social buttons, cross-site scripts, fingerprinting, cryptomining, and many third-party analytics. It is not a full ad blocker. It targets tracking-related content while trying to keep core site features working.

What you get:

• Privacy: Less cross-site profiling and fewer third-party trackers loading in the background.

• Speed: Fewer tracking scripts can mean faster page loads and less wasted bandwidth.

• Control: Pick a protection level and add site exceptions when a trusted site breaks.

Long chats break when the model forgets what you said ten turns ago. Oasis uses optional structured session memory (internal nickname  Railroad ) to help follow-ups stay coherent.

Insight for other users: Session memory extracts structured facts across turns and re-injects them into later prompts so the assistant can remember details within your session and plan limits. You do not edit memory by hand. It updates as you chat.

What it is not: Memory is not a full backup of web pages. It is distilled text used to steer replies, not a copy of everything you browsed.

How to work with it:

Hey Product Hunt community

We ve been getting great questions from early testers and people considering Oasis as their daily browser. One keeps coming up after every iteration, and it s exactly the right question to ask:

You talk about history, bookmarks, and semantic search staying on-device while the assistant runs on cloud models. When onboarding says I can pull passwords over from my old browser where do those actually land? How are they encrypted? And is the vault fully walled off from anything that could train or power the assistant? @ferdi_sigona