Prepare recovery before enforcement

Keep parent account recovery, administrator credentials and device-management ownership accessible to the parent. Record original settings, the tool that owns each one and a way to reach required communication or schoolwork. Test recovery while you still have access.

Use a dedicated child device where practical: mandatory machine-level Chrome policy can affect an adult’s profiles on the same computer.

Undo Chrome policy carefully

  1. Sign in as the authorized parent or administrator and identify which policy source applied the change.
  2. Compare current values with your recorded original values and the changes you made.
  3. Restore only those changed values through the owning management tool. Preserve unrelated browser or organization policies.
  4. Restart Chrome, reload chrome://policy and verify the result.
  5. Confirm needed access works and review the remaining device restrictions separately.

Removing a force-install rule can uninstall the extension. Do not delete the whole Chrome policy key or remove all management profiles as a shortcut. The policy planner provides a snapshot for review, not an automatic rollback script.

Device restrictions are a separate change

Use Apple, Microsoft or your app-control provider’s parent recovery process for their restrictions. Removing a FeedHush device record does not remove Chrome policy, Screen Time or Qustodio. Removing a Chrome policy does not change the parent’s saved household settings.

On an organization-managed device, contact its administrator. A family guide is not authorization to remove someone else’s device management.

If credentials are lost

Use the account provider’s official recovery process. Do not share a child’s or parent’s password with someone offering an unofficial unlock. FeedHush does not currently offer public account recovery or direct support.

After recovery, recheck device records, parent access and the setup checklist. A reinstall or reset does not prove previous protection has returned.