Last updated: 17 November 2026

Privacy Policy

ShieldBlock does not collect, transmit or sell any data. There are no accounts, no analytics and no telemetry. Everything the extension records stays in your browser.

What is stored, and where

All of the following is kept locally by the browser and never leaves your device except through Chrome's own sign-in sync, which is under your control.

DataWhereWhy
Settings — protection mode, category toggles, playback options, toolbar count, cookie pop-up and notification-request options, and the sites you leave alone for themchrome.storage.local, copied to chrome.storage.syncTo remember how you configured the extension
Allowlist — sites you paused protection on, and when a timed pause endschrome.storage.local, copied to chrome.storage.syncTo keep protection off on those sites, and turn it back on when the time is up
Hosts you allowed on one site from the popup’s “Blocked on this page” listchrome.storage.local, copied to chrome.storage.syncTo let those requests through on that site only
Custom hiding rules and “My filters” lines you wrotechrome.storage.local, copied to chrome.storage.syncTo keep applying the rules you chose
Block counters — ads, trackers and popups blocked, per site and per daychrome.storage.localTo show the statistics in the dashboard
When each open tab last loaded a pagechrome.storage.session (cleared when the browser closes)To show only the current page in “Blocked on this page”
What happened to each open tab’s cookie pop-up and notification requests: the consent platform’s name and whether it was rejected, hidden or shownchrome.storage.session (cleared when the tab moves on or the browser closes)To show it in the popup
Totals of cookie pop-ups rejected or hidden, notification requests stopped and links cleanedchrome.storage.localTo show the totals in settings
Theme preferencechrome.storage.localTo remember light or dark mode

chrome.storage.sync is Chrome's own settings sync. When your settings are small enough to fit, ShieldBlock keeps a copy there so a new install on another of your devices starts with them. If you are signed into Chrome with sync enabled, Chrome replicates that copy across your devices. That transfer is performed by Chrome, not by ShieldBlock, and is covered by Google's privacy policy. Nothing is sent to the extension author or to any third party.

What is not collected

  • Browsing history
  • Page content, form input, passwords or cookies
  • Personal or financial information
  • Any identifier that could be tied to you
  • IP addresses

The extension makes no network requests of its own. It has no server.

Reporting a broken site

The popup's Page not working? → Report this site button opens your own email app with a message to support@nanotom.in already written. The message contains the site's name (not the full address), the ShieldBlock version and mode, the protection, cookie pop-up and notification-request settings, and the list of hosts ShieldBlock blocked on that page. Nothing is sent unless you send it, and you can edit or delete any of it first.

Cookie pop-ups and notification requests

Both options are off by default.

Cookie pop-ups applies only to the pop-ups of known consent platforms. “Hide them” hides a pop-up without answering it. “Reject all for me” presses the pop-up’s own “Reject all” (or “Necessary only”) button, so the site records that you refused, as it would if you had pressed it yourself; a pop-up without such a button is hidden instead. ShieldBlock never presses a button that gives consent. On sites you choose to leave alone, pop-ups are left as they are.

Stop “Show notifications?” requests tells sites you have never allowed or blocked that notifications are blocked, so they do not ask. It does not change Chrome’s notification settings, and sites you already allowed are unaffected.

Clean tracking from links

On by default, with a switch in Settings. When you open a page whose address carries an ad-click identifier, such as fbclid, gclid or msclkid, Chrome’s own request engine takes that identifier out of the address before the page loads, following a fixed list that ships inside the extension. ShieldBlock does not read or keep the address; it keeps only a count of how many addresses were cleaned. Campaign tags (utm_…) and anything a site needs to show the page are left as they are.

The how-to-use page

After a first install, ShieldBlock opens its own “How to use” page once. It is part of the extension, loads nothing from the internet, and is never opened again on an update. Its switches change the same settings as the Settings page.

Why the extension can read every site

ShieldBlock requests access to all websites (<all_urls>) because an ad blocker cannot know in advance which sites will serve ads. That access is used only to:

  1. block requests to advertising and tracking hosts,
  2. hide advertising elements in the page,
  3. take ad-click identifiers out of the addresses of pages you open, and
  4. detect and repair broken video playback.

Page structure is read in your browser, used immediately to decide what to hide, and then discarded. It is never stored, logged or transmitted.

Statistics detail

The dashboard shows counts of blocked requests, broken down by site. The site names in that breakdown come from tabs where a block occurred, and are stored locally so the numbers persist between sessions. Clear them at any time with Settings → Statistics → Reset Statistics, or remove everything by uninstalling the extension.

Third parties

None. ShieldBlock includes no third-party libraries, SDKs, trackers or remote code. The blocking rule lists ship inside the package and are not fetched from anywhere. Part of the ad and tracker lists is derived from EasyList and EasyPrivacy (easylist.to), used under the Creative Commons Attribution-ShareAlike 3.0 licence; they are lists of rules bundled with the extension, not services, and nothing is sent to them.

Children

ShieldBlock is not directed at children and collects no data from anyone, regardless of age.

Changes

If this policy changes, the updated version will accompany the release that changes it, and the date above will be updated.

Contact

Questions about this policy can be sent by email to support@nanotom.in.