Privacy & permissions

An extension that runs on every page you visit deserves a straight answer about what it does there. Here it is: it reads the structure of elements you click, and writes a list of them to your own machine. Nothing else, nowhere else.

Nothing leaves your computer

  • No accounts — there's nothing to sign in to.
  • No servers — the extension has no backend of its own to send anything to.
  • No analytics or tracking — of any kind.
  • No sync — your rules stay on this computer and don't travel to your other devices.

What's stored

For each page where you've hidden something, the extension saves a short list of entries. Each entry is a CSS selector describing the element plus a brief label — its tag and a snippet of its text — so the popup can show you something readable rather than raw selectors.

That list lives in your browser's local storage, keyed by the page's host and path. It's what makes hidden elements stay hidden after a reload or a restart, and it's what fills the list in the popup. That's the entirety of what the extension keeps.

What the permissions are for

  • Storage — saves that list of hidden elements. Nothing else is written.
  • Active tab — lets the popup and the keyboard shortcut talk to the tab you're actually looking at, so the picker can start, count what's hidden, or restore it. It applies only to the tab you invoked the extension on, and only at the moment you invoke it.
  • Scripting — a fallback for tabs that were already open before the extension was installed or updated. Those tabs don't have the content script running yet, so it's injected into that single tab on demand rather than making you reload the page.
  • Access to all sites — see below.

Why it asks for access to every site

This is the permission worth explaining properly, because it sounds broader than what it does.

You decide which sites you want to prune, and the extension can't know that list in advance — it could be any page you visit. For a previously hidden element to be hidden again on your next visit, the content script has to be able to run there. Restricting it to a fixed list of sites would mean the feature silently failing everywhere else.

On a page with no saved rules, the content script reads its own empty storage entry and stops. It doesn't read the page's content, and it does nothing at all until you start the picker. While you are picking, it reads the structure around the element under your cursor — tag names, ids, and classes — in order to build a selector that will find it again.

Removing your data

Restore what you've hidden per page from the popup, or remove the extension from chrome://extensions — uninstalling takes its stored rules with it. There's nothing held anywhere else to delete.

Related guides

For exactly how a rule is scoped to a page, read How pages are remembered. To clear rules yourself, see Bring hidden elements back.