Skip to main content

Browser privacy evaluations.

Published evaluations document the browser and version, operating system, test date, method, and sources for each result.

How to use a browser privacy evaluation

Start with the privacy question behind your choice. You may need to reduce tracking, keep projects separate, understand Incognito, or decide which accounts belong in a research browser. Each requires different evidence.

  1. Match the setup to your work

    Check the browser version, operating system, settings, account state, and network route described in the evaluation. Those details affect what a website can see. Compare like-for-like conditions before applying a finding to your team. A signed-in browser, a private window, and a VPN session may have different account and storage boundaries while still sharing device traits.

    Read the Chrome privacy evaluation →
  2. Follow the evidence

    Use the technical analysis to see which browser properties, rendering outputs, request headers, and network signals support a conclusion. Distinguish what was observed from how it is interpreted. A repeatable signal can help connect visits, while an account login provides a direct identity relationship. The analysis records methods and conditions so you can understand how the result was reached.

    Inspect the technical evidence →
  3. Choose a practical next step

    Use the findings to review account separation, extensions, browser configuration, and research habits. The fingerprinting guides explain each signal with focused diagrams and demonstrations. If your organization needs evidence from its own environment, a scoped Attribution Risk Audit can compare agreed configurations and help prioritize changes. A published evaluation is a starting point for that decision.

    Explore an audit for your environment →