Privacy

Personal history

Your recent test history is stored in your browser using localStorage. It is not uploaded merely because you run the test.

Optional community benchmark

If you explicitly opt in after completing a session, the benchmark endpoint may receive the five valid trial times, false-start count, coarse device class, coarse input class, refresh-rate estimate bucket, coarse frame-stability label, a one-bit main-thread long-task flag, test version, timestamp, and a random one-session ID used to reject accidental duplicate submissions. Summary statistics are recalculated on the server from the five raw trials. The session ID is not an account ID and is not reused across sessions or sites.

What we do not ask for

We do not require your name, email address, precise location, date of birth or a user account to take the test.

Advertising and Google AdSense

Current state: the site build does not include AdSense ad code, and AdSense is not part of the current test experience.

If AdSense is enabled later, Google and its advertising partners may use cookies, web beacons, IP addresses, device information, or other identifiers to serve, measure, personalize, limit, or report advertising in accordance with applicable law and the user choices available in the relevant region.

Third-party vendors, including Google, may place and read cookies in your browser or use web beacons and similar technologies as a result of ads being served on this site. You can learn how Google uses information from sites and apps that use its services at Google's partner sites policy page. Where required, advertising consent choices will be presented before personalized advertising technologies are used.

ReactionMetric does not send your raw reaction-time history, benchmark trial values, name, email address, or precise location to Google AdSense for ad targeting. We do not create advertising audiences from reaction-time scores or other potentially sensitive benchmark results.

Privacy-minimal product telemetry

ReactionMetric keeps first-party daily aggregate counters for core product reliability and funnel totals independently of the optional Google Analytics choice. This layer is designed as aggregate counting rather than user profiling: it does not use an analytics cookie or a persistent user/session identifier.

The aggregate layer stores counts grouped by UTC day, event name, page path and a small allowlisted category such as test mode, coarse device class, share method, challenge source, interruption reason, web-vital quality band or analytics-choice outcome. The application does not store IP addresses, complete User-Agent strings, persistent user/session identifiers, raw challenge scores or raw local-history values in this aggregate table. URL query strings and fragments are discarded; a recognized share source such as native, copy, X or Reddit may be reduced to an allowlisted category before the URL is discarded. Aggregate telemetry older than 400 days is automatically deleted.

Optional Google Analytics

Google Analytics 4 (GA4) and its consent prompt are temporarily paused. No GA4 script loads for new or returning visitors during this pause, including browsers that had accepted in the past. Previous stored analytics choices are cleared; if GA4 is enabled again, visitors will be asked to make a fresh choice before it loads. Events from the paused period are not replayed to GA4. First-party privacy-minimal aggregate counters remain active independently of GA4.

Hosting and logs

Cloudflare may process standard request metadata needed to serve and protect the site. ReactionMetric does not require an account to run the test.

Retention and deletion

Local history remains in your browser until you use the in-page “Clear local history” control for that test mode or clear site storage in your browser. Raw contributed benchmark sessions are retained for up to 24 months; a scheduled benchmark cleanup runs daily and new benchmark submissions also trigger cleanup. First-party product telemetry is stored only as daily aggregates and is retained for up to 400 days. For benchmark/privacy requests, contact privacy@reactionmetric.com. ReactionMetric does not use the one-session benchmark ID as an account or cross-site identifier.