← XIO The identity check

XIO Hub

A browser that refuses to hand you over.

The XIO Identity Check recognised you from your canvas, your network, and the way you move a mouse. It only worked because your browser answered every question a web page asked it. A browser doesn’t have to. Here is how XIO Hub — built on Firefox — shuts each signal down.

Signal by signal

neutralised

Canvas, WebGL & audio fingerprints

A page draws invisibly and reads back the pixels; tiny GPU/driver differences make the result unique to your machine.

Fingerprint resistance. XIO Hub turns on Firefox’s privacy.resistFingerprinting, which feeds canvas and audio reads a slightly randomised result on every call and hides the real GPU behind a generic WebGL vendor/renderer string. Two reads never agree, so there is no stable hash to store. Everyone looks like the same generic machine.

neutralised

Installed fonts

Measuring text width reveals exactly which fonts you have — a strong, silent signal needing no permission.

A fixed font set. With resistFingerprinting the browser exposes only a standard bundled font list and normalises text metrics, so font probing returns the same answer for every visitor instead of your personal catalogue.

neutralised

Hardware & screen class

CPU core count, device memory, screen resolution and pixel ratio narrow you to a small group of machines.

Clamped and letterboxed. XIO Hub caps navigator.hardwareConcurrency, drops navigator.deviceMemory, reports the viewport in rounded 200×100 steps (“letterboxing”) and pins the pixel ratio, so your hardware reads as a common bucket, not a unique one.

neutralised

Time zone & locale

Your time zone and language list are quietly readable and rarely change, which helps link your devices.

Spoofed to a common value. Fingerprint resistance reports the time zone as UTC and the language as a standard en-US, so this stops distinguishing you from everyone else running the same defence.

neutralised

Your IP address & network

Your public IP ties every device in your home together and pins you to a city and an ISP; WebRTC can even leak your local IP.

Built-in proxying and a WebRTC seal. XIO Hub routes traffic through its proxy/VPN layer so sites see an exit address shared by many people, and disables WebRTC IP discovery (media.peerconnection.enabled off by default) so your real and local addresses never escape.

blunted

How you move, scroll & type

Pointer speed and curvature, scroll rhythm and key hold/flight times are behavioural biometrics — they follow you onto a brand-new device, and this is the hardest signal to hide.

Starve it and add noise. You cannot un-move your mouse, so XIO Hub attacks the plumbing: aggressive third-party script blocking means most pages never get to run the measuring code, event timestamps are coarsened so fine-grained dynamics blur together, and strict site isolation stops one tracker correlating your behaviour across different sites. Honest framing: this reduces the signal rather than erasing it — the real fix is not letting the script load at all.

neutralised

Cookies & cross-site linking

Third-party cookies and shared storage stitch your activity together across every site a tracker is embedded on.

Partition everything. Total Cookie Protection gives every site its own isolated cookie jar and storage, third-party cookies are blocked, and Global Privacy Control is sent on every request. A tracker on site A cannot read what it wrote on site B.


The short version

Want to feel the attack first? Run the XIO Identity Check, then come back and watch each signal go quiet.

Try the identity check All XIO projects