Privacy Policy — Parental Controls for YouTube: Kid Mode

Chrome extension · version 1.0.0 · effective 2026-08-12

This extension collects nothing, sends nothing, and has no server. Every rule you set — the approved channel list, the daily limit, the bedtime, the PIN — is stored locally on your own computer and never transmitted. There is no account, no login, no analytics, and no way for us to see anything your child watches. This matters more here than in most extensions, because the data involved is a child's viewing.

Who we are

Filterfabrik, an independent developer. The extension is free and carries no advertising.

What the extension stores, and where

ItemWhere it livesDoes it leave your computer?
Approved channels and starter packsChrome local extension storage, on your deviceNo.
Daily time limit and bedtime windowChrome local extension storage, on your deviceNo.
Your PINChrome local extension storage, on your device, stored as a hashNo.
Activity log of blocks and allowsChrome local extension storage, on your deviceNo.
Which protections are switched onChrome local extension storage, on your deviceNo.

All of the above uses chrome.storage.local and deliberately not chrome.storage.sync, so none of it is copied to a Google account. The activity log is a fixed-size local ring that never leaves the device; it exists so a parent can see what happened, not so anyone else can. Uninstalling deletes all of it.

What we do NOT collect

Permissions, and why each one is unavoidable

PermissionWhy it is required
storageSaves your rules and PIN locally so they survive a restart. Nothing leaves the machine.
alarmsWakes the extension on a schedule so a bedtime and a daily limit can end a session without the page having to ask a server.
webNavigationLets the extension re-check a rule when YouTube navigates within its own app, which it does without loading a new page.
declarativeNetRequestWithHostAccessBlocks disallowed YouTube requests using Chrome's own rule engine. Chrome applies the rules; the extension never sees the requests, which is the more private of the two available designs.
*://*.youtube.com/*The rules only apply on YouTube, so the permission is scoped to YouTube.

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 configured by a parent and used on a child's browser. It is designed so that a child's activity stays on the device: nothing about what they watch is transmitted, and there is no remote dashboard, because a remote dashboard would require sending it.

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.