This policy explains how the ModHeader Extension (HTTP Header Editor) Chrome extension, published by TARKO EVOLUTION SL, handles your data.
What the extension does
ModHeader Extension adds, modifies or removes HTTP request and response headers (and, in Pro, cookies and redirects) on the sites you choose, using the browser's declarativeNetRequest engine. The rules are applied by the browser itself, so the extension never sees the content of your requests or the pages you visit. It runs entirely in your browser.
Request body rules (optional). If you create a rule to change the body of a request, a small script runs only on the sites you list in that rule (or on every site, if you choose "*"), and only while that rule is on. With no body rule turned on, no script runs on any website. The script wraps the page's own fetch and XMLHttpRequest calls to change the body before it is sent, as your rule says. It does not read or change the page itself, and nothing it handles ever leaves your browser: no request, body or address is sent to us or to anyone else. Because the script runs inside the page, that website's own code can see the body rules that apply to it (only those for that site, never the rest of your rules).
Data we do NOT collect
- Your browsing history or the pages you visit.
- The content of web pages or the body of your HTTP requests or responses, even when a body rule changes it.
- Your rules, profiles and preferences (stored only in your browser, unless you turn on Cloud).
- No analytics, no telemetry, no tracking, no ads.
Data we do handle
Pro purchase. If you buy the optional one-time Pro upgrade, the payment is processed by Stripe, which receives your card details and email to issue a receipt; we never see or store your card details. A license key is then generated.
Emails. We keep the email address and first name you gave at checkout, linked to your license key. We use them only to send you the key, one single message the day after your purchase asking how you rate the extension, and to answer you if you write to us. No newsletters, no marketing. These emails are sent through Resend.
License validation. The extension stores your license key locally and sends only that key to our server (extensionshub.net) to confirm it is valid and unlock Pro. No personally identifiable information is sent.
Cloud account (optional). Only if you sign in to Cloud, we keep your email address, the name of each device you sign in on (for example "Chrome · Windows"), the teams you belong to, and the profiles you sync, with up to 20 earlier versions of each. Synced profiles are stored encrypted on our servers and are used only to sync your devices and share them with your team. We send emails only for sign-in codes and team invitations. If you subscribe, Stripe handles the subscription. You can ask us to delete your account and its data at any time by writing to info@extensionshub.net; we do it within 30 days.
Uninstall survey. When you remove the extension, Chrome opens a short page on extensionshub.net asking why. The address only carries the extension version and your browser language. Answering is optional: we only receive the option you pick and, if you choose to, a comment and an email address for a reply. Nothing about your rules or the sites you visit is sent.
Permissions
- declarativeNetRequest (with host access): to apply or redirect headers through declarative rules. The extension does not read the content of your requests; the browser applies the rules.
- Host access: so your header rules can apply on the sites you decide, via URL filters or regular expressions. It does not mean we read or store the content of those sites.
- storage: to save your rules, profiles and preferences in your browser.
- scripting: only for request body rules, to run the script described above on the sites you list in each rule and only while it is on.
- alarms: to sync your profiles every few minutes when you are signed in to Cloud.
- Access to extensionshub.net: for Pro payment and license validation, including a small script that runs only on our own thank-you page after purchase to activate your license, and, only if you use it, Cloud sign-in and sync. Your header rules never apply to extensionshub.net.
Third parties
We use two third parties: Stripe, to process the optional Pro payment, under its own privacy policy, and Resend, to send the emails described above, under its own privacy policy. We do not sell or share your data with anyone.
Contact
Questions about this policy: info@extensionshub.net.