Frequently asked questions.

Early access is intended for personal, unmanaged Windows 11 devices with Chrome, Edge, and Firefox in scope. Browser behavior, installer behavior, and health signals remain evidence-gated before external launch.

Chrome, Edge, and Firefox are the intended early-access browser scope. Unsupported and portable browsers remain outside early-access blocking scope; device health and partner notices should surface relevant signals where feasible and proven.

Early access targets Windows 11 (Home/Pro, x64) with Chrome, Edge, and Firefox. Additional platforms are planned but not part of the current scope.

An accountability partner is what turns a blocker into real accountability. They authorize sensitive changes, receive tamper and request alerts, and make it far harder to quietly undo protection in a weak moment. The relationship is consent-based on both sides.

You can request an allow for a specific site. Your accountability partner is notified and can approve it when the active policy classifies the block as eligible. Hard never-allow gambling and funding-route protections cannot be overridden by an emergency allow.

Yes. You can add your own sites to the blocklist. Removing protected sites is a partner-accountable change, not a silent one-click toggle.

No. Your accountability partner sees explicit requests and protection health — never a list of the sites you visit. There is no browsing-history feed.

There is a recovery path so you're never permanently locked out if an accountability partner becomes unavailable. It's intentionally deliberate so it can't be used as a quick bypass.

GuardianBlock is designed not to alter DNS, hosts, VPN, firewall, proxy, routes, adapters, SMB mappings, mapped drives, WSL mounts, or work-network configuration. It uses browser integrations and a local Windows service, with clean-VM evidence required before stronger claims. The no-DNS/VPN/firewall trust page explains the boundary.

GuardianBlock is designed not to alter DNS, hosts, VPN, firewall, proxy, routes, adapters, SMB mappings, mapped drives, WSL mounts, or work-network configuration. Clean-VM pre/post evidence is still required before stronger work-network claims; the limitations page and no-DNS/VPN/firewall trust page explain the current posture.

Private and incognito behaviour varies by browser. Coverage is tested and documented browser by browser; some private modes require the extension to be explicitly enabled.

Yes. You can cancel at any time. Because this is voluntary self-restriction, winding down protection is a deliberate, partner-visible process rather than an instant disable.

GuardianBlock includes space for region-aware helplines, self-exclusion resources, and peer-support links alongside the product workflow.