Before you begin

Planning guide: FeedHush has no released extension, published Web Store ID or working managed filtering runtime. Do not substitute another extension or a developer-build ID to make the setup look complete.

  • A parent controls administrator credentials and recovery.
  • The child uses a separate standard Windows account.
  • The device is yours to manage. Ask its administrator about any existing work or school management.
  • You have selected app controls that work on the device’s Windows version and edition.

1. Plan machine-level Chrome policy

Google supports Chrome policy on Windows through administrative templates or registry-based management. The intended family configuration uses mandatory machine policy so a child cannot simply switch Chrome profiles to avoid a user-only setting. It can affect adult profiles on the same computer too.

Have the device administrator review these values against existing policy sources:

  • ExtensionSettings: the verified release ID with installation_mode: force_installed and Google’s Web Store update URL.
  • BrowserGuestModeEnabled: false and BrowserAddPersonEnabled: false.
  • IncognitoModeAvailability: 1 to disable private windows.
  • DeveloperToolsAvailability: 2 to restrict developer tools.

These settings are a baseline, not a complete hardening policy. Existing profiles, policy precedence, extension host permissions and other browser installations still need review. Our policy planner creates a review file without applying it.

2. Restrict alternate browsers and apps

Configure your device app-control tool to restrict Edge, Firefox and other unapproved browsers, native social apps and newly introduced software. Test existing installations and apps installed in the child’s own folders. Hiding shortcuts or choosing Chrome as the default browser does not stop another app opening.

Windows application control can provide a stricter approach, but availability and deployment depend on the Windows edition and tool. App Control can affect the whole device; AppLocker has different scoping options. These require a separate reviewed deployment and recovery plan. FeedHush does not generate or install those policies.

Microsoft Family Safety’s web filtering is designed around Edge. Do not assume enabling it will preserve a Chrome-first setup. Read Microsoft’s requirements before combining tools.

3. Verify from the child’s account

  1. After separately deploying reviewed policy, fully quit and reopen Chrome. Open chrome://policy, reload policies, and check expected values, mandatory level, machine scope, and any errors or conflicts.
  2. Confirm the intended extension is actually installed and cannot be disabled or removed through Chrome.
  3. Try guest mode, a new profile, every existing profile and a private window.
  4. Try Edge, Firefox, another installed browser and a permitted test app installed without administrator rights.
  5. Check that required schoolwork and communication still work, then repeat after a restart.

Do not record “protected” until signed parent settings and real filtering also pass in a supported FeedHush release. Those checks cannot pass with the current build.

4. Keep a way back

Record original policy values and which tool owns them. Change only the settings you intended. Do not delete the entire Chrome policy registry key or remove unrelated management. See recovery and removing a setup.