Privacy training for organizations
Practice browser choice, VPN hygiene, account separation, and repeatable workflows in a custom team workshop.
Tests and demonstrations
Browser fingerprinting tests and demos
Inspect a browser signal, understand where it comes from, and compare what changes. Choose a local inspector or explore a conceptual model.
Start here
See what your browser volunteers.
The browser signal inspector brings several surfaces into one view. Open it for an introduction, then use the focused demos below to explore a single signal.
Open the browser signal inspector ↗DisplayViewport + pixel ratio
ConfigurationLanguage + timezone
ImplementationGraphics + hardware hints
Example surfaces, not readings from your device.
Explore a surface
Choose what you want to understand.
Local inspectors read selected browser output. Conceptual demos explain a mechanism with illustrative values. Opening this directory does not run the linked tests.
- Local demo
Canvas pixels
Render a scene and compare its pixel digest.
See how a small rendering change produces a different hash.
- Local inspector
WebGL graphics
Inspect renderer details, capabilities, and a rendered scene.
Connect GPU and driver behavior to browser signals.
- Local demo
Fonts and text
Compare text measurements for a candidate font list.
Explore the clues left by text rendering and font availability.
- Local demo
Audio processing
Render an offline audio graph and inspect its output.
Compare processing behavior without recording a microphone.
- Local inspector
Navigator properties
Inspect language, platform, CPU, and memory hints.
Read the browser’s advertised properties, rather than a hardware inventory.
- Local inspector
Screen and viewport
Inspect display dimensions, viewport, and pixel ratio.
See which values move when you resize, zoom, or change displays.
- Local inspector
Timezone and locale
Inspect language preferences and date/time formatting.
Understand regional configuration clues without treating them as GPS.
- Demo + optional sensors
Hardware and motion
Explore a posture simulation or compatible motion samples.
Live sensor access depends on permission, support, and an explicit action.
- Local observer + sample
Extension traces
Watch page changes and exposed extension-resource addresses.
Observe traces visible to the page; the result is not a complete extension inventory.
- Conceptual demo
VPN visibility map
Switch network routes, private sessions, and account sign-ins.
Compare what each observer sees. No VPN or IP test is performed.
Make a useful comparison
One control. The same measurement.
- 01
Record a baseline
Note the device, browser version, extensions, settings, and demo scene. Keep sensitive accounts and real client material out of the exercise.
- 02
Change one thing
Switch the VPN route or change one browser protection. Repeat the same test so you can connect a difference to a specific change.
- 03
Compare several runs
Separate stable outputs from changing ones. A matching digest shows repeatability in that test; a new digest alone does not establish anonymity.
These tools explain individual surfaces. They do not assign a universal privacy score, measure population-wide uniqueness, or test every way a service can connect visits. Accounts, stored state, and server-side observations also matter.
Beyond browser JavaScript
Some signals need a different vantage point.
A page can inspect browser APIs. Measuring an exit IP, DNS route, or protocol handshake requires a network-facing observer. The guides below explain those layers and distinguish illustrations from measurements.
Put the evidence to work
From a browser signal to a privacy decision.
A demonstration shows one part of an environment. Choose the next step around the work you need to protect.
Start with the free online privacy checklist to review your browser, VPN, and account habits before choosing a next step.
Explore fingerprinting tests and demos · Does a VPN make you private?