A Gambling Blocker Where Someone Else Holds the Key

The key means authority, not a password

GuardianBlock has no reusable password for someone to hold.

“Someone else holds the key” is a useful metaphor, but only if the mechanism stays clear. Your chosen keyholder has ongoing approval authority in GuardianBlock. They use their own authenticated account and multi-factor authentication to approve or deny a specific eligible exit or other sensitive change. They do not receive your Windows administrator credentials, enter a secret on your computer, or gain remote control of the device.

Approval begins a 24-hour cooling-off path. It does not immediately turn protection off. After that period clears, the device can receive a signed, single-use authorization for the supported local exit. That authorization is tied to the device and installation. Windows administrator elevation remains a separate local requirement. The human decision, the delay, the signed authorization, and the machine-level action are four different steps.

“

The keyholder does not keep an unlock code. They keep their place in the decision.

That distinction matters because a one-time password handoff creates a reusable route around the commitment. Continuing authority requires a new, authenticated decision about the specific request in front of the keyholder. It also keeps the relationship adult-to-adult: one person opted into a boundary, and another person agreed to hold that boundary without becoming the owner of the computer or the owner of the first person's choices.

1. Does it appear in Programs?

Yes. GuardianBlock's signed Windows package keeps one visible maintenance entry in Programs/Installed apps rather than hiding itself. That is a trust signal, not a weakness. Voluntary accountability software should identify itself honestly, use the normal Windows installation surface, and give the person a supported place to begin a legitimate maintenance or exit request.

A visible entry does not mean the active-protection path collapses into an ordinary click-through uninstall. On that path, the guard checks whether the required deactivation authorization exists. If it does not, the person can request deactivation, view an existing request, or open the documented support and recovery route.

2. Can you stop it, and does someone get told?

Stopping protection is a supported request, not a quiet switch on the device. The supported exit path runs through chosen-human approval and the cooling-off period, and the health model makes a supported request, an unexpected stop, an integrity problem, and a quiet device different states instead of treating every disappearance as normal. The limitations page states the supported scope in full.

For an enrolled device with reporting history, a loss of expected health signals can move the device to offline or needs-attention rather than leave it looking healthy. But that state does not prove why the device went quiet. A service failure, connectivity problem, powered-off computer, or deliberate action can look similar from a distance. The honest statement is that the state needs attention, not that the system has diagnosed the cause.

A recorded product event is also not the same as an external message reaching a person. Provider acceptance or delivery status is an operational transport state, not proof that the keyholder read the message. Ask any product in this category whether it can distinguish event creation, message delivery, and authenticated human acknowledgement. Those are three different claims.

3. Does it inspect page content or intercept traffic, or is it browser policy?

GuardianBlock is designed around supported-browser policy, signed browser extensions, and an on-device Windows service. It is not a DNS, VPN, proxy, or traffic-interception layer. The browser integrations are designed not to read page content or browsing history, and the keyholder does not receive a feed of sites visited, page titles, screenshots, keystrokes, private files, or every blocked attempt.

The product does observe the narrower information needed to operate the accountability model: enrollment and protection state, browser-integration health, policy status, explicit requests, and bounded integrity or offline signals. “No browsing feed” does not mean “observes nothing.” It means the data boundary is protection health and specific decisions rather than general monitoring of an adult's online life.

That architecture also should not be inflated into a universal compatibility promise. GuardianBlock does not alter DNS, VPN, firewall, proxy, or route settings. That design reduces one class of collision, but it does not establish compatibility with every employer policy, managed device, browser, VPN, or work setup. GuardianBlock supports eligible personal, unmanaged Windows 11 Home or Pro x64 devices, in Chrome, Edge, and Firefox. Shared computers and employer-, domain-, MDM-, or IT-managed devices are outside that scope.

4. Does the second person hold a password once, or approve each exit with cooling-off?

They approve a specific eligible exit through their own account; they do not hold a password once. The keyholder sees which person and device are involved, what action is requested, and what the timing and consequences are. Recent multi-factor authentication is part of that decision. An email inbox by itself is not approval, silence is not approval, and the keyholder never needs to type a credential into the protected computer.

If the keyholder approves, the 24-hour cooling-off period gives the earlier commitment time to outlast the immediate request. Approval still does not uninstall anything. The supported path must reach the later signed authorization and local Windows action. If the keyholder is unavailable, unsafe, or no longer suitable, documented support and recovery paths are designed to prevent refusal from creating an indefinite lock. Support is business-hours email, not 24/7 service, remote control, or a reusable unlock secret.

That is ongoing authenticated approval authority: a continuing role in defined GuardianBlock decisions, not permanent custody of a master secret. It is deliberately narrower than ownership, surveillance, or remote administration. The keyholder can approve or deny the request GuardianBlock presents. They cannot operate the computer, inspect private activity, or make every life decision for the protected adult.

5. Does anyone find out if it was never installed or goes quiet?

These are two different cases. If setup never reaches installation and enrollment, there is no enrolled device with heartbeat history to report. Incomplete setup should remain visibly incomplete; GuardianBlock should not label it protected. But absence alone cannot prove that a download was never installed, explain why setup stopped, or automatically establish what happened on a computer.

If a device was enrolled and later stops reporting, the missing expected signals can support an offline or needs-attention state. That state can be visible in authenticated account views, including the keyholder's view, as a signal that protection status needs attention. It still may not reveal the cause. Account visibility is not an external notice, and even when a related notice has a provider delivery state, delivery is not proof of reading. A truthful accountability product preserves each of those uncertainties instead of collapsing them into certainty.

What the model can honestly promise

The useful promise is not that software can cover every route or determine what another adult is thinking. It is that a person can make a commitment in a calmer moment, appoint someone they trust to hold ongoing approval authority, and use a system that keeps supported exits, health changes, and recovery routes explicit rather than quietly collapsing into one reusable secret.

That can create meaningful friction and a clearer conversation. It is still voluntary accountability software, not treatment, crisis support, or a guaranteed outcome. The setup that holds up is one where both adults understand the authority, the privacy boundary, the notification limits, and the humane recovery route before protection begins.

GuardianBlock for Windows will be available soon. The privacy summary, the limitations page, and the install and removal path set out the same model this article describes, in the detail a keyholder and a protected adult should read together.