This extension collects nothing, sends nothing, and has no server. It hides listing cards on Blocket search pages inside your own browser. Your filter settings are saved locally on your computer using Chrome's local extension storage, and they are never transmitted anywhere — not to us, not to Blocket, not to anyone. There is no account, no login, and no analytics.
Who we are
Filterfabrik, an independent developer. The extension is free and carries no advertising.
What the extension stores, and where
| Item | Where it lives | Does it leave your computer? |
|---|---|---|
| Which filters you turned on | Chrome local extension storage, on your device | No. |
| Words you chose to hide | Chrome local extension storage, on your device | No. |
| Maximum price and maximum age | Chrome local extension storage, on your device | No. |
| Listing IDs you have already seen | Chrome local extension storage, on your device | No. |
| Your chosen interface language | Chrome local extension storage, on your device | No. |
All of the above uses chrome.storage.local. It deliberately does
not use chrome.storage.sync, which would copy your settings to your
Google account and off your device. Uninstalling the extension deletes all of it.
What we do NOT collect
- No personal information, name, email address or account of any kind.
- No browsing history, and no record of which listings you viewed leaves your device.
- No analytics, telemetry, crash reporting, advertising or tracking identifiers.
- No data is sold, rented or shared, because none is collected in the first place.
Permissions, and why each one is unavoidable
| Permission | Why it is required |
|---|---|
storage | Saves your filter choices locally so they survive closing the browser. Nothing leaves the machine. |
*://*.blocket.se/* | The filter has to read and hide listing cards on Blocket's own result pages. Scoped to blocket.se only. |
There is no <all_urls> permission. The extension cannot read any site
other than the one named above.
How to verify this yourself
You do not have to take our word for it. Open chrome://extensions, turn on
Developer mode, and open the extension's service worker. Then open DevTools → Network and
use the extension normally. You will see no outbound requests, because there are none in the
code: the extension contains no fetch, no XMLHttpRequest, no
sendBeacon and no WebSocket to any external host. The typeface it uses is packaged
inside the extension rather than loaded from a font CDN, precisely so that displaying text is
not a network event.
Children
The extension is not directed at children and collects no data from anyone, of any age.
Changes
If this policy ever changes, the new version is published here with a new effective date. A change that expanded what the extension can access would also require a new permission, which Chrome shows you before it takes effect.