Fingerprint and its editor

A site reads the screen, card, cores, memory, fonts, clock and languages. No finished fingerprint is kept: it is built again at every launch.

• Identity

  platform, User agent, vendor, client hints.

• Screen

  size, space under the menu bar, colour depth, ratio.

• Hardware

  WebGL vendor and renderer, cores, memory, touch, fonts.

• Place

  time zone, language stack, locale, country.

• Devices and connection

  microphones, speakers, cameras, voice locale, downlink, latency, heap.

• Noise seeds

  canvas seed and audio seed.

Your profile takes the drawn values from its own id, and the draws chain because the strongest tells are pairs.

1. 1

   Draw the graphics card

   The profile takes a vendor and renderer pair from the template's cards.

2. 2

   Read the cores and memory off it

   A card class carries the counts it ships with.

3. 3

   Read the architecture off it

   Apple Silicon and the mobile templates give arm, the other desktop cards x86.

4. 4

   Narrow the system versions

   On a Mac a new chip on an old system does not turn up.

5. 5

   Draw the country before the clock

   One throw settles clock and language together.

A fingerprint template is the kind of machine. A desktop profile is assembled from its parts, a mobile one is a whole device.

With a proxy, the profile takes the clock and languages of the country its first exit resolves to, unless you picked them by hand.

• The time zone

  Intl, Date and the offset move together, and large countries carry several zones.

• The language stack

  The full list, because one entry beside a foreign exit is the mismatch.

• The speech voices

  An inventory of the system, trimmed to the profile's language when the machine has such voices.

• Nothing else

  Screen, card, cores and fonts stay as drawn: the account knows them.

• No proxy at all

  A current-generation profile draws a country by seed; older generations keep the computer's clock.

Under Change values you pick from lists: Screen, CPU cores, Memory (GB), Pixel ratio, Timezone, Languages, WebGL; on a phone, the Device.

• Card, core and memory lists come from the generator

  The profile fills an empty field itself, and a card pulls its cores and memory.

• A value outside the list

  You are told by name when you save, not at launch.

• Cores the card never has

  Laptop graphics with a workstation core count will not save.

• A ratio the screen never has

  No real panel has that ratio, and it will not save.

• A template this generation cannot build

  You are told outright, not given a phone in the card and a Mac to the site.

A newer generator would hand your profiles a different computer at the next start, and that reads as a takeover.

So each profile carries its generation number and stays on it, whatever generator comes later.

Test fingerprint: on ARMANOS Browser the self-test reads a profile as a site reads it: up to 37 lines per profile.

• The values

  Platform, client hints, screen, cores, memory, renderer, clock, languages.

• The hiding

  The automation flag reads false, patched functions read as native code.

• The canvas and the card

  Repeated reads agree, a graphics read agrees with the canvas, noise resists subtraction.

• Other realms

  An iframe and a worker answer the document's cores and platform.

• Fonts

  Measured as font fingerprinting works, by comparing rendered widths.

On ARMANOS Browser the fingerprint lives inside the engine, ahead of any page script. The built-in engine installs its values by script at document start.