Accountability alerts.

Your keyholder hears when protection is paused, removed, or interfered with — never what you were browsing.

What raises an alert.

Alerts follow protection, not behaviour. Each one names a change to protection or a request you chose to send.

  1. Protection paused, removed, or interfered with
  2. An unapproved browser launch that was blocked
  3. Your Emergency allow requests and deactivation requests
  4. A change to where alerts are sent
How keyholder approval works

Offline is a status, not an alert

Your PC checks in with GuardianBlock while it is on and online. When check-ins stop, your keyholder sees Offline and the time of the last check-in, and nobody is alerted: a sleeping or switched-off PC goes quiet too. Alerts follow the changes to protection that a device reports.

Silence is never approval

An alert is information for your keyholder. It never approves or denies anything on its own, and no alert can turn protection off.

Protection health, in plain words.

A state, not a record of what you were doing. The tray app and the dashboard show the same one.

See exactly what you share
Protected
The service, browser integrations, and policy are all in place.
Needs attention
Something needs a look — for example, a browser integration that is missing.
Offline
The PC has not checked in with GuardianBlock recently.
Tamper detected
Protection was interfered with outside the supported path.
Unapproved browser attention
An unapproved browser launch was blocked, or browser protection needs attention.
Guardian pending
Your keyholder has not accepted yet.
Rolled back
An update failed and the last good protection release was restored.

Common questions.

Alerts never carry your browsing, searches, or screen.

Install and the supported way to turn it off

  • What happens if I try to remove GuardianBlock?

    Your keyholder hears when protection is paused, removed, or interfered with — never what you were browsing. The supported way to turn protection off is a request your keyholder approves or denies, followed by a cooling-off period, and the install and uninstall page describes that path.

  • Does my partner know if I uninstall it?

    Turning protection off through the supported path starts with a request your keyholder approves or denies, so they know before anything is removed. Removal or interference outside that path shows up as Tamper detected when the device reports it, and that report is what your keyholder is alerted to.

  • Does my partner see which sites I try to open?

    No. Your keyholder sees protection health, alerts, the Custom Blocks you add, and the requests you choose to send — an Emergency allow request carries the site and the reason you wrote. The pages you open, and the ones a block stops, are not shown to them.

  • How fast is an alert?

    An alert follows the evidence: it is raised when the device reports a change to protection, never because a PC went quiet. GuardianBlock reports what the device reported rather than promising a delivery time.

Accountability, not a feed.

Alerts exist so your keyholder can act when protection changes.

Start GuardianBlockLimits and recovery