Firefox render diagnostics, with consent.

What we collect

Only browser-render diagnostics. Everything below is gathered locally, summarized across a few repeated passes, and sent in a single small payload to auth.vulpineos.com.

• Browser and OS metadata

  Browser brand and version, OS name and version, platform, architecture, browser language, timezone, hardware concurrency, and device memory.

• Display metadata

  Screen width and height, available area, color depth, device pixel ratio, prefers-dark and reduced-motion preferences.

• Canvas and text rendering summaries

  We render fixed canvas and text scenes locally several times and send hashes of the resulting pixels plus a short list of font width measurements. Raw pixels and screenshots never leave your browser.

• WebGL summary

  Vendor and renderer strings, GL and shading language versions, texture and viewport limits, and the supported extension list.

• Worker capabilities

  Whether your browser exposes Worker, SharedWorker, ServiceWorker, and OffscreenCanvas.

• Coarse country / region

  If your hosting provider exposes it via request headers, we may store the country or region. We do not store IP addresses.

What we do not collect

The following are explicitly out of scope. The collector is built to refuse them.

• Passwords, tokens, or any credentials.
• Cookies, localStorage, or sessionStorage contents.
• Account data or personal identifiers.
• Browsing history or referrer chains.
• Page HTML, text content, or any DOM contents.
• Screenshots or raw images of any kind.
• Raw data URLs.

Why this exists

VulpineOS depends on browser rendering being predictable across operating systems, drivers, and configurations. RenderLab helps us measure how consistent that rendering really is in the wild — across a much wider surface than any single test rig.

The data improves Vulpine RenderLab and our wider work on browser rendering and fingerprint-consistency research. It is not used for advertising, tracking across sites, or training third-party models.

Optional, always

RenderLab is opt-in. The site works identically if you decline. Declining saves a local-only flag — nothing is sent to the backend.

Acceptance creates a participant id and consent id which are stored in your browser's localStorage so you can revoke later. A diagnostic is submitted only when you accept. We do not run diagnostics automatically on every visit. If you revoke and later allow diagnostics again, a new consent and diagnostic payload are created.

Revoke any time

Use the control at the top of this page. Revocation deletes the local participant and consent ids, and submits a revocation to the backend so we stop accepting runs for them.

Contact

Questions or requests: privacy@vulpineos.com.