HeaderForge Privacy Policy
Summary: HeaderForge is offline-first. It does not collect, transmit, sell, or share your data.
- Zero telemetry
- Zero analytics
- No external API calls for extension features
- No accounts
- No cloud sync in v1
What we store
Configuration is stored only in chrome.storage.local on your device:
- Profiles
- Header definitions (names, values, operations)
- Domain rules
- Enable/disable state and “All sites” preference
- Automatic local backup snapshot
What we do not do
- Send browsing history, URLs, or headers to any server
- Use Google Analytics, Sentry, or similar tools
- Phone home for license checks or usage stats
- Store data outside
chrome.storage.local - Require an account
Permissions
| Permission | Why |
|---|---|
storage |
Save profiles locally |
declarativeNetRequest / host access |
Modify request headers |
tabs |
Open options and support toolbar workflows |
http://*/*, https://*/* |
Required so header modifications can run on websites. No browsing data leaves your device. |
Domain marks
Favicon-like marks next to domain rules are generated locally (SVG data URIs). They are not fetched from the network.
Changes
If a future version adds optional cloud sync, it will be opt-in, documented, and never enabled by default.
Contact
For privacy questions or reports, open an issue in the HeaderForge GitHub repository.