Record the setup you actually tested

Write down the operating system, browser, parental-control tool and FeedHush versions, the child account, the date, and who owns each setting. Use a harmless test website and test account. Keep passwords, pairing codes and private messages out of notes and screenshots.

Current result: incomplete. FeedHush filtering and its complete managed runtime are not available. You can test separate vendor controls now, but cannot pass the full FeedHush checklist.

1. Parent authority

  • The child cannot sign in as the parent or use administrator or recovery credentials.
  • The child cannot edit household rules or approve their own requests.
  • Unfamiliar devices are reviewed; device removal and recovery are understood.
  • The parent can restore access without giving the child permanent administrator rights.

2. Chrome policy

  • Expected policies are effective at mandatory machine scope with no errors or unresolved conflicts.
  • The correct extension is installed; Chrome’s remove and disable controls are unavailable.
  • Guest, private windows and adding a profile are unavailable.
  • Every existing Chrome profile has been checked.
  • Developer tools and separate browser installations have been assessed.

A “managed by your organization” label alone does not pass these checks. Review the actual values and behavior.

3. Other access paths

  • Safari on Mac, Edge on Windows, Firefox and every other installed browser obey the chosen restrictions.
  • User-installed and portable apps cannot provide an unapproved path.
  • Native social apps, installed web apps and apps with embedded browsing have been considered.
  • Other local accounts and any guest OS account are controlled.
  • Allowed schoolwork and communication remain usable.

If a supported alternative browser can open an allowed social site without FeedHush, the setup does not meet the intended restriction. Other devices and networks require their own plan.

4. FeedHush behavior — awaiting a supported release

  • The client receives and verifies the latest signed parent settings.
  • Real supported feed elements follow the configured rules on reload and in-page navigation.
  • Offline, expired, invalid and older settings do not silently open access.
  • Revocation and interrupted updates produce the expected restricted or recovery state.
  • A request approval only grants the intended scope and duration when that feature is released.

These are release requirements, not claims about current behavior. Installation and successful pairing cannot substitute for them.

5. Restart and revisit

Repeat the checks after restarting, after browser or OS updates, and after changes to accounts, profiles, apps or management. Record failures explicitly. A partial pass means partial coverage; do not label it tamper-proof or fully locked.