Browser Metadata Demo

This page presents request-side and browser-readable signals that may be available during a standard site visit, including transport details, rendering characteristics, capability hints, and selected client environment data. Metadata can be used for a "fingerprint" which is a probabilistic match of different pieces of data for the use of identification. Not all metadata is utilized or tracked across services for this purpose, but ad-first (Google, Meta, Amazon Ads, LinkedIn, The Trade Desk) and identity-first (LiveRamp, Epsilon, Neustar / TransUnion, Experian), along with data-brokers (Mobilewalla, Kochava, InMarket) do. If you use an ad/tracker blocker extension such as Privacy Badger or uBlock Origin, you will see that there are no trackers displayed as blocked on this page, because third-party trackers are not required for the information gathered. Disabling JavaScript can heavily reduce exposure, but does not remove metadata gathered (though it may not be shown) from the preliminary http/https request.

This page is intended as a transparent demonstration of ordinary and ubiquitous metadata exposure. Using a reputable VPN and browsers such as Mullvad Browser or Brave Browser (configured for anti-fingerprinting) can reduce metadata exhaust and exposure. Having only a VPN or only a privacy browser is often not enough, and many "privacy browsers" often do not work. The word reduced is used because there is no such thing as total or real anonymity, only approximation. It should be noted that anonymity or uncertainty is broken when logging into a service using credentials. Not all metadata is as identifying as other kinds, but the aggregate is what aids in higher certainty of identification across time when compared to other instances of gathered data.