HeaderForge

Last updated August 23, 2026

Privacy policy

HeaderForge is designed to modify HTTP headers locally in your browser. It does not require an account and does not send your rules or browsing activity to a HeaderForge server.

Summary

HeaderForge stores the header rules and preferences you create in Chrome’s local extension storage. The extension processes those rules on your device through Chrome’s Declarative Net Request API.

No account, analytics, or remote rule service

HeaderForge does not sell personal information, profile browsing activity, or use rule values for advertising.

Data handling

Information stored locally

HeaderForge stores rule definitions, enabled states, URL filters, and the global pause setting in chrome.storage.local. A rule may contain values you enter, including test authorization values or custom headers.

Network activity

HeaderForge does not operate a server that receives your rules or browsing history. Chrome evaluates enabled rules against permitted network requests on your device. Websites you visit still receive the request headers that you deliberately configure for matching URLs.

Export and import

Export copies the current rule list as JSON to your clipboard. Import reads JSON that you provide. You control where exported data is stored or shared. Review exported files before sharing because they may contain sensitive header values.

Browser permissions

The extension requests only the permissions needed to create and manage header rules.

declarativeNetRequest

Creates dynamic browser rules that add, modify, append, or remove eligible request and response headers.

storage

Saves your rules and preferences locally so they remain available after Chrome restarts.

Host access: <all_urls>

Lets rules apply to URLs you choose. HeaderForge needs broad host access because a header editor cannot know in advance which development, staging, local, or production host you will test. Per-rule URL filters let you narrow the actual scope.

Your control

You can disable individual rules, pause all rules, delete rule definitions, or uninstall HeaderForge. Uninstalling the extension removes its local Chrome storage according to the browser’s extension data behavior.

Avoid placing production credentials or long-lived secrets in rules. Use short-lived test values and narrow URL filters whenever possible.

Policy changes

This page may be updated when HeaderForge’s features, permissions, or data practices change. The effective date at the top of the page identifies the latest revision.

For common data and storage questions, read the HeaderForge FAQ. For technical help, visit the support page.