What the extension stores

One thing: the list of domains you have blocked, and the expiry time you chose for each one. That is held in chrome.storage.sync, which is Chrome's own storage for your profile. If you are signed into Chrome, your browser syncs it between your devices through your Google account. It is never sent to me or to any third party.

What the extension does not do

  • It does not record, store, or transmit your browsing history.
  • It does not read the content of any page you visit.
  • It does not inject scripts into pages.
  • It contains no analytics, tracking, or telemetry.
  • It has no server, no account, and makes no network requests of its own.

How blocking works

Blocking uses Chrome's declarativeNetRequest API. Your block list is turned into rules that Chrome matches inside its own network stack. The extension is never handed the requests it does not block, so it has no view of where you browse.

The extension requests host access for one reason: when a blocked page navigation is stopped, the request is redirected to the extension's own Blocked page so it can tell you which site was blocked. Redirect rules in declarativeNetRequest require that access. Nothing is read from the page.

Removing your data

Uninstalling the extension deletes the block list along with it. There is nothing held anywhere else to delete.

Source code

The extension is open source under the MIT licence, so all of the above can be checked against the code: github.com/danieljohnmorris/site-blocker.

Contact

Questions about this policy: [email protected].