Effective 6 October 2026 · applies to the Porn Filter Chrome extension and to pornofilter.app

The short version

Porn Filter does not collect, store on a server, transmit or sell any information about you. There is no account, no sign-in, no analytics and no advertising. The extension has no backend: everything it does happens inside your browser, on your device.

What the extension stores — on your device only

Porn Filter keeps its settings in Chrome’s extension storage on your computer: your password (as a salted hash, never in plain text) and its optional hint, the lists of sites you blocked or allowed, the on/off state of each protection layer, the unlock delay, Family mode and its message, Panic mode’s end time, the activity log of blocks and setting changes, and the images you chose to remember as safe. Uninstalling the extension deletes all of it. Nothing in this storage is ever read by us or sent anywhere.

The result of each image check — a number per picture address — is kept in memory for the current browser session, so the same picture is not checked twice; it is gone when the browser closes.

Some lists ship inside the extension and never change on your device except through updates: the adult and gambling domains, the adult-only ad networks, and a list of well-known sites where images are not checked. Deciding whether a page is on one of them happens in your browser; nothing is looked up online.

What the extension sends

Nothing about you. The image filter is a model that runs entirely in your browser; images are never uploaded. Your history, the sites you block and everything you type stay on your device.

The extension makes two requests of its own and no others. It opens its setup page, pornofilter.app/welcome, once right after installation. And once a day it downloads a list update from pornofilter.app — a single static file of newly found adult domains, the same file for everybody. That request carries no data about you: no identifier, no account, no cookies, nothing about the pages you visit, and we keep no logs of it. If it fails, nothing changes: the lists packaged inside the extension keep working, offline and indefinitely.

One more kind of request is not of its own making, and we name it because it is a request. To check an image on a page you opened, the extension sometimes has to read that image again: a picture from another address than the page cannot be read inside the page, so the extension fetches it from the same site that is already showing it to you, in your browser, with your browser’s own cookies for that site and from the browser cache where possible. It goes nowhere else, it carries nothing that your visit did not already send, and the image is checked on your device and then forgotten.

Every other connection your browser makes while Porn Filter is installed is one you made yourself by visiting a website.

Why it asks for these permissions

Read and change data on all websites
Needed to stop an adult page before it loads — also when another page embeds it in a frame — to stop adult-only ad networks, to hide explicit images on the pages you open (when the image check is on), and to keep safe search switched on. No page content leaves your browser.
Tabs and navigation
To send a blocked tab to the block page, to count blocks in the activity log, and to close incognito windows when you ask for that.
Alarms
For timers: the unlock delay, a pause, temporary access, Panic mode.
Context menus
The “Block this site” item in the right-click menu.
Storage
Your settings, on your device.
Offscreen document
Runs the on-device image classifier in one hidden extension page instead of in every tab, so memory stays flat and tabs start faster. No page content leaves the device.
Scripting
When the extension updates, Chrome disconnects the filter from the pages already open. This permission lets the new version start the filter in those pages again right away, instead of leaving them unprotected until you reload them.

The setup page

After installation the extension opens pornofilter.app/welcome. When you type a password there, the page hands it to the extension inside your Chrome through the browser’s own extension messaging; the page has no server to send it to, and its security policy forbids any network connection. The page can only do three things: read the setup status, set a password when none exists yet, and open the extension’s Settings. It can never change or remove an existing password or switch any protection off.

When you remove Porn Filter

When you remove the extension, Chrome opens pornofilter.app/uninstall/ once. That is Chrome’s doing, after the extension is gone, and the address carries nothing about you — no identifier, no version, nothing at all. The page asks one question in a Google Form, shown in a frame from docs.google.com; answering it is optional. What you type there — an email address too, if you leave one — goes to Google Forms, under Google’s privacy policy. The page itself sends nothing anywhere.

This website

pornofilter.app is a static site with no cookies, no analytics and no third-party scripts. Like any web host, the company that hosts it may keep standard server logs (such as IP address and time of access) for a short time to run its service. We do not use those logs to identify anyone.

Lock mode

The optional Lock mode is a Chrome policy that you apply on your own computer with the guide inside the extension. The policy names only the extension’s identifier; it contains nothing about you and is not sent anywhere.

Children

Porn Filter can be set up by a parent for a child’s computer. Family mode shows a child a neutral page without the product name. The extension collects no information about the child or anyone else.

Changes

If this policy ever changes, the new version will be published here with a new effective date. The extension itself will not start collecting anything without a new version and an updated policy.

Contact

support@pornofilter.app