Four jobs, four checks
| Layer | Its job | What it cannot prove |
|---|---|---|
| Parent settings | Authorize household rules and requests. | That the device received or applied them. |
| Chrome policy | Force-install an extension and restrict Chrome’s guest, profile and private browsing options. | That filtering works, or that another browser is blocked. |
| Device app controls | Restrict other browsers, native social apps and unwanted software. | That an allowed social page has its feed filtered. |
| Website rules | Allow or block access to entire sites. | Which feed elements remain visible on an allowed page. |
FeedHush’s filtering and managed-device runtime are unfinished. You can plan these layers now, but there is no complete FeedHush protection setup to enable today.
What “managed Chrome” means
Google supports an extension installation mode that prevents normal removal or disabling inside Chrome. It requires correctly applied policy. Installing an extension normally, loading an unpacked developer build, or signing in to a regular Google account does not establish that protection.
A Chrome policy is not an operating-system app rule. Safari, Firefox, Edge, portable browsers and apps with their own web views need separate consideration. Adult administrator access, removable management, device resets and other devices remain meaningful limits.
Avoid a conflicting website rule
Suppose you want a child to use an allowed social website in managed Chrome while preventing access in Safari. A device-wide block on that domain may also block Chrome. A device-wide allow rule may let the same site open unfiltered in another allowed browser.
The intended setup is an approved browser plus effective restrictions on other access paths. Do not assume a website allow rule means “allow only through FeedHush.” Test both the approved path and the blocked path.
Choose a level you can verify
For a family computer, use parent-controlled administrator credentials, a standard child account, managed Chrome and a separately verified app-control tool. A standard account alone is not an app allowlist: software can sometimes run without a system-wide installation.
A more restrictive setup can require device management and application control configured by an administrator. FeedHush does not supply that service. Organization management is a separate deployment model, not a family account feature.
If a route remains open, treat the setup as incomplete. Use the verification checklist to record exactly what passed.