How we back our claims.
GuardianBlock is built on friction and accountability, not promises. This page describes the kinds of evidence we hold ourselves to, the checks we have actually recorded so far, and — just as honestly — what we have not proven yet.
Before a behavior becomes a claim, it has to be observed and recorded somewhere we can point back to.
Disposable-VM test matrix
We exercise the installer, the local Windows service, the tray, and the browser integrations inside disposable Windows 11 virtual machines, following a written test plan, and we record what each run actually did rather than what we hoped it would do.
Founder dogfooding
Before anyone else relies on it, the founder runs GuardianBlock on a real device and works through setup, accountability-partner enrollment, and everyday use — so the first person living with the friction is us.
Per-browser checks, browser by browser
Chrome, Edge, and Firefox are each checked and documented on their own, because what one browser can enforce is not what another can. We do not generalize one browser's result to the others.
Signed, traceable releases
Each protection release is signed and records what changed, so any statement about a specific release can be traced back to a specific signed artifact instead of a memory of how it used to work.
These are checks we have actually run and filed, described as tested behavior — not a statement about other sites, other browsers, or other machines.
- Chrome — native URL-policy manifest checkRecorded · Win 11
- Edge — native URL-policy manifest checkRecorded · Win 11
Each recorded check describes how a specific build behaved on a specific Windows 11 setup at the time it was run. It is a tested observation, not a promise that the same will hold on a different device or a later build.
Being honest about the gaps is part of the evidence. These are things we are still working to test, and we will not describe them as settled before then.
Long-run enforcement across browsers and edge cases
We have early, per-browser checks — not months of real-world use across the full range of browsers, profiles, and edge cases. We describe that as in progress, never as finished.
Behavior when the protected adult keeps local administrator rights
GuardianBlock adds friction and accountability, and a local administrator can ultimately remove or bypass installed software. We design for that honestly rather than claiming it cannot happen.
The full installer and guarded-deactivation flow on a clean machine
We are still building out end-to-end captures of the signed installer and the supported deactivation path on a fresh Windows 11 virtual machine before we present them as established.
Whether it changes a person's outcomes
We do not measure or claim outcomes here. Whether the product helps a given person stay off a site they chose to avoid is not something this page asserts.
Protection releases are versioned and signed, and the methodology for how a release is built and described is written up separately — including what we deliberately do not publish.
Read the Protection Updates methodology →
More on what we collect and what nobody ever sees lives in our privacy overview and the FAQ.