Security patch latency
Time from a public stable Chrome release containing security fixes to a signed Lean build based on it.
Security and transparency
Trust needs evidence.
Lean starts from Chromium, but that is not enough. This page separates what is measured, what is published with each release, and what the product does not promise.
Two different clocks
Browser patches and blocking repairs.
Repair latency
Time from a Lean Guard rule breaking a website to a corrected list reaching users.
They are separate metrics and are published separately.
Release evidence
A verifiable file, not a trust request.
VersionThe Lean and Chromium versions used by the build.
SHA-256A hash published beside the official installer.
Source changesLean-specific code is available through the project organization.
Known limitsProduct boundaries are documented instead of hidden behind broad claims.
Contexts
Separate sessions are not anonymity.
Contexts separate cookies, storage, cache, and network connections. They also present different signals for canvas, WebGL, audio, and deviceId.
They do not change your IP address. History, passwords, and permissions are shared. Lean does not describe Contexts as anonymous devices.
Lean Guard
Blocking can break a website.
You can allow the current website with one click. Corrected lists are distributed separately from browser builds so compatibility repairs do not wait for a full release.