Privacy policy
Effective 8 November 2026
Kosher Browser is an extension for Chrome and Firefox on a computer, and for Firefox on Android phones. It runs entirely on your own device and helps block distracting or inappropriate websites — with child profiles and time limits, daily time per site, schedules, a Shabbat and Yom Tov mode, a focus timer, password protection, strict mode, SafeSearch enforcement, an ad blocker, YouTube controls, and image, word and music filters. Get it from the Chrome Web Store or Firefox Add-ons; this policy covers both. This page explains, in plain English, exactly what data the extension touches.
What we collect
Nothing. Kosher Browser collects no personal data, no analytics, no telemetry, and no crash reports; it sells or shares nothing. There is no account system because there is nothing to associate to an account.
Where your settings live
All settings are stored in the extension's own browser storage (chrome.storage) — on your own device only, with no syncing to your browser account.
What Smart mode found in the images it checked is also kept on your device only, in the extension's own IndexedDB.
The bytes never leave your device. “Save to a file” (Settings → General) writes your settings to a file on your computer, where your browser saves downloads; it holds no password, no children's codes and no list of blocks, and it is never uploaded anywhere.
What is stored
- Your blocklist, your whitelist (and whether Whitelist mode is on), category choices and schedule.
- The settings of each filter: the ad blocker and the sites allowed to show ads; the image hider's mode and options (who Smart mode covers, how covered images look, reveal with a click, peek on hover, the status label on videos), the sites without blurring and the sites you chose to blur from the toolbar popup; the word filter's mode, your words, the sites without the word filter, and whether the built-in list for children and the explicit-words list are on; the music filter, whether it also mutes singing without instruments, and the sites without the music filter; your YouTube settings — the mode, “Block YouTube ads”, Restricted Mode, the approved channels and the “Tidy YouTube” switches (hide comments, suggested videos and the home feed, no autoplay); and your blocked-page message.
- The sites you gave a daily time, with their minutes; and, for today, how many minutes each of those sites was on screen for each profile and any extra minutes a parent added. Only these sites are counted, and only the minutes.
- The Shabbat and Yom Tov setting: whether it is on, the place you chose (as a latitude and longitude), whether Yom Tov is kept one day or two, and the candle-lighting and havdalah minutes. The times are worked out on your device; no calendar or location service is asked.
- Sites a parent opened from the block page for a while (“For 15 min”, “For 1 hour”): the site's name, the profile, and when it closes again — until then.
- Sites with a waiting page, and how many seconds it counts down; and, for each such site you waited for, when it closes again (15 minutes later). Until the browser closes, in
chrome.storage.session: when a tab's waiting page opened, so its “Continue” cannot come early. - The address blocked sites go to instead of the block page, if you chose one, and whether the removal notice is on.
- When to show the toolbar popup's one request to rate or share the extension (a week after it was installed or updated to version 1.9.0, or a month after “Not now”), and whether that request is finished.
- Whether the focus timer is active and when it ends.
- A cryptographic hash (SHA-256) of your password, if you set one. The plaintext password is never stored anywhere.
- For the password and for each child's code: how many wrong tries in a row, and when a lockout ends, so guessing can be slowed down.
- Two numbers: how many times a page was blocked today and in total (for the in-extension statistics view).
- The list of recent blocks, for the parent: for each of the last 300 blocked pages, when, why (for example “Blocklist” or “Category: Social networks”), which profile was browsing, and the name of the listed site that closed it — the entry from your blocklist or a category list, or, in Whitelist mode, the site's host name. Never the full address of the page. Blocks by the adult-site list are listed without any site name; blocks in a private window are not listed at all (they only add to the day's block count). The list is shown only in Settings → General, after the password, and “Clear the list” erases it.
- Your interface language preference (Hebrew or English).
- Whether “Blocking enabled”, SafeSearch enforcement and strict mode are on.
- Family profiles, if you create them: each profile's name, avatar, color, age band, filters, daily time limit and downtime hours, plus a SHA-256 hash of its optional 4-digit profile code, and which profile is browsing now.
- How many minutes each profile has had a browser window in focus today, and any extra minutes a parent added today, so the daily limit can be enforced. Only the minute count is kept; the extension never records which sites were open. On phones (Firefox for Android), which have no browser windows to check, every minute Firefox is open counts. When a limit or downtime begins, or the browser opens to the “Who's browsing?” screen (also after an update of the extension), open web pages are reloaded so the block takes effect immediately.
- Until the browser closes, in
chrome.storage.session: when the 5-minute unlock of Settings ends, whether a profile was picked since the browser opened, and whether the web is closed right now and why (the “Who's browsing?” screen, downtime or the daily limit); and, for a YouTube video closed in “Approved channels only”, its channel's name and links and the video's address, for the block page's “Approve this channel”, until a parent approves it or the browser closes. - What Smart mode found in each image it loaded from an address, for up to 5,000 images, in the extension's own IndexedDB — never the image or its address (details under “offscreen” below).
Network requests
Kosher Browser sends no data to any server: there is no server, no analytics and no usage reports. The code and the models ship inside the extension; no code or model is downloaded.
There is one case where the extension itself goes to the network: in the image hider's Smart mode it loads again an image the page already loaded, from exactly the same address, so it can check it on your device. That request carries no cookies and does not follow redirects; the only thing the extension adds to it is the browser's standard header listing the image formats it accepts, so the site sends the same kind of file the page got. The extension refuses to send it to private network numbers and to the local-network names it can recognise (details under “offscreen” below). The image itself is never sent anywhere. With Smart mode off, the extension makes no network requests of its own. Two choices of yours open a web page, as a link would: “Where blocked sites go” sends a blocked page to the address you chose, and the removal notice (off unless you turn it on) makes the browser open a page on kosher-browser.pages.dev when the extension is removed. That page visit carries nothing from the extension. The “Rate” and “Share” links (in the toolbar popup and in Settings → General) open the extension's store page, WhatsApp, Telegram or your mail app only when you click them; a share carries a short description and the address of kosher-browser.pages.dev, nothing else.
Links you click inside the extension (the guides on this site, WhatsApp support, email, the site tiles on the block page) open like any other link. The block page's “Back to where I came from” button opens google.com when there is no earlier page, and so does the “Who's browsing?” screen when there is no page to return to and Whitelist mode is off.
Permissions explained
- storage — stores your settings in
chrome.storage.local, and a few values that are cleared when the browser closes inchrome.storage.session. Smart mode's record of checked images is kept in IndexedDB, which needs no permission. - alarms — a check once a minute: is it inside a schedule window or downtime, is it Shabbat or Yom Tov at the place you chose, has today's time run out, and has a site's daily time run out? If a browser window is in focus (on Firefox for Android, whenever Firefox is open), the same check adds one minute toward the daily limit; it looks only at whether a window is in focus, never at tabs or sites. A second check, every 30 minutes, starts a new day's block count, and one more alarm ends a focus session on time.
- declarativeNetRequest, declarativeNetRequest
WithHostAccess — rules the browser itself applies by address: sending blocked sites to the block page or to the “Who's browsing?” screen, blocking ad and tracking servers, adding SafeSearch to Google, Bing (its AI Mode too), DuckDuckGo, Brave, Yahoo, Qwant and Startpage searches, and turning on YouTube Restricted Mode. The rules are built from your settings, plus lists that ship inside the extension: the adult-site list, translation and archive services that would show any site (both always on), and, while the ad blocker is on, a list of ad servers and of pop-up ad networks. Apart from the “Who's browsing?” screen and the time's-up, downtime and Shabbat pages (see “Open tabs” below), they do not tell the extension which addresses you open: any other block page is told only the reason and the name of the listed site that closed it (in Whitelist mode and on a waiting page, the site's host name), never the full address; that name is what the block page shows under “Open this site” and what the list of recent blocks keeps. - host: <all_urls> — required to block or allow any site you choose, and so the filters described below can work on any site. The blocking rules look at the address only. Page content is read only by the scripts described below, only while their option is on, and always on your own device. This permission also lets the extension see the addresses of open tabs, which it uses only as described under “Open tabs” below.
- scripting (YouTube ads) — registers a script on youtube.com only while “Block YouTube ads” is on and blocking is not paused, and removes it otherwise. The script drops the ads from YouTube's Shorts feed before the page reads it; ads in the video player are hidden, muted and fast-forwarded by the youtube.com script described below. It reads no personal data and sends nothing anywhere.
- scripting (image hider) — registers a script on every site while the image hider is on; while it is off, only on the sites you chose to blur from the toolbar popup. It also runs inside the frames those pages make for themselves (about:blank, srcdoc and data: frames, where many ads are drawn), and it reaches the pictures inside web components (open or closed shadow roots) too. It covers images and videos; while “Reveal with a click” is on, a click reveals one until the page reloads. In “Blur images” mode it reads nothing but the on-screen size of image elements, so small icons can stay visible, and, when you click, what lies under the pointer, so the click reaches the picture and not a button drawn over it; it never inspects what an image contains. In Smart mode the same script also hands the images of the top page, web components included, to the on-device engine described under “offscreen” below (pictures inside frames are not checked and stay covered); before it hands over a picture the page made itself (a blob: address), it reads that picture's file, on your device, to see whether it is animated, and an animated one stays covered. It never stores anything and never sends anything off your device. Sites without blurring never receive the script at all.
- scripting (word filter) — registers a script on every site only while the word filter is on and has at least one word of yours, or one of its built-in lists switched on: the list for children (new child profiles start with it on) or the explicit-words list (every protection level turns it on). It also runs inside the frames those pages make for themselves (about:blank, srcdoc and data: frames, where many ads are drawn). It reads, on your device, the text shown on the page, the page's title and the text descriptions of images, compares them with the word list, and hides or blurs the card, post or paragraph that mentions one. While a built-in list is on, a page whose own title is a sexual topic (such as an encyclopedia article about one) goes to the block page instead. It never reads what you type into forms or text boxes, does not analyze images, never stores page text, and sends nothing anywhere. Sites without the word filter never receive the script.
- scripting (music filter) — registers a script on every site only while the music filter is on. It also runs inside the frames those pages make for themselves (about:blank, srcdoc and data: frames). It listens to videos and audio that are playing, on your device: about one second at a time is reduced to 16 kHz mono and handed to the extension's own engine (an open-source sound classifier bundled in the extension), which says whether it hears music; if it does, the element is muted until the music ends. Audio is never recorded, stored or sent anywhere. Sites without the music filter never receive the script.
- scripting (daily time per site) — registers a script only on the sites you gave a daily time, only while blocking is not paused, and only in the page itself (not in frames). Once a minute, while the page is on screen (its tab is visible and its window has focus, or a video or audio on it is playing), it tells the extension's own background “still here”; the background works out the site from the page's own address, counts the minute, and, once the site's time is used up, closes it until tomorrow and reloads the page so the block page appears. The script reads nothing from the page except whether the tab is visible and whether something is playing, stores nothing and sends nothing anywhere.
- scripting (ad styles) — while the ad blocker is on and blocking is not paused, registers two style sheets and no script: one on every site, which hides the empty boxes blocked ads leave behind, and one on Google, Bing, DuckDuckGo, Yahoo and a few big Israeli news sites, which hides their own sponsored results and items. A style sheet reads nothing from the page and sends nothing. Sites on your list of sites allowed to show ads never get them.
- Site access (no extra permission) — the browser lets anyone take away an extension's access to sites (Chrome's puzzle menu, Firefox's add-on page), and without it the blocking rules stop. The extension asks the browser whether it still has that access; if not, it says so in its toolbar popup and Settings, and while a password is set it closes every site until access is given back. It reads nothing from any page.
- scripting (reload notice) — after an install or update, and only if one of the filters that work inside pages (images, words, music or YouTube) is on, the extension shows a small notice in each open web tab with a “Reload” button, because those filters start on a tab only after it reloads. The notice reads nothing from the page, stores nothing and sends nothing.
- offscreen (on-device engine) — only while the image hider is in Smart mode or the music filter is on; on Chrome the engine is closed when both are off. It hears the short sound clips the music filter hands it, and in Smart mode it checks images: every image starts covered, and the engine, built from open-source models that ship inside the extension, releases only images that show no one you chose to cover. To read an image it fetches the same address the page loaded (for images the page drew itself, and for video frames, it takes a reduced copy in the page). That request is sent without cookies and does not follow redirects, and the only thing the extension adds to it is the browser's standard header listing the image formats it accepts. The extension refuses to send it to local-network names (like router.local) or private network numbers (like 192.168.0.1); an image that needs a login simply stays covered. The extension itself never saves the images: they are checked in memory on your device and never uploaded or sent anywhere. The repeat request goes through the browser's ordinary cache, so the browser may keep the image there like any image it loads. So that an image loaded from an address is not checked twice, even after the browser restarts, what the engine found in it is kept: the people it saw and the gender of each face, each with a confidence score, the image's width and height, and when it was checked — not the image, and not its address. Reduced copies (video frames, images the page drew itself) are checked each time and never kept. This record is filed under a fingerprint (SHA-256) of the image's bytes together with the name of the site it was shown on, so that no site can tell what was checked on another, in the extension's own storage on your device (IndexedDB), for at most 5,000 images; beyond that, the oldest are dropped. It stays after Smart mode is turned off. The “Forget checked images” button on the Images tab erases it, and so does removing the extension. While the engine is running, recent results are also held in memory under the image's address. A page in a private window neither uses nor adds to what is kept, and the repeat request for its images is not stored in the browser's cache. (On Firefox, desktop and Android, the same engine sits in the extension's background page, without the offscreen permission; its models load only at the first check.)
- content_scripts on youtube.com — a script that is always part of the extension loads on every www.youtube.com and m.youtube.com page, in every mode, and also in YouTube players embedded in other sites (there it runs only inside the player's own frame, never in the site around it). It reads your YouTube settings and whether blocking is paused, and checks the address of the YouTube page you are on. While “Block YouTube ads” is on (and blocking is not paused), it hides YouTube's ad cards in the feed, search and beside videos, and while the player shows an ad it hides the ad's picture, turns its sound off, plays it at 16× to its end and presses YouTube's own Skip button, then puts the sound and speed back. If you turn on any “Tidy YouTube” switch, in every mode, it adds a stylesheet that hides the comments, the suggested videos (beside a video and at its end) or the home page feed, and, for “No autoplay”, it switches YouTube's own “autoplay next” control off once for each video. Apart from that, in “No limits” and “Block entirely”, and while blocking is paused, it does nothing. In “No Shorts” it sends a Short to the block page when one opens. “Approved channels only” does the same with Shorts; on a video page, and in an embedded player, it also hides and pauses the player, reads the video's channel from the page, together with the id of the video the page names (so that the channel belongs to the video on screen), and compares it with your approved channels: a video from another channel, or one whose channel cannot be read within 8 seconds, goes to the block page — in an embedded player, the block page replaces the player inside its frame. An approved embedded video waits for its own play button. On other YouTube pages (the home feed, channel pages, the miniplayer) videos stay paused and hidden. When it sends a video to the block page because its channel is not approved, it hands the channel's name and links (its @handle or channel address) and the video's address to the extension's own background, which keeps them in the browser's session memory, for that tab, until a parent approves the channel there with the parent password, or the browser closes. All of this happens on your device; nothing is sent anywhere.
- Open tabs (no extra permission) — the toolbar popup reads the address of the tab you're on, only while it is open, to offer its buttons for that site (such as “Blur all images on this site” and “Turn the word filter off on this site”); only the site name you choose is saved. When the web closes — the daily time runs out, downtime starts, Shabbat or Yom Tov begins, or the browser opens with more than one profile — and after an install or update, the extension finds the open web tabs to reload them or show the reload notice. When the “Who's browsing?” screen opens, the page you were heading to rides along in that screen's own address so you land back on it, and once a profile is picked, every tab showing that screen goes back to its own page. The time's-up and downtime pages carry the page you were opening in their own address the same way (after “#”), so the child can go back to it (from the time's-up page, once a parent adds time); that address is not stored. The Shabbat page does the same (after “#”); that address is not stored either. Apart from the site names you choose to save, the site names in the list of recent blocks, and a blocked YouTube video's address (in session memory, until a parent approves its channel or the browser closes), no address is ever stored.
Third parties
None. The extension uses no outside service. The open-source libraries and models inside it (TensorFlow.js, face-api, COCO-SSD and YAMNet) run inside the extension and send nothing; each is listed in the THIRD_PARTY_NOTICES.md file that ships with the extension. Apart from the Smart-mode image check, which goes back to the same address the page already loaded, the extension contacts no site, and no fonts are fetched from Google or anywhere else.
Store policy compliance
Kosher Browser complies with the Chrome Web Store User Data Policy, including the
Limited Use requirements. On Firefox it follows Mozilla's add-on policies, and the add-on declares to Mozilla that it collects no data (data_collection_permissions: none).
Any user data the extension touches is used solely
to provide the user-facing feature (blocking sites, focus timer, etc.) and is never transferred
to third parties, used for advertising, used to improve unrelated products, or read by any
human at our end — because there is no server-side component.
Cookies
None.
Children
A parent installs and sets up Kosher Browser. Children can browse under a child profile the parent creates: the extension shows them a “Who's browsing?” screen and, in Whitelist mode (on for new “Ages 4–8” profiles), a page of the sites approved for them. Nothing is collected from anyone, including children: everything in a child's profile — name, avatar, age band, filters, limits and minutes used — stays on this device and is never sent anywhere.
Changes
When this policy changes, the date at the top changes with it, and the new version is published at the same address. If we ever add an optional cloud-sync feature, it will be strictly opt-in and accompanied by an updated version of this policy that explains what is uploaded and where. The default forever is local.
Contact
Questions, security reports, or bug reports: dayanimo@gmail.com.