How we count, and what we won't publish.
Transparency about protection has to be honest in both directions: clear about what a number means, and disciplined about what we never expose.
- 1
Counts come only from the signed release
Every figure is sealed inside the cryptographically signed release artifact and snapshotted. There is no hand-editable marketing counter behind these pages.
- 2
We publish counts, never the list
The exact domains stay private. Publishing the full corpus would hand a roadmap straight to the behavior we're protecting against.
- 3
A release is not a device
A release being available is not the same as a device running it. We never report an offline or unconfirmed device as actively protected.
- 4
Change-counts, not absolute promises
We report what changed — added, corrected, fixed — and the size of the current release. We don't claim to catch everything, because no blocker honestly can.
These boundaries hold for the public hub and for signed-in subscribers alike.
- The full domain listNever
- A check-if-a-domain-is-blocked lookupNever
- Anyone else's custom blocksNever
- Your browsing historyNever
Numbers you can trust because of how they're made.
Every count on the Protection Updates hub traces back to a signed release. That's the whole point.