Verification Governance

Browser & Device Analysis Policy

How browser and device information is detected, what it reveals, and how we protect user privacy.

Browser detection

Browser identification uses standard navigator APIs and user-agent parsing. Both are heuristic indicators — easily spoofed and frequently outdated by major-version releases.

Feature detection

  • Web platform feature availability (e.g. Service Workers, WebRTC, WebGL).
  • Standards-compliance hints surfaced by the browser itself.
  • Codec, format, and protocol support reported via runtime checks.

Compatibility reporting

We compare detected capabilities against current web platform baselines to surface compatibility gaps. We do not attempt to fingerprint or uniquely identify users.

Device capability analysis

  • Viewport dimensions, color depth, device pixel ratio (display only).
  • Pointer and hover capability (input modality only).
  • Reported language, timezone, and Intl preferences.

Privacy considerations

  • All detection runs in the user's browser. No silent uploads of device profiles.
  • We do not combine signals into a persistent device fingerprint.
  • Browser privacy modes, anti-fingerprinting features, and extensions are respected — if they hide a value, our report shows it as unavailable.
  • Detected information is shown to the user and not retained server-side beyond aggregate request metrics.

Last reviewed: June 2026.

Part of the Information Verification Trust Center. Published by Relationale LLC. Founder: Keiron Brown.