the quiet parts
Blanc’s privacy is structural: what the browser blocks, what it refuses to run, and how it handles the data you care about.
what runs, and what does not
Ad and tracker blocking runs inside the browser, not as an extension — so it is not subject to an extension store’s rules or Manifest V3’s limits. The shield on the Island shows what was blocked on each page. How blocking works.
Web pages run inside Chromium’s sandbox, isolated from the browser and from your files. Blanc’s own pages — settings, history, favorites — live on a privileged internal scheme that ordinary web content cannot link into, and the browser re-checks who is calling on every internal request.
Extensions are privileged third-party code running inside your browser. Blanc removed the runtime entirely, which removes that class of risk outright — and a common reason to install one, ad blocking, is already built in at a deeper layer. If you need a specific extension, we are honest about it: Blanc is not your browser today.
the sensitive parts
Sync is off by default. When you turn it on, favorites and settings are encrypted on your device with a key derived from your passphrase; the server stores ciphertext it cannot read, index, or merge. The passphrase is never stored and never sent.
On a Mac with Touch ID, Blanc creates device-bound passkeys inside Apple’s Secure Enclave. The private key never leaves the chip, and Blanc is signed with an Apple-issued Developer ID and provisioned to hold its own keychain access group. macOS only for now.
Camera, microphone, location, notifications — each request raises a Blanc prompt, and each decision is remembered for that site. Decisions made in a private tab are never written to disk.
When the packaged app launches, it sends a small pseudonymous usage ping; the privacy policy lists every field. None of them include browsing data, and the random install ID identifies the installation, not you. Settings turns it off with one switch.
ready when you are
