Signals · identity · counted, not scored by the rubric
Browser and version
The browser family and its major version, for example Chrome 141 or Firefox 133.
Rubric 1.0.0 does not print a prior for this value. The population still compares it, so the box beside this text counts how many of the devices these sites have read share yours.
How a page reads it
The collector parses the user agent string and, in Chromium browsers, the client hints brand list, which names the real engine even when the user agent is edited. Only the family and the major version are kept, so two patch releases of one browser count as one value.
Why it splits browsers apart
On its own it splits little: most visitors run one of a few current versions. It matters as a clock. A browser two or three majors behind stands out for a few weeks, and a version that does not exist yet (or a brand list that names a headless build) stands out for good.
What moves it
Every browser update moves it, usually within days of a release, which is why the device key leaves it out.
What moving it costs
Editing the user agent moves this value and nothing else. The client hints, the JavaScript features the engine ships and the TLS handshake still describe the real version, and a detector compares them.
How the count is made
Your value is compared with the latest reading of every device the eight sites read in the last 365 days, this browser's own rows left out. The share is (devices sharing it + 1) ÷ (population + 1), and the bits are −log₂ of that. Why the counts sit beside the priors and are never added to them.
Questions about browser and version
- Why is my browser version not part of the device key?
- Because it changes with every update. A key that included it would split one device into a new identity every few weeks, so the key uses values that survive an update instead.
- Does a rare browser version make me easier to track?
- For a short while. An old or unusual version narrows the crowd until the next release moves everyone else. A version that contradicts the rest of the browser is the bigger problem, because contradictions do not expire.
In the same group
Next
Operating system version: The operating system and its version, for example macOS 10.15 or Windows 10.
Where the pens move
A value patched in the page is a patched value. Set in the engine, it is just a value.
Engine level, not JS level. Donut Browser spoofs through CDP injection in its Wayfern Chromium fork, so the value a page reads is the value the engine reports — there is no patched accessor to catch.
It refuses to contradict itself. A profile whose proxy exit geography, time zone or language disagrees with its fingerprint does not launch. That is a pre-launch gate in the app, not advice in a manual.
Open, and quiet. AGPL-3.0, desktop app and sync server both in the repository, and no analytics SDK anywhere in the source. macOS, Windows, Linux.