Privacy Policy
This policy explains what Best Reaction Test processes, what stays in your browser, what you may choose to publish, how analytics and advertising services may operate, and the controls available to you.
Who we are and the scope of this policy
Best Reaction Test operates best-reactiontest.com, a free browser-based reaction-time tool and related informational pages. This policy applies to this website. It does not control third-party websites or services that we link to.
The site does not currently require an account, sell products, process orders, run a newsletter, or provide a public comment area.
Information we process
The categories of information involved depend on how you use the site:
- Local test data: reaction times, calculated scores, recent sessions, preferences, and locally saved leaderboard names or regions remain in your browser unless you take an action that explicitly sends data.
- Voluntary public-result data: only when you choose to publish a result.
- Infrastructure data: hosting and database providers may process standard request, security, diagnostic, and network data needed to deliver and protect the service.
- Contact-form data: when you submit the contact form, we receive the name you optionally provide, your email address, selected topic, message, optional related-page URL, optional public-result submission identifier, a random message reference, and the submission time.
- Other information you choose to send: content you email to contact@best-reactiontest.com or place in a public GitHub issue.
Reaction-test results stored on your device
Your attempts, personal best, recent score-card history, training progress, and any local leaderboard entries are processed and stored with browser storage on your device. No third-party analytics service receives these values. A result leaves your device only when you deliberately publish it anonymously to the public dataset.
You can clear supported histories from the relevant result card. You can also remove all local data for this site through your browser’s cookie and site-data controls.
Voluntary public results
The home page may show community statistics built from results visitors voluntarily publish. Publishing is strictly opt-in: no reaction-time result is uploaded until you activate the “Publish my result” control.
A published record contains a random submission identifier, median, best time, average, spread, test protocol, a general device label such as operating system and browser family, and a timestamp. The application payload does not include your name, account, email address, or precise location. As with any web request, hosting and database infrastructure may process network information such as an IP address for delivery, security, abuse prevention, and logs, even though an IP address is not stored in the public-result table.
Published rows are stored in Supabase behind row-level security: anonymous visitors can insert permitted rows but cannot read, update, or delete raw rows. An automated process validates and deduplicates data and publishes aggregate statistics for a rolling 90-day window. Raw records may be retained for integrity, abuse prevention, aggregation, and deletion handling until they are no longer needed. To request removal, use the contact page and provide the submission identifier displayed after publication.
Cookies, local storage, and similar technologies
We use browser storage to operate optional local history, preferences, training progress, and publishing limits. The site does not currently use a third-party traffic analytics service. Advertising services, if enabled in the future, may place or read cookies or use other identifiers after any required consent controls are deployed.
You can block or delete cookies and site storage in your browser. Some local-history and preference features may reset or stop working, but the basic reaction-time test can still operate.
Advertising and Google AdSense
The site may use Google AdSense or other advertising services to fund free access. When Google ads are enabled, third-party vendors including Google may use cookies to serve ads based on a visitor’s prior visits to this website or other websites. Google’s use of advertising cookies enables Google and its partners to serve personalized ads where permitted. Advertising requests can also involve page URLs, IP addresses, browser or device information, cookies, web beacons, and other identifiers for ad delivery, measurement, fraud prevention, and personalization.
You can manage or opt out of personalized Google advertising through Google Ads Settings. You may also use applicable industry opt-out controls such as AboutAds. Before advertising is activated for visitors in regions where Google or applicable law requires consent, the site must deploy the required consent controls; this policy by itself does not record consent.
Hosting, database, and other service providers
Vercel hosts and delivers the website and may process standard request, security, and diagnostic data. Supabase hosts opt-in public-result records and private contact-form submissions. Google may provide advertising after AdSense and the required consent controls are enabled. GitHub provides the public issue tracker. These providers process information under their own terms and privacy policies and may operate infrastructure in multiple countries.
Why we process information
Depending on the information and applicable law, processing supports one or more of the following purposes: providing requested website functions; remembering settings on your device; maintaining security and preventing abuse; measuring and improving the site; publishing a result you explicitly choose to submit; complying with legal obligations; and, where implemented and permitted, funding the service through advertising. The applicable legal basis depends on the visitor’s location and the processing involved; consent must be obtained before any consent-dependent processing is activated.
How information may be disclosed
We do not sell contact details or reaction-test scores. Information may be processed by the service providers described above, disclosed when required by law or necessary to protect rights and security, or transferred as part of a reorganization of the website. Aggregate statistics do not identify individual visitors. A public GitHub issue is visible to anyone, so do not post passwords, medical information, or other sensitive personal information.
Retention and security
Local data remains on your device until you clear it, the site replaces it, or your browser removes it. Public-result aggregates cover a rolling 90-day period; raw submissions may be kept longer for validation, abuse prevention, aggregation, and removal requests. Contact messages remain in the private contact database until they are manually deleted after the request has been handled or are no longer needed. Service-provider logs follow the providers’ configured retention practices.
We use reasonable technical measures such as HTTPS, security headers, database constraints, insert-only public permissions, and row-level access controls. No website, network transmission, or storage system can be guaranteed completely secure.
International processing
Our service providers may process information in countries other than the one where you live. Their privacy terms describe the safeguards and legal mechanisms they use for international data transfers.
Your choices and privacy rights
You can decline to publish a score, clear browser storage, block cookies, use browser privacy controls, and manage Google advertising preferences if advertising is enabled in the future. Depending on where you live, you may also have rights to request access, correction, deletion, restriction, objection, portability, or withdrawal of consent for personal information we control. Use the contact page to make a request. We may need enough information to verify and locate the relevant record; for an opt-in public score, the submission identifier is the practical lookup key.
Do Not Track and Global Privacy Control
Because there is no consistent industry standard for the browser “Do Not Track” signal, the site does not currently claim to respond to DNT. Where a legally recognized opt-out signal such as Global Privacy Control applies to processing we control, we will treat it in accordance with applicable requirements. Browser blocking, consent controls, and the opt-out links above remain available.
Children and sensitive information
The site is a general-audience tool and is not directed to children under 13. We do not knowingly request personal information from children under 13. If you believe a child has submitted personal information, contact us so we can review the request. Do not use this site to submit medical or other sensitive information; the tool is not a diagnosis or medical assessment.
California privacy notice
Visitors may use the site without creating an account. A link to this policy is available in the site footer. We will post material changes on this page and update the date above. California residents may use the contact method below to ask about applicable privacy rights. We do not offer financial incentives for personal information and do not sell personal information in the ordinary meaning of that term.
Changes and contact
We may revise this policy when the product, service providers, advertising setup, or legal requirements change. Material revisions will update the date displayed above. For privacy questions, correction requests, or removal of a published result, use our contact page or email contact@best-reactiontest.com. GitHub issues are public, so do not include sensitive information there.