Browser privacy check

Quick Browser Privacy Check

Review understandable browser storage, permission, locale, timezone, and privacy-control observations without triggering deeper tests.

Browser privacy guide

How to review browser permissions and privacy settings

This quick check reads permission states and common privacy preferences without opening camera, microphone, clipboard, or location prompts. It tests first-party storage and clearly marks cross-site storage as unconfigured until the optional controlled Aerod probe is deployed.

How to use the result

  1. Run the quick check and start with the summary.
  2. Open only the settings marked for review to see meaning and a next step.
  3. Use a dedicated WebRTC or fingerprint test only when you need deeper evidence.

What it means

“Review” means the setting deserves context; it does not mean the browser is unsafe. A granted permission may be intentional. A blocked or unavailable API may reflect browser policy, private mode, an extension, or platform support.

Important limits

  • Permission queries do not request or exercise the permission.
  • Cross-site partition status is unknown when the Storage Access API is unavailable.
  • The quick check intentionally skips deep fingerprint surfaces.
Useful next checks Run the advanced fingerprint checkRun the WebRTC check

Common questions

Does this check ask for camera or location access?

No. It reads queryable permission states and reports unavailable states when the browser does not expose them.

Does available storage mean third-party tracking is allowed?

No. First-party storage, partitioned third-party storage, and unpartitioned cross-site access are different states. The result explains which one could actually be observed.