Privacy Policy

Version 1.1 uploads no test scores or device information. Rendering, per-frame timing and score calculation happen in your browser; results live only in the current session (sessionStorage) and disappear when the tab is closed.

The page itself uses third-party analytics to count visits, described below under “Analytics and third-party resources”.

Before a run we read and display: the GPU renderer and vendor strings (via the WebGL debug extension), browser name and version, OS and version, platform, screen resolution, device pixel ratio, estimated refresh rate, touch-point count, and during the run per-frame timings plus aggregate results (average FPS, 1% Low, minimum FPS and the FPS curve).

This is used for the result view and local scoring only — it is never uploaded as test data. Browsers may return generalised values such as “Apple GPU” in Safari; that is expected privacy behaviour.

No names, email addresses, accounts, passwords, contacts or precise location. We run no advertising and no cross-site ad profiling. Analytics is limited to the three services listed below; there are no other third-party scripts.

Phase 1.2 plans to add optional anonymous result submission. The exact fields will be listed before you submit, and submitting stays a deliberate action — declining still lets you see your full result. Submitted data is anonymous technical data without personal identifiers. If rate limiting is enabled, IP addresses are hashed and kept briefly, never written to public data.

This page will be updated before submissions go live. We will not start collecting silently.

In fairness: a combination of GPU renderer string, resolution and browser version can be fairly unique and could act as a device fingerprint. It is never uploaded with a score, and the device-information block on the page is marked as excluded from session replay, so analytics does not capture it.

Because no server-side test records exist today, there is nothing to query or delete. You can clear session data at any time or simply close the page; cookies set by the analytics tools can be cleared in your browser settings or blocked permanently with an extension. A deletion channel will be provided if submissions open later.

The site uses three third-party services to understand traffic and page usage. They set cookies and make requests to their own servers:

• Google Tag Manager (GTM-PZMPG3J2) loads the analytics and event scripts;
• Baidu Analytics counts referrers and page views;
• Microsoft Clarity aggregates clicks, scrolling and dwell time to help improve page structure.

These services typically record the page URL, referrer, browser and device type, an approximate region inferred from your IP address, and on-page interactions. The device-information block shown before a test is marked as excluded from capture, so it does not appear in session replay. These scripts run alongside the page and never participate in benchmark timing.

Fonts are served via Google Fonts, so your browser makes ordinary resource requests to that service. Links to the original project point to an external site with its own practices.

You can limit this analytics with a browser extension or a Do-Not-Track style setting; the core benchmark does not depend on it and keeps working if you block it.

Privacy questions: hello@volumeshaderbm.app. Changes to this policy update the date above.