Last updated: 28 July 2026
Shomer Filter is a content filter. You install it, activate it with a code tied to a Shomer Filter subscription, and it then filters the pages you visit in this browser: it forces SafeSearch, refuses searches for flagged terms, blurs or hides images, and blocks pages whose content trips its word list.
It is supervision software, bought deliberately by the person or household being supervised. This policy sets out exactly what it does and does not send anywhere.
Nothing. Until you enter a valid activation code the extension registers no content scripts, enables no rules, reads no pages and sends no network requests. An installed-but-unactivated Shomer Filter is inert.
| What | Where it goes | Why |
|---|---|---|
| Your activation code, once | api.shomerfilter.com | to exchange it for a session token |
| Your session token, periodically | api.shomerfilter.com | to check the subscription is still active |
| Domain pairs — “page on site A needed a resource from domain B, and could not reach it” | api.shomerfilter.com | so the allow-list learns which behind-the-scenes domains a permitted site needs |
| A liveness message | the Shomer Filter program on your own computer, over a local channel that never touches the network | so the filter knows the extension is running |
That is the complete list.
To keep permitted sites working, the extension reports domain pairs:
“a page on example.com needed cdn.example.net”. By default it
reports these only when the resource failed to load — which is
precisely the signal that the allow-list is missing an entry. It records the two domain
names, the resource type and the network error. It does not record the
page URL, the path, the query string, the page content, or a timestamp of your visit.
A subscription administrator can turn on a broader mode that reports successful dependencies too. Where a device is centrally managed, whoever administers the subscription decides this — as they already decide the filtering policy for that device.
We do not collect names, email addresses, passwords, payment details, location, health data, keystrokes, form contents, or the contents of your communications through this extension. (An account and payment exist on the Shomer Filter website; those are covered by the website’s own policy, not this one.)
We do not sell your data, and we do not share it with third parties
for advertising, analytics or any purpose unrelated to running the filter. There are no
third-party analytics, advertising or tracking libraries in the extension. The only
server it contacts is api.shomerfilter.com.
| Permission | Why |
|---|---|
<all_urls> host access | a filter that only works on some sites is not a filter |
declarativeNetRequest | force SafeSearch and YouTube Restricted Mode |
webNavigation | see a navigation in time to refuse a blocked search |
webRequest | observe which dependency domains failed (observation only — this extension cannot read or alter request bodies) |
scripting | register the filtering content script, and unregister it when not activated |
tabs | send a refused navigation to the block page |
storage | keep the session token and settings |
nativeMessaging | talk to the Shomer Filter program on the same computer |
alarms | re-check the subscription on a schedule |
Session tokens live until the session is revoked or the subscription ends. Reported domain pairs are kept as part of the shared allow-list; they are domain names, not records of a person’s browsing.
Uninstalling the extension stops all of it. On a centrally managed device the extension is installed by policy and cannot be removed by the user of that device — that is the point of a managed device, and it is disclosed at purchase. On such a device, extended access to certain sites is granted only while the filter is running, so removing it removes access rather than granting it.