Effective date: 26 July 2026
Last updated: 26 July 2026
Applies to: the IP Protection browser extension (Chrome / Chromium, Manifest V3)
The short version
IP Protection collects nothing, sends nothing, and has no server.
The extension has no backend, makes no network requests of its own, contains no analytics or telemetry, and loads no remote code. The only information it keeps is a handful of settings that you create yourself, and those never leave your device.
1. Information we collect
None.
We — the developer of IP Protection — receive no information about you or your browsing whatsoever. There is no account, no registration, no identifier, and no mechanism in the extension that transmits data anywhere.
Specifically, the extension does not collect, transmit, sell, rent or share:
- personally identifiable information (name, address, email, age, ID numbers);
- health, financial or authentication information;
- personal communications (email, messages, chats);
- location data;
- your IP address;
- web browsing history, visited URLs, or search queries;
- page content, form input, keystrokes, mouse movement or clicks;
- device or usage analytics of any kind.
2. Information stored on your device
The extension stores a small amount of its own configuration using the Chrome storage API. This data stays in your browser profile on your computer. It is not synced to a Google account and it is not accessible to us or to any third party.
Stored in chrome.storage.local (persists until you remove it or uninstall):
| Item | What it is | Example |
|---|---|---|
| Protection state | Whether the on/off switch is enabled | true |
| Allowlist | Domains you chose to unblock via "Allow domain" | ["grabify.link"] |
| Blocked counter | A single integer counting blocked requests | 42 |
Stored in chrome.storage.session (erased when you close the browser):
| Item | What it is |
|---|---|
| Temporary exceptions | Which domain you chose to open once, in which tab, after clicking "Open anyway" |
The allowlist is the only stored item that relates to browsing at all, and it exists only because you explicitly created an exception. No URLs, no hostnames of sites you merely visited, and no timestamps are ever written to storage.
3. How the extension processes navigation information
To do its job, the extension must be able to tell that a page you are about to open belongs to a known IP-logging service. This happens entirely inside your browser, in memory, and nothing is retained.
- Blocking. Chrome's
declarativeNetRequestengine evaluates the extension's block rules internally. The extension supplies the rules; it does not observe the requests those rules apply to. - Warning. When a top-level navigation starts, the extension compares the hostname against its bundled blocklist. If there is no match — which is the case for virtually everything you browse — the hostname is discarded immediately and nothing further happens.
- If there is a match, the blocked address is passed to the extension's own local warning page so it can show you what was blocked and offer you a choice. That page is part of the extension and runs on your device. The address is not logged, not stored, and not sent anywhere.
- Counting. When a request is blocked, one integer is incremented. The URL, hostname, tab and time of that request are not recorded.
The blocklist itself is bundled inside the extension. It is not downloaded, never updated over the network, and no lookup is performed against any external service. Updating the list requires a new version of the extension.
4. Permissions and why they are needed
| Permission | Why it is requested | What it does not do |
|---|---|---|
declarativeNetRequest | Blocks requests to domains on the bundled blocklist. | Does not give the extension visibility into your requests; Chrome applies the rules internally. |
declarativeNetRequestFeedback | Notifies the extension that one of its own block rules matched, so the counter in the popup is accurate. | The details of the matched request are discarded; only a counter is incremented. |
storage | Saves the settings described in section 2. | Stores no browsing data and syncs nothing. |
webNavigation | Detects that a navigation is heading to a blocked domain, so the warning page can be shown instead of a blank error page. | Nothing is stored or transmitted; the hostname is used for one decision and discarded. |
The extension requests no host permissions and injects no content scripts. It is therefore technically incapable of reading the content of any web page you visit, of seeing what you type, or of accessing cookies, credentials or site data.
5. Third parties
There are none. IP Protection contains no third-party libraries, SDKs, trackers, advertising, or remote code. No data is shared with anyone, because no data is collected.
6. Retention and deletion
Because nothing is transmitted, there is nothing for us to retain or delete on your behalf.
The data on your device stays there until you remove it. You are in full control:
- Clear the counter — open the popup and choose "Clear counter".
- Remove an allowlist entry — open the popup and choose "Remove" next to the domain.
- Clear temporary exceptions — close and reopen your browser.
- Erase everything — uninstall the extension. Chrome deletes its storage along with it.
7. Children
IP Protection is a general-purpose privacy tool and is not directed at children. It collects no personal information from anyone, regardless of age.
8. Your rights (GDPR, UK GDPR, CCPA/CPRA and similar laws)
These laws give you rights over personal data that an organisation holds about you — access, correction, deletion, portability, and opting out of sale or sharing.
We hold no personal data about you. We never receive it, so there is nothing to access, correct, port or delete, and nothing that could be sold or shared. We do not act as a data controller or processor in respect of your use of this extension.
The information described in section 2 is under your own control at all times, and section 6 explains how to remove it.
9. Changes to this policy
If the extension ever changes in a way that affects this policy, the policy will be updated and the "Last updated" date above will change. Material changes — in particular, any change that would introduce data collection — will be described in the extension's release notes. Continued use after an update means you accept the revised policy.
10. Contact
Questions about this policy or about how the extension works? Send an email to contact@heldit.nl.
The source code is available for inspection, so every claim in this document can be verified directly.
Last updated: 26 July 2026
