GuardianBlock is not treatment or crisis support.
GuardianBlock does not diagnose, counsel, or replace professional help. It is accountability software for adults who have chosen a protection commitment.
What GuardianBlock can and cannot promise.
GuardianBlock is adult Windows accountability software. It is designed to add friction, visibility, and a keyholder-approved path for sensitive changes, while staying honest about what software can and cannot control.
The strongest posture still has Windows limits.
GuardianBlock works best when the protected adult is not the local administrator. When that is not true, the promise changes: more accountability and visibility, not impossible control.
A local administrator can ultimately remove software.
A person who keeps local administrator rights on a Windows PC can ultimately remove installed software. GuardianBlock treats that as a health and accountability event, not as something to overpromise away.
Unsupported browsers and devices are outside private-beta blocking scope.
The private beta is scoped to personal unmanaged Windows 11 Home or Pro x64 devices, with Chrome, Edge, and Firefox in the browser scope. Unsupported devices, alternative browsers, and portable browsers sit outside private-beta blocking scope.
The people model has boundaries too.
The keyholder is there to make sensitive changes accountable. That role is intentionally narrower than device control, therapy, or crisis care.
The keyholder approves sensitive changes; they do not remotely control your computer.
The keyholder can approve or deny specific GuardianBlock changes through the web app after authentication. They cannot operate your device, view your screen, run commands, or access private files.
Accountability cannot become an indefinite trap.
The supported model separates billing, protection, deactivation, and recovery so one stuck relationship or payment event does not become an unsafe lock.
Billing cancellation is separate from protection deactivation.
Cancelling future billing does not silently turn protection off. Protection deactivation follows the supported authorization or recovery model instead of a payment switch.
Guardian refusal cannot create an indefinite lock; support recovery exists for safety and account-loss cases.
Deny-keeps-protection is the accountability default, but GuardianBlock includes reviewed support recovery for abuse, safety, account-loss, legal, wrong-person or wrong-device, accessibility, and severe technical cases.
Last reviewed: 2026-06-29
Join with the limits visible.
GuardianBlock is strongest when the protection commitment, Windows posture, browser scope, billing separation, and recovery model are clear before you start.