Before you begin

Planning guide: FeedHush has no released Chrome extension, Web Store ID or active managed filtering. The native Mac app’s controls are limited to its own app; it does not configure system-wide Screen Time.

Give the child a separate standard Mac account. The parent keeps administrator credentials, Apple Account recovery and any device-management credentials. Check for existing management before changing the Mac.

1. Choose who will manage Chrome policy

Google documents Mac Chrome policies using managed preferences and configuration profiles. The Chrome preference domain is com.google.Chrome. Use a device administrator to review the deployment method and effective scope; a profile file on disk is not evidence that Chrome is managed.

For a stronger device-management setup, the management service must also control enrollment and profile removal. A manually installed profile is not equivalent to that setup. Chrome Enterprise Core is a separate browser-management service with its own enrollment requirements; it does not block Safari or other Mac apps.

FeedHush does not enroll your Mac in management, provide an MDM service or prevent profile removal. An organization-managed Mac needs its existing administrator’s involvement.

2. Review the Chrome baseline

Plan mandatory machine policies for the intended Web Store release: force-install through ExtensionSettings, disable guest mode and adding profiles, disable private windows, and restrict developer tools. Review all existing profiles and conflicting policy sources.

The policy planner shows the proposed preferences and changes. Its JSON download is a review document, not an installable configuration profile. Do not paste it into a profile installer.

Some off-store extension installations have additional management requirements. A developer build is not a substitute for an approved release or a tested distribution method.

3. Configure device app restrictions separately

Use Apple Screen Time or your chosen app-control tool to set the family’s device rules. Verify whether the exact version can block Safari and each other browser continuously, including after restart. A time allowance is not automatically a permanent app block.

Also consider native social apps, installed web apps, other user accounts and new software. A standard account and App Store restrictions alone do not prove that every app downloaded from the web is prevented from running. If your tool cannot enforce the required restriction, do not mark this setup complete.

Keep allowed websites usable in Chrome. A device-wide domain block may also stop them opening in FeedHush or Chrome.

4. Test the whole setup

  1. After separate policy deployment, restart Chrome and check chrome://policy for expected values, mandatory level, machine scope and errors.
  2. Confirm the intended extension cannot be removed or disabled in Chrome.
  3. Try guest, private windows, all existing profiles and adding a profile.
  4. From the child’s standard account, attempt to open Safari, Firefox, Edge and any other installed browser. Check permitted test apps downloaded outside the App Store.
  5. Confirm the child cannot change the relevant device restrictions or remove the management responsible for them through ordinary account access.
  6. Restart the Mac and repeat, including schoolwork and recovery access.

FeedHush’s signed settings and filtering must also work in a supported release before you can rely on them. Neither is established by this guide.