Purpose
RequestHeaders adds HTTP request headers only according to key-value rows explicitly created and enabled by the user. It is intended for web development, API testing, and debugging.
Data handled
RequestHeaders stores profile names, header names, header values, row enabled states, the selected profile, and the global enabled state in Chrome’s local extension storage.
Header values may contain authentication information or other sensitive data if a user chooses to enter it. Users should only add values they intend to send to websites while the rule is enabled.
How data is used
Enabled values are applied locally through Chrome’s declarativeNetRequest API. While the global switch is on, those headers may be added to HTTP and HTTPS requests handled by Chrome’s network stack.
Collection, transmission, and sharing
RequestHeaders does not transmit extension settings, browsing activity, or usage information to the developer or any third party. It contains no analytics, advertising, tracking, account system, remote code, or external synchronization service.
RequestHeaders does not sell or share user data and does not use data for advertising, creditworthiness, or purposes unrelated to its single purpose.
Retention and deletion
Settings remain in local browser extension storage until the user removes rows or profiles, clears the extension’s storage, or uninstalls RequestHeaders.
Permissions
Changes and contact
Material changes to this policy should be reflected in the Chrome Web Store listing before the corresponding extension update is published.
For privacy or support questions, use the publisher contact displayed on the RequestHeaders Chrome Web Store listing.