Signals · locale · counted, not scored by the rubric
Number and date formats
A hash of what the Intl API resolves: the locale, calendar, numbering system, time zone and how sample numbers and dates are formatted.
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 asks each Intl formatter for its resolved options and for a few formatted samples, then hashes them together.
Why it splits browsers apart
Language, region, operating system settings and the browser's own locale data all feed it, so two browsers that report the same language can still format a date differently.
What moves it
Changing the system region or the browser language, and browser updates that ship new locale data.
What moving it costs
A language list that says one country while the formats resolve to another is a classic proxy and spoofer tell.
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 number and date formats
- Why does my date format matter?
- It shows the region and settings the browser actually uses, which may differ from the language it reports. That gap is what detectors look for.
- Why is it not in the device key?
- Browser updates ship new locale data and change it, so the key uses the time zone and the language list instead.
In the same group
Next
Keyboard layout: A hash of the keyboard layout map, or unavailable where the API is missing.
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.