v0.1.27811 Sep 2026·Rendering, Networking, Privacy & Shields, Tabs & interface

A tracker can no longer follow you from one site to the next

The biggest anti-tracking upgrade yet, and the truest expression of the idea that your memory is yours. A company that follows you around the web by quietly embedding itself on the sites you visit can no longer recognize you from one site to the next. Anything such a third party stores on your device is now kept in a separate box for each site you were actually on, so those visits cannot be joined into one profile - the same cross-site tracking that third-party cookies were banned for, closed here too and for storage as well. Your own sites keep their data exactly as before; nothing you rely on moves. This release also enforces a site's security policy when it arrives as a response header, not only when it is written into the page, so a script the site itself forbids can no longer slip in. Everything is decided and kept on your device. The security architecture aspect moves 53 to 56; the overall platform score stays at 70.

Parity with the reference browser

74overall, as of v0.1.343

Web APIs / DOM surface42

Security architecture66

GPU / graphics acceleration68

DevTools / extensions72

Networking85

Media85

Accessibility85

Real-world site compatibility99

HTML parsing100

CSS parsing + selectors100

Layout: block / flex / grid / tables / writing-modes100

Paint + visual100

JavaScript language100

JavaScript performance (JIT)100

HTML parsing100

What changed 3 changes

Networking	A third party cannot join you across sites. When a page embeds something from another company, whatever that embed stores on your device is now filed under the site you are actually visiting, not under the embedder alone. So the same tracker on two different sites gets two separate, empty boxes and cannot tell that the two visits are the same person - the cross-site profiling that third-party cookies were killed for, now closed for on-device storage as well.
Tabs & interface	Your own sites are untouched. A site's own saved data keeps its normal place, so logins, drafts and settings you rely on carry over exactly as before. Only a third party embedded across different sites is boxed apart, which is precisely the case that enables tracking.
Rendering	A site's security policy is enforced from its headers, not just its markup. When a site states, in its response, which scripts it is willing to run, that instruction is now honored - so a script the site itself forbids cannot slip in through an injected tag. The refusal is shown to you in the same honest list of what was blocked.