Privacy statements
One statement per tool. None of them use accounts, advertising trackers or analytics, and none sell personal information.
Noggin
Noggin is a Chrome extension for adding HTTP request headers that you configure to the requests your browser makes.
What Noggin stores
Your header names, values, on/off states and the master switch are
stored only in Chrome's local extension storage
(chrome.storage.local) on your own machine. Noggin never
sends your configuration to us or to any service of its own.
Uninstalling Noggin removes this data and stops all header changes.
Where your headers go
While a header is switched on, and the master switch is on, Noggin adds it to every request your browser makes, on every website. That includes requests to other servers loaded by the page you're on, such as images, scripts, ads and analytics. All of those servers receive the header's name and value. If a request already carries a header with the same name, Noggin replaces its value.
What Noggin doesn't do
No accounts, no cloud sync, no analytics, no ads, no tracking. Noggin makes no network calls of its own. It only changes the headers on requests your browser is already making.
Why Noggin needs broad permissions
Enabled headers may be added to requests across websites, so you never have to re-enable a header per site. That's why Noggin asks for permission to read and change data on all websites, which is Chrome's standard phrasing for the permissions used to add headers to outgoing requests. Noggin 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.
A note on secrets
Don't use passwords, session cookies, API tokens or other credentials as header values. An enabled header is sent to every server your browser contacts, so a secret would be shared with all of them. Noggin also stores values unencrypted and doesn't mask them in its popup. It isn't built to be a secrets manager.
Removing your data
Delete headers in the extension, or uninstall Noggin to remove everything it has stored.
Contact
Privacy questions can be sent to hello@camas.dev.
Bonce
Bonce is a Chrome extension for applying request headers that you configure to matching developer domains.
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. 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. This includes page
loads and requests for images, scripts and data. The patterns are
checked against the request's destination, not the page you're on. A
matched site's requests to other servers, such as analytics or CDNs,
don't get your headers. 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, no cookies. 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 your own domain patterns (specific hosts, wildcarded subdomains, or host:port combinations) and applies your configured request headers to requests matching them. Because these domains are chosen by you and can't be known in advance, and because Chrome requires host permission for any URL whose headers an extension modifies, Bonce asks for permission to read and change data on all websites rather than a fixed list. Bonce cannot read the content of pages you visit or your browsing history; it can only attach the header values you've configured to 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.
Removing your data
Delete your header sets in the extension, or uninstall Bonce to remove everything it has stored.
Contact
Privacy questions can be sent to hello@camas.dev.