ClickPlayground logo

Contact Us

Bugs, feature ideas, blog topics, partnerships — we read real inboxes.

ClickPlayground runs free CPS tests, spacebar and typing benchmarks, jitter and Kohi trainers, reaction and aim drills, plus a growing blog — all in the browser with no install. This page explains how to reach the team, what to include so we can fix things fast, and where to find answers without waiting on a reply.

What we can help with

Use the form below for anything that affects your experience on the site: broken timers, confusing instructions, partnership or press inquiries, and privacy-related questions. Pick the closest topic so your note lands in the right queue. Many questions are already answered in our FAQs or noted on the changelog.

Bug reports

Timer stuck, score not updating, audio missing, layout broken on mobile, or a benchmark that will not start. Pick Bug in the form and paste the full page URL (for example /cps-test/10-second/ or /typing-test/5-minute/), your browser, device, and what you expected versus what happened.

Features & UX

New timers, leaderboard ideas, accessibility tweaks, or copy that confused you on first visit. Say which tool your idea affects and whether you are on phone or desktop — that context helps us prioritize the changelog.

Blog & guides

Article corrections, topic requests, or broken links inside a post. Point to the article title or URL on our blog so we can fix or expand the guide quickly.

Privacy & legal

Data questions, cookie preferences, or formal requests related to how we handle scores stored locally in your browser. Read the policies first — many answers are already spelled out there.

Send a message

We read every submission. The more specific you are, the faster we can reproduce bugs or slot feature ideas into the roadmap. You do not need an account — just a valid email so we can reply.

  • Timer or score issues on any benchmark
  • Blog corrections or article requests
  • Privacy requests (see Privacy Policy)
  • Supporter credit after we ship your suggestion — see Supporters
0/20 characters
0/40 characters
0/200 characters (min 8)

Writing a useful bug report

1. Where: Copy the address bar — e.g. jitter click test or a 60-second spacebar test.

2. Environment: Chrome vs Firefox, Windows vs macOS vs Android, and whether you use a trackpad, mouse, or touchscreen.

3. Steps: “Started timer → clicked 40 times → score froze at 12” beats “it does not work.”

4. Expected vs actual: Tell us what you thought should happen. Screenshots are welcome but not required.

Rough response expectations

Urgent site issues

ASAP when seen

Mark subject line: [OUTAGE]

Everything else

A few days

Solo-maintained inbox — thanks for patience.

Common questions

Do I need an account to contact you?
No. The form is enough. We do not require sign-in for benchmarks today, and we reply to the email address you provide.
Where are my CPS or typing scores stored?
Personal bests and session data stay in your browser (local storage) unless we announce accounts later. That is why bug reports should mention browser and device — it helps us reproduce storage issues.
How fast will you reply?
Urgent site-wide problems get attention as soon as we see them — use [OUTAGE] in the subject line. Everything else is handled by a solo-maintained inbox, usually within a few business days.
Can I suggest a feature and get credited?
Yes. When your idea ships, we can list you on the Supporters page. Mention it in your message and watch the changelog for the release note.
Should I email instead of using the form?
The form is preferred — it routes by topic and keeps spam down. For the same inbox, use the Contact form with the right topic selected.

Partnerships & policies

Collaborations

For sponsorships, integrations, or press, use the form with topic Partnership / press. Include your site, audience, and timeline. We review inbound notes between benchmark fixes and blog updates.

Privacy & terms

Legal and privacy questions: start with our Privacy Policy, Terms of Service, Cookie Policy, and Disclaimer. Still stuck? Contact us with topic Support and quote the section you read.

Quick check

Still browsing?

Scoring rules, cookie behavior, every live benchmark, and long-form guides live in FAQs and the blog. Release notes land on the changelog first — worth a look before you hit send.