Bypass-Proof YouTube Parental Controls: What It Means on Each Device

TL;DR: Every parental control that lives only inside an app or a browser can be switched off by the child who uses it. The only protection that holds is the one your child has no rights to touch: the operating system's own account and policy system, controlled by your password. WhitelistVideo builds on that layer on Windows, macOS, iOS, Android and managed Chromebooks, then does the one job the operating system is bad at: deciding which YouTube videos play.

Why parental controls keep getting switched off

The discovery usually happens by accident. You open the tablet to check something and the filter you set up in March has been off since April. No alert, no confrontation. Your child found the toggle, and the toggle did what toggles do.

This is not a failure of one product. It is a design flaw shared by an entire category. Restricted Mode is a switch in YouTube's own settings, on the same screen the child uses to change their profile picture. YouTube Kids is a separate app that a nine-year-old abandons the moment they learn the regular app exists. A filter extension that a child can disable from the Extensions page is a filter for exactly as long as the child chooses to keep it.

The common thread: the control lives inside the thing it is supposed to control, at a permission level the child already has. Anything you can install with a child's rights, a child can remove with the same rights.

The principle: protection has to live where your child has no rights

Every modern operating system already ships a layer built for exactly this problem. Windows and macOS separate Administrator accounts from Standard accounts. Apple's Screen Time and Family Controls are gated by the parent's Apple Account. Google Family Link is driven by a supervised child account that only the parent can change. ChromeOS answers to whoever manages the device.

These layers were designed so that one person's decision cannot be undone by another person with fewer rights. That is the property a parental control needs, and it is the property most parental-control apps ignore. They try to rebuild it with tricks: VPN tunnels, Accessibility-service overlays, Device Admin hooks. Every one of those can be turned off in Settings by the child, because the child owns the account they run under.

WhitelistVideo does not fight the operating system. It enlists it. On each platform, the parent completes one short OS-level step that only a parent can complete, and WhitelistVideo checks that the step is in place before it reports the device as protected.

Division of labour: the OS locks the door, WhitelistVideo picks the videos

An operating system is good at one thing here: deciding which apps and settings a given user may touch. It is hopeless at deciding whether a specific YouTube video is right for your eleven-year-old. Family Link and Screen Time can block YouTube entirely or allow it entirely. Neither can allow one channel and refuse another, and Family Link only lets you block a channel after your child has already watched it.

WhitelistVideo is the opposite. Its content layer is a Chrome and Edge extension on computers, a child app on iPhone, iPad, Android and Android TV, all reading one parent-controlled whitelist that syncs in real time. Everything on YouTube is blocked by default. Only channels and videos you approve will play, and your child can request a new channel from inside the app instead of hunting for a workaround.

So the split is clean. The OS decides who may change what. WhitelistVideo decides what plays. Neither is asked to do the other's job.

What "bypass-proof" means, and what it does not

Bypass-proof means the child cannot remove or disable the protection without the parent's credentials. On a computer that is the administrator password. On an iPhone it is the parent's Apple Account password. On Android it is the Family Link parent login. On a managed Chromebook it is the Google Admin console.

It does not mean "no configuration required". On every platform there is a one-time setup step in the operating system, usually five to ten minutes, and it is what makes the whitelist hold. It also does not mean a universal guarantee against every conceivable trick. A child who knows the admin password is, as far as the device is concerned, the parent. The sections below say plainly, for each platform, what your child would need to hold in order to undo the protection.

Windows: managed browser policy plus a watchdog

Windows already knows how to stop a Standard user from changing managed settings. Chrome and Edge both obey enterprise policy stored in registry keys that only an Administrator can write. WhitelistVideo's Windows installer writes the right policy and then keeps a guard on it.

What the installer sets up

The installer runs per machine and requires administrator approval (the familiar UAC prompt). You choose which Windows account belongs to your child. Protection is applied per account, and administrator accounts cannot be protected, which is the correct behaviour: the child must be a Standard user. For that account, the installer writes Chrome and Edge policy so that:

• The WhitelistVideo extension is force-installed, pinned to the toolbar, and active in Incognito. It cannot be removed or switched off from the Extensions page.
• All other extensions are blocked from being added, which closes the "install a second extension to break the first" route and ad-blocker or user-script tricks.
• Developer Tools are disabled and the chrome://extensions and DevTools URLs are blocked.
• Incognito, Guest mode and adding new browser profiles are disabled. There is no fresh profile without the extension.
• YouTube Restricted Mode is forced to Strict as a second net beneath the whitelist.
• Extension auto-update is forced on, so a security fix cannot be held back.

Chrome documents these controls in its enterprise policy list; they are the same mechanisms schools and companies use to manage thousands of machines.

The watchdog

Policy that can be deleted is not protection. So the installer also adds a Windows service, WhitelistVideo Watchdog, running as the system account and starting with the machine. It watches the policy registry keys for changes and re-applies them within about a second if a child account edits or deletes them, with a periodic sweep as a backstop. Removing the service or uninstalling WhitelistVideo requires administrator elevation.

Who can undo it, and the honest boundary

An Administrator, and only an Administrator. If your child has the admin password, no software on earth can protect them, so the recommended setup is simple: child on a Standard account, parent holds the only admin password. The installer covers Chrome and Edge. Firefox and other browsers are not filtered, and the right tool for that is the one already on the device: block or limit them with Microsoft Family Safety, or simply do not install them on the child account. Full steps are in the Windows advanced protection guide.

Mac: managed preferences, installed from your child's account

macOS has the same Standard-versus-Administrator split, plus a folder called Managed Preferences that only the system can write to. Chrome and Edge treat what they find there as enterprise policy the user cannot override. That folder is where WhitelistVideo's Mac installer puts its rules.

What the installer does

The package refuses to run from an administrator account. The message is blunt on purpose: "WhitelistVideo must be installed from your child's account, not an admin account." That forces the correct model. Your child is a Standard user, and you type the admin password once to authorise the install. The installer then writes system-wide Chrome and Edge policy files so that the extension is force-installed and pinned, all other extensions are blocked, Incognito and Guest mode and new profiles are disabled, Developer Tools are off, and a minimum extension version is enforced so an old build cannot be pinned to dodge a fix. A signed configuration profile exists as an alternative way to deploy the same policies.

Who can undo it, and the honest boundary

Uninstalling requires administrator privileges. A Standard child account cannot remove it. As on Windows, the coverage is Chrome and Edge. Safari and Firefox are not filtered, and this is where the division of labour shows up in practice: macOS Screen Time's App Limits and Allowed Apps are built to block whole applications, so you use Screen Time to close Safari and Firefox on the child account, and WhitelistVideo to control what plays in Chrome. The Mac advanced protection guide walks through both.

iPhone and iPad: Apple Family Controls with a Child Apple ID

Apple gives third-party apps exactly one sanctioned way to restrict content system-wide: the Family Controls framework behind Screen Time. WhitelistVideo's iOS child app plugs directly into it, and the design of that framework is what makes the protection hard to undo.

How it works

• On first launch you approve Family Controls access. The app requests the child-account authorization, the mode Apple reserves for a Child Apple ID in Family Sharing. In that mode, revoking WhitelistVideo's Screen Time access in Settings asks for the parent's Apple Account email and password, not the four-digit Screen Time passcode. A child cannot do it.
• Once authorised, the app applies a system-wide web filter that blocks youtube.com, m.youtube.com, youtu.be and music.youtube.com in every other browser on the device whenever your child leaves the WhitelistVideo app. Inside the app, the filter lifts and YouTube plays through the whitelisted view. Net effect: YouTube exists on that iPhone only through WhitelistVideo.
• The app checks for the native YouTube app and will not complete setup for a child account while it is still installed, because the native app would defeat filtering entirely. You remove it once, then set Screen Time's "Deleting Apps" and "Installing Apps" to Don't Allow (or Ask to Buy) so it cannot come back.
• A parent PIN on the child's device gates every protection setting. It is PIN only, with a lockout after failed attempts, and deliberately not Face ID, because the face enrolled on a child's phone is the child's.
• Every time the app comes to the foreground it re-checks its authorisation. If access has been revoked, a persistent banner appears with a one-tap "Allow" that reopens the consent step. Protection state is verified, never assumed.

Who can undo it, and the honest boundary

The holder of the parent Apple Account. That strength depends on one setup choice: your child needs a Child Apple ID in Family Sharing. Without one (Apple calls it Individual mode), revocation needs only the Screen Time passcode, so for bypass-proof protection on iPhone, set up the Child Apple ID first. Two more things worth knowing: Apple allows only one third-party Family Controls app per device, so do not stack a second Screen Time app, and do not add youtube.com to Screen Time's own "Never Allow" list, because a blanket block also stops approved videos loading inside WhitelistVideo. The app detects that state and tells you. Step-by-step instructions are in the iOS Family Controls guide.

Android phones and tablets: Google Family Link, verified

Android is the one platform where the operating system offers no API for a third-party app to switch on parental supervision. Family Link, driven by a supervised child Google Account, can block apps, stop installs and block websites in Chrome, but an app cannot request or read that supervision. So WhitelistVideo does the next best thing, and arguably the more honest one: it verifies the outcome on the device before it will report the child as protected.

The setup gates

1. Block the YouTube app (and YouTube Music and YouTube Kids) in Family Link. The WhitelistVideo child app reads the package state on the device and refuses to continue while the YouTube app is still enabled.
2. Block other browsers in Family Link. The app lists which installed apps can open https links and will not proceed while a non-allowed browser is active. Chrome stays, because Family Link supervises it.
3. Block youtube.com in Chrome through Family Link's website controls. An app cannot probe this one, so you confirm it yourself. It is the only gate that is acknowledged rather than verified, and we say so in the app.
4. Set a parent PIN on the device.

The checks do not stop after setup. If the YouTube app or a blocked browser becomes active again later, an amber bar appears immediately and the device is flagged as broken until you fix it. The gates are fail-secure: if the device check itself errors, the app treats YouTube as unblocked and shows the gate again rather than silently reporting "protected". With Family Link's "require approval" on, your child also cannot uninstall or reinstall apps without you, which is the only sanctioned way on Android to keep the child app in place.

Who can undo it, and the honest boundary

The Family Link parent. WhitelistVideo deliberately avoids Device Admin, VPN and Accessibility-service tricks on Android. A child can switch each of those off in Settings, which is why we rejected them. The Android Family Link guide covers each gate.

Chromebook, honestly: full filtering everywhere, un-removable with administrator control

Google's rules here are counter-intuitive and plenty of advice online gets them wrong, so this section is deliberately precise. The WhitelistVideo extension installs and filters YouTube completely on every Chromebook. There is no ChromeOS installer, because ChromeOS does not run the Windows or Mac installers and cannot; the enforcement layer on a Chromebook is whoever manages the device.

What Family Link does and does not do on a personal Chromebook

Family Link lets you require approval before your child installs an extension, blocks private browsing for the child account, and, if you disable Guest mode as device owner, keeps your child inside supervision. What it cannot do is stop removal. Google's own support page states it directly: "To remove a Chrome app or extension on a Chromebook, a parent doesn't need to give permission. To re-add, a parent needs to approve it again." Family Link also cannot force-install an extension. So with Family Link alone, WhitelistVideo is tamper-evident (the parent dashboard shows the device has stopped syncing, and re-adding needs your approval) rather than tamper-proof. Our Chromebook parental controls guide covers the Family Link setup in detail.

The bypass-proof path: device management

Force-install on ChromeOS comes from Google Admin console policy, the same mechanism the Windows and Mac installers use. There are two routes to it:

• School-issued Chromebooks are already enrolled in the school's Admin console. The school's IT admin can force-install WhitelistVideo, block other extensions, and disable Guest mode and Incognito. You ask the school; we supply the extension ID and policy. The school-managed Chromebook guide includes a request you can forward to IT.
• Personal Chromebooks can be enrolled by you. Google sells a standalone ChromeOS Enterprise Upgrade licence at $4.17 per device per month, billed annually, so about $50 a year, bought in the Google Admin console with a free 30-day trial. It needs a Google Workspace or free Cloud Identity account, and enrolling requires a Powerwash of the device. After that you are the administrator: you force-install WhitelistVideo and lock the device down the same way a school does, and the child's account cannot remove it.

The one-line version: on Chromebook, WhitelistVideo filters YouTube completely. To make it un-removable you need administrator control of the device, either your school's IT admin or a ChromeOS Enterprise Upgrade licence from Google at about $50 a year.

Android TV and Google TV: curated-only viewing

The TV app takes a different approach because the platform gives third parties nothing to enforce with. It runs in Curated Feed only: a grid of approved channels and playlists, with no search, no YouTube interface and no recommendations. There is nothing to filter because nothing unapproved is ever fetched. Parent settings sit behind a PIN, and a parent "pause" is stored on the device so it survives restarts and network loss.

The gap on a TV is the regular YouTube app. Disable it in the TV's Settings under Apps, and lock app installs with the TV's Google account controls. Because Android TV offers no OS-level enforcement for third-party apps, we position TV as curated-only viewing rather than bypass-proof. It is still the only way to give a child a full-screen YouTube on the living-room TV that shows nothing you have not approved.

Every platform on one table

Scroll horizontally to see all columns.

Fail-secure by design

Enforcement handles the child who tries to remove the protection. Fail-secure handles everything else that can go wrong: a dropped connection, a server hiccup, a half-finished setup. In every one of those cases WhitelistVideo's content layer blocks YouTube rather than letting anything through.

• If the extension cannot sync or loses contact with its background service, it enters secure mode and blocks all content.
• If a device has not been activated with a Parent Activation Code, it blocks everything.
• If it is offline and missing channel data, it blocks rather than guesses.
• Comments, downloads and Shorts are hidden unless a parent has explicitly enabled them.
• If a video's AI analysis fails, the video is blocked, not allowed.
• Search is blocked unless the server explicitly says search is allowed for that child.

Pairing is built the same way. Devices pair with a six-digit Parent Activation Code that expires in 15 minutes and works once; a replayed code is rejected server-side. Activation is refused in Incognito or Guest mode and requires a signed-in Chrome profile, so the whitelist is tied to your child's own browser profile rather than to whichever window happens to be open.

Scope: what bypass-proof covers, and what it leaves to your device

Content, not time. WhitelistVideo controls what plays, not how long. Time limits, bedtimes and schedules are already built into Screen Time, Family Link and Family Safety on every device your child owns. WhitelistVideo adds the piece those tools lack: control over the actual content.

Prevention, not surveillance. There is no watch log, no activity report and no child data collection. You approve channels and see requests, which is what COPPA compliance looks like when a product is designed for it rather than patched for it. Children get a safe YouTube without feeling spied on.

Your credentials are the perimeter. A child who holds the administrator password, the parent Apple Account or the Family Link parent login can undo any protection, because the device now believes they are you. Keep the admin account yours, put your child on a Standard account, and the rest of this article holds.

Key takeaways

• Any control installed with a child's rights can be removed with a child's rights. Protection has to live at the operating-system level, behind the parent's credentials.
• The OS decides who may change what; WhitelistVideo decides which videos play. Neither is good at the other's job.
• Windows and Mac: enterprise browser policy plus (on Windows) a watchdog service. Removal needs the administrator password.
• iPhone and iPad: Apple Family Controls with a Child Apple ID. Revocation needs the parent's Apple password.
• Android: Family Link blocks the YouTube app and other browsers; WhitelistVideo verifies it on the device and keeps checking.
• Chromebook: filtered everywhere; un-removable only with school management or a ChromeOS Enterprise Upgrade licence at about $50 a year.
• If anything breaks, YouTube is blocked, not opened.
• Start with the device your child actually uses. The per-device setup guides take five to ten minutes each, and the download page picks the right path for you.