Privacy Policy
Learn what information the site uses, how optional analytics works and how you can update your privacy choices.
This policy explains what the site may store or process when you use the public tools, save a result, open the apps page or send a support message.
Core data the site may handle
- test results and supporting metrics such as score, CPS, WPM, accuracy or reaction time
- device, browser, operating system, approximate country and referrer data when available
- consent choices for preferences and analytics
- contact-form submissions when you message the site
Why that data exists
The data supports local and saved histories, abuse prevention, moderation of public score blocks, product maintenance, support handling and optional analytics after consent. The site does not require an account just to use the public tools.
What stays public and what does not
Using a tool does not automatically mean every raw attempt becomes a public leaderboard entry. Local history can remain on your own device, while public saved rows are treated as a moderated layer that may exclude suspicious, impossible or duplicate-looking values.
Retention and moderation context
Some stored rows may remain in internal history even after they stop being suitable for public display. That allows the operator to backfill stricter moderation rules over time without pretending that every older historical row should remain publicly visible forever.
Public results and moderation
Saved public results may be filtered, hidden or excluded when they look impossible, bot-like, duplicated or otherwise misleading for other visitors. The goal is to protect trust in the visible pages, not to preserve every raw row as a public badge.
Your controls
You can review your cookie choices in the Cookie Policy and reopen at any time. If you contact the site about a result, include the page URL and visible value so the issue can be reviewed more efficiently.