What Bonce stores

Your header sets — names, values, domain patterns, and enabled/disabled states — are stored only in Chrome's local extension storage (chrome.storage.local) on your own machine, under the headerSets key. Bonce never sends your configuration to us or to any service of its own.

Where your headers go

When a header set is on, Bonce adds its enabled headers to every request to a host that matches one of its domain patterns, including page loads and requests for images, scripts, and data. Patterns are checked against where a request is going, not the page you're on: a matched site's requests to other servers, such as analytics or CDNs, don't get your headers, but requests from any site to a matched host do. A *. pattern covers every subdomain. If a request already carries a header with the same name, Bonce replaces its value.

What Bonce doesn't do

No accounts, no cloud sync, no analytics, no ads, no tracking. Bonce makes no network calls of its own — it only changes the headers on requests your browser is already making. Bonce does not read page content, browsing history, or response bodies, and never transmits your configuration off-device.

Why Bonce needs broad permissions

Bonce lets you define custom domain patterns — specific hosts, wildcarded subdomains, or host:port combinations — and apply your own configured request headers to requests matching those patterns. Because these domains are chosen by you at runtime and can't be known in advance, and because Chrome's declarativeNetRequest API requires host permission for any URL whose headers it modifies, Bonce asks for permission to read and change data on all websites rather than a fixed list — Chrome's standard phrasing for the permission used to add headers to outgoing requests. Bonce cannot read the content of pages you visit or your browsing history; it can only attach the header values you've configured to outgoing requests matching the domains you specify.

A note on secrets

Don't use passwords, session cookies, API tokens, or other long-lived credentials as header values. They're sent to every matching host, including over plain HTTP if a host isn't using HTTPS. Bonce also stores values unencrypted and doesn't mask them. It isn't built to be a secrets manager.

Questions

For privacy questions, email hello@camas.dev.