Keyholder approval means your accountability partner approves or denies each sensitive change in GuardianBlock from their own account, with multi-factor authentication. There is no password for them to hold and nothing for them to type on your PC.
A keyholder decision gates the changes that would weaken protection. Everything else stays yours.
Adding protection never needs approval. You can add a Custom Block or strengthen protection on your own at any time.
A decision is an authenticated act inside your keyholder's own account. It is never a reply, a forwarded link, or an assumption made from silence.
Deactivation is a sequence, not a switch. Each step has to finish before the next one starts.
You request deactivation from the GuardianBlock web app, the tray app, or the uninstaller.
Your keyholder is notified and approves or denies.
If approved, a 24-hour cooling-off period runs.
No authorization exists yet and nothing on your PC changes while the period runs.
After cooling-off, GuardianBlock issues a signed, single-use authorization for that one device. It is valid for 48 hours.
The authorization is single-use, tied to that one device, and expires when the window closes.
The uninstaller checks that authorization on your PC before removing protection. Windows still asks for the normal administrator confirmation to uninstall software.
Approval by itself does not turn anything off. The decision, the cooling-off period, the signed authorization, and the uninstall are four separate steps.
If a blocked site is one you genuinely need, you can send an Emergency allow request with the site and your reason. Your keyholder approves or denies it. Gambling sites and their funding routes cannot be allowed this way, even with approval.
A keyholder's refusal or absence never leaves you locked out for good. Replacing a keyholder with their approval takes effect 24 hours after the new keyholder accepts and sets up MFA. Without their cooperation, GuardianBlock uses a seven-day identity-verified review. Documented safety, abuse, account-loss, or wrong-person cases can be expedited by support.
The role is deliberately narrow. Holding the key is not holding your computer.
No. Your keyholder never receives a password, a code, or anything to type on your PC. They approve or deny requests inside their own signed-in GuardianBlock account with multi-factor authentication.
No. They approve or deny a request that you make. Nothing is removed remotely, and GuardianBlock does not run server-triggered removal commands.
Deactivation or keyholder replacement without their cooperation goes through the seven-day identity-verified review, and documented safety, abuse, account-loss, or wrong-person cases can be expedited by support. Refusal or silence never creates an indefinite lock.
No. Each keyholder is a separate person with their own verified account and multi-factor authentication. GuardianBlock is built for one protected adult and one accountability partner.
Keyholder approval works because the decision, the wait, and the signed authorization are separate things. Pick the person while the choice is calm, not during the moment you built this for.