Explainer · Privacy
Why Incognito is not enough: zero-trust sandbox browsers explained
Incognito is a temporary session. Zero-trust Spaces keep long-lived logins isolated—with optional per-Space encryption.
What Incognito solves—and what it does not
Private tabs leave fewer local traces when closed, but they do not keep multiple long-lived logins, and they are not network anonymity. A sandbox browser turns identity isolation into switchable Spaces.
Under the hood: WebKit data stores
On iOS, XBrowser Spaces map to separate WebKit website data stores—
WKWebsiteDataStore(forIdentifier:)—so each Space gets its own cookies, cache, and local storage.
Incognito-style private browsing typically uses a non-persistent store that is thrown away when you leave.
Spaces keep those stores around: you stay signed in to account A and account B at the same time, without one session overwriting the other.
That difference matters for dual WhatsApp Web, two Gmail inboxes, or shop admin panels. Incognito is built to forget. Spaces are built to remember each identity separately.
Zero-trust mindset
Assume accounts should not share cookies. Isolate storage per Space, then add Face ID to sensitive ones for defense in depth.
Encryption & privacy · Spaces technical FAQ
FAQ
Is Incognito “more private” than a Space?
For a throwaway visit, temporary private mode can leave fewer local traces after you close it. For multi-account work, Spaces are usually the better fit: persistent isolation without constant logout, plus optional Space Lock. Neither mode hides your IP.
Do Spaces share cookies across tabs?
Tabs inside the same Space share that Space’s data store (normal browser behavior). Different Spaces do not share cookies. Isolation is per Space, not per tab inside one Space.
Try Spaces in XBrowser
Zero-trust Spaces and isolated multi-account sandboxes—in one browser.