Privacy

The short version: the tools run on your machine, not ours. Here's exactly what that means, and the few things that are genuinely different.

Tool data never leaves your browser

Every tool on this site — keyboard tester, CPS test, and every one that follows — processes its input entirely in your browser. Keystrokes, clicks, audio, video, text: none of it is sent anywhere, because none of these tools talk to a server to do their job. There is no upload step to intercept, because there is no upload step.

Best scores and preferences a tool remembers for you — a CPS personal best, a chosen keyboard layout — are written to localStorageon your own device. They stay there. They are not readable by us, and they don't leave your browser either.

One honest caveat: localStorageis not encrypted. On a shared or public computer, whatever it holds stays there for the next person to open the same browser, until it's cleared. Not leaving your machine is a genuine privacy property, but it isn't the same as being locked away — don't use a tool here to store anything you'd call confidential. See the terms page for the same point put plainly.

What does leave the browser

Two things, and both are anonymous counters, not records:

  • A per-tool view count — one increment per visit, with no payload attached to it, used only to show which tools people actually use.
  • A per-tool reaction count, when you click "Worked" or "Something's off" on a tool page — again, a counter increment, not a record tied to you.

To stop those counters being spammed, both endpoints rate-limit by IP address. That means your IP is used to form a short-lived key — a count of recent requests, expiring within the minute — so it is fair to say your IP is briefly processed, though it is never stored alongside which tool you used or what you did with it.

Beyond that, this site receives the same request logs any web server does — the kind that record that a request happened, for operating the site rather than for tracking who made it.

Analytics, and why there is still no cookie banner

This site does use Google Analytics, but in a deliberately reduced configuration: it runs in consent mode with analytics storage denied by default. In practice that means no _ga cookie is written, no identifier is kept on your device, and your visits are not stitched together into a profile across sessions.

What it does report is aggregate and per-page: which URLs were viewed, where visitors arrived from, and roughly which country. That last one matters here for a specific reason — it is how we can tell whether people find these tools through a search engine or through an AI assistant, which genuinely changes what is worth building next.

There is no cookie banner because, configured this way, there are no non-essential cookies to ask you about. There is no ad-tech pixel, no advertising or personalisation signal is sent, and no other third-party script is watching what you do.

If that configuration ever changes — if cookies get switched on, or another vendor is added — this page changes in the same update that does it, not afterwards.

Accounts are optional

Signing in is never required to use a tool, and no tool is ever gated behind it. An account exists for exactly one reason: to save results you choose to keep, instead of leaving them in your browser's localStorage. Sign-in and account management are handled by Clerk.