Methodology

The passive stage reads browser-exposed signals such as your device and operating system, browser and version, languages, timezone, screen, hardware hints, battery support, WebGL, and canvas/audio rendering. These signals are combined into explanations and confidence labels; they are not a claim that every signal uniquely identifies you.

The test may also attempt a client-side WebRTC public-IP check and an optional direct lookup that turns that IP into an approximate city and ISP. Hardened browsers, extensions, and network settings can block these readings, which is shown as unavailable or blocked rather than guessed.

Precise location, camera and microphone devices, clipboard, and notifications are requested separately and only after you choose to continue. The test does not record camera or microphone content. It also demonstrates tab attention, pointer, click, scroll, and dwell signals that pages can observe without a permission prompt.

The reveal can make network requests to the WebRTC STUN service, the disclosed IP-geolocation provider, and tracker endpoints to show whether those resources are reachable from your browser. These requests are part of the demonstration and can be blocked by your browser or extensions.

Raw test signals are computed in your browser and are not sent to an Am I Tracked backend. A localStorage value is used only for the returning-visitor demonstration, so it stays on your device. Third-party requests and anonymous analytics are described in the privacy policy.

Browser APIs differ by browser, operating system, extensions, and network. A blocked or unavailable value is a real result, not an inferred value. You can inspect the collection logic, explanations, and tests in the public repository:

View the Am I Tracked source on GitHub ↗

If a browser change makes a result or explanation inaccurate, you can report a correction in GitHub Issues ↗.