How this actually works

What’s real

Every data point shown on the main page is computed from your browser using standard, publicly documented Web APIs — nothing is fabricated or randomized. If a signal can't be determined confidently, it's simply left out rather than guessed.

• ▸Browser/OS identification (user agent, parsed browser and OS, platform, User-Agent Client Hints)
• ▸Display (screen and viewport size, color depth, pixel ratio, orientation, color gamut, HDR support)
• ▸Hardware (CPU core count and architecture, device memory, GPU vendor/renderer via WebGL)
• ▸Fingerprints (a canvas rendering hash, an audio-context hash, an installed-font probe)
• ▸Network (effective connection type, media device counts, your resolved public IP and country)
• ▸Browser state (cookies/local/session storage availability, Do Not Track, online status, permission grants, automation/ad-blocker detection)
• ▸Page context (referrer, current URL, tab history length)
• ▸Derived signals, computed from the above rather than read directly: an illustrative uniqueness/entropy estimate, and a timezone-vs-IP-location consistency check (a classic VPN/proxy heuristic)

What’s theatrical

The presentation is deliberately over-the-top. None of the following reflects anything actually happening:

• ▸"SYSTEM PENETRATION ACTIVE", "[email protected]" terminal framing, and all the hacker-movie flavor text
• ▸The skull icons, glitch effects, and binary rain background
• ▸Any implication that this data is being sent to a "master" server or used maliciously

Where data goes

Nothing collected here is stored server-side, logged, or sent to any third party for tracking purposes. Two network requests are made purely to resolve your public IP for display purposes:

• ▸/api/network, a route on this same server, which reads the IP-related headers already present on your request (see the source for exactly what it does).
• ▸As a fallback only, when the above yields nothing, a request to api.ipify.org, a public third-party IP-echo service, unrelated to this app.

Stored locally, on your device

The “WELCOME BACK” / “FIRST CONTACT” panel comes from a small record (a random ID, visit count, and a handful of field values to diff against next time) kept in this browser’s localStorage. It never leaves your device — there is no server-side database behind it. Clearing your browser’s site data for this page resets it.

The uniqueness/entropy estimate is a heuristic illustration, not a measurement — it sums a rough, hand-assigned “bits of surprise” weight per captured field. It’s meant to communicate roughly how identifying a combination of signals can be, not to be a precise statistic.