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.
What we have recorded so far
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 — browser policy checkRecorded · Win 11
- Edge — browser policy 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.
The kinds of evidence we require
Before a behavior becomes a claim, it has to be observed and recorded somewhere we can point back to.
- 01
Fresh Windows testing
We test the installer, Windows app, status display, and browser integrations in fresh Windows 11 environments. We follow a written test plan and record what each run actually did.
- 02
Hands-on founder use
Before anyone else relies on it, the founder runs GuardianBlock on a real device and works through setup, accountability-partner enrollment, and everyday use.
- 03
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.
- 04
Signed, traceable releases
Each protection release is signed and records what changed, so any statement about a release can be traced back to that specific version.
What we have not proven yet
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.
The full installer and guarded-deactivation flow on a clean machine
We are still testing the signed installer and supported removal path from start to finish on fresh Windows 11 systems 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.
How releases are tracked
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.
Last reviewed: 2026-08-31
We would rather under-claim than overstate.
GuardianBlock for Windows will be available soon. We will keep this page honest about what is tested as the evidence grows.