Privacy Policy
Ad Interceptor
A browser extension that blocks advertising and the tracking scripts behind it.
- Effective
- October 9, 2026
- Applies to
- Ad Interceptor v3.0+
- Data collected
- None (free) · Licence key and a random installation ID (Pro)
The extension collects nothing about you — every rule ships inside it and runs inside your own browser. It makes one request for everyone: once a day it fetches a small settings file from our own server, saying whether offers are running (for example, whether Pro is currently free). That request carries no identifier, no licence key and nothing about your browsing; like any web request it reveals your IP address to Cloudflare, which hosts our server, and our code does not record it. If you have a Pro licence key, one more thing happens: the key, with a random installation ID, is sent to our server to check that it is valid, and to download updated filter rules. Those are the only network requests this extension ever makes, and they never carry anything about your browsing.
What this extension does
Ad Interceptor stops advertising and tracking requests using Chrome’s built-in declarativeNetRequest API, and hides leftover ad containers with a bundled stylesheet. Blocking decisions are made by Chrome itself, evaluating rule files bundled inside the extension package. Our own code never inspects, reads, or has access to the content of your browsing.
Data we collect
Free version: none. Specifically:
- We do not collect, log, or transmit your browsing history, page content, or the URLs you visit.
- We do not run analytics, telemetry, or crash reporting of any kind.
- Without a licence key, the only request the extension makes is the settings fetch described above, which carries nothing about you. Nothing your browser does is ever sent anywhere.
- The only data stored is your own settings — the on/off switch, the sites you have paused, and a running count of blocked requests — held in Chrome’s
storage, under your own Google account if Chrome Sync is enabled, never accessible to us.
Pro version: your licence key and a random installation ID, and nothing else.
- When you activate Pro, and roughly once a day afterwards, the extension sends your licence key to our server so we can confirm it is still valid. The response says only whether the licence is active and when it expires.
- The same key authenticates a daily download of updated filter rules.
- These requests contain your licence key, the extension version, and an installation ID. The installation ID is a random value the extension generates the first time you activate Pro on a browser; it is not derived from you, your device or your browser, and it is not shared between your devices. We store it with your licence, together with the version and when it was first and last seen, only to count how many browsers a licence is active on so the device limit can be enforced.
- These requests do not contain, and cannot be used to derive, the sites you visit, what was blocked, or anything else about your browsing.
- We use the key and installation ID solely to check entitlement. We do not sell it, share it, or use it to build a profile.
The blocked-request counter
The number on the toolbar icon comes from Chrome’s own getMatchedRules(), which reports how many of the extension’s rules matched on the current tab. We use it to display a count and to keep a running total in local storage. The matched URLs themselves are never stored, logged, or transmitted — only the number is kept, and it stays on your device.
Permissions we request
Chrome requires every permission to be declared up front. Here is what each one is actually used for:
| Permission | Why we need it |
|---|---|
| host_permissions <all_urls> |
Ads appear on arbitrary sites, so the rules and the element-hiding stylesheet have to be able to apply anywhere you browse. It is not used to read or collect page content. |
| declarativeNetRequest declarativeNetRequestWithHostAccess |
Lets Chrome itself block matching requests using rule files bundled in the extension — the blocking decision happens inside Chrome, not in code we control. |
| declarativeNetRequestFeedback | Counts how many of our own rules matched, so the badge and popup can show you a number. Nothing derived from it leaves your device. |
| storage | Saves your settings, paused sites, blocked count, and — for Pro — your licence key, so they persist between sessions. |
| scripting | Registers the on-page code that hides leftover ad containers, and, for Pro users only, the scripts that defeat anti-adblock detection and remove YouTube video ads. |
The two Pro scripts run in the page’s own JavaScript context (world: "MAIN"), which is necessary because their job is to change what the page’s own scripts see — an isolated script cannot do that. They are static files inside the package; no code is ever downloaded and run. Both stop running entirely if you pause a site or turn blocking off.
Third-party rule data
The blocking rules are compiled at build time from EasyList and EasyPrivacy, and — for Pro — the Adblock Warning Removal List. These are community-maintained, publicly available filter lists, used here under the Creative Commons Attribution-ShareAlike 3.0 licence and credited accordingly. They are static data compiled into the extension; the free version never contacts EasyList or anyone else while running.
Data sharing & sale
We do not sell user data and never will. The free version collects nothing to sell. The Pro version handles a licence key, which is used only to verify that a licence is valid.
This website, and paying for Pro
Everything above describes the extension. This website is separate, and the distinction matters: the extension sends nothing about you, but a payment necessarily involves a payment company.
These pages load no analytics, no tracking scripts, no cookies, no webfonts and no third-party resources of any kind — including the pricing page. There is no longer any exception. Buying Pro navigates you to PayPal’s own checkout page; nothing belonging to them runs on this site.
If you uninstall the extension, Chrome opens a page here asking why. If you tap a reason, that page sends it to our own server along with anything you choose to type, the extension version, and the country Cloudflare reports for the request. No IP address, no identifier and nothing about your browsing is stored, and nothing is sent unless you tap.
If you buy Ad Interceptor Pro, you are buying from us — Ratnesh Kushwaha, trading as Ad Interceptor. PayPal processes the payment as our payment provider. Your billing details and payment method go to PayPal, not to us, and are handled under PayPal’s privacy policy. We never see or store your card details.
What we receive from PayPal, and store, is limited to what is needed to run a licence: your email address, their customer, order and subscription identifiers, and the licence key we issue you. That is used to verify your licence and to contact you about it — nothing else.
Children’s privacy
Ad Interceptor is a general-purpose browser utility, not directed at children, and does not knowingly collect information from anyone, of any age — see “Data we collect” above.
Changes to this policy
If this policy changes, the “Effective” date at the top of this page will be updated accordingly. Material changes will also be reflected in the extension’s Chrome Web Store listing.
Contact
Questions about this policy, or about the extension’s handling of data, can be sent to thenightwatchcaptain@gmail.com. This address is monitored for both user enquiries and Chrome Web Store review correspondence.