Contact

JoyCheck Contact: Bug Reports, Feature Requests, and Privacy

The JoyCheck contact channel is one email address: support@joycheck.io. Use it for bug reports, feature requests, Pro-tier questions, press, partnerships, or privacy concerns. Every message is read by a human, usually the same person who wrote the code you are using. We respond within 48 hours on weekdays and 72 hours on weekends, with no live chat, no ticket portal, and no paid support tier between you and a reply.

▶ Bug-report form

Send us a quick report

Browser, OS, controller, expected vs observed. That is all we need.

Leave blank if you don't want a reply.
Opens your email client · we reply within 2 business days.
TL;DR

Key takeaways

  • The JoyCheck contact channel is one email address: support@joycheck.io.
  • Replies come from a human within 48 hours weekdays, 72 hours weekends.
  • Genuine bugs jump the queue and usually get a fix or workaround within the same week.
  • For formal GDPR requests, you can also contact the Irish Data Protection Commission [1].

◆ Verified The support@joycheck.io inbox is monitored by Taimoor Bamazai, founder of Elites Algorithm Limited, a registered tech company in Dublin, Ireland. Reply turnaround is logged publicly in the changelog. Source: JoyCheck Notes blog.

01

How do I reach JoyCheck the fastest?

Email support@joycheck.io with a clear subject line that names the controller and the issue. We do not run a live-chat widget, do not operate a ticket portal, and do not gate response time behind a paid tier. One inbox, one founder reading every message, and a 48 to 72 hour reply window.

I read every message that lands in support@joycheck.io myself. After 15 years of building browser tools and shipping under my own name, I would rather take the inbound directly than route it through a triage team that loses the context.

For status, follow the JoyCheck Notes blog and the RSS feed [2], where we log changes and known incidents in public.

02

What kind of questions are in scope for support?

Email support covers anything that needs a real reply: bug reports (a controller does not detect, vibration does not fire, gyro reads wrong, a value is off), feature requests, Pro-tier account or billing questions once Pro launches, press and partnership inquiries, integration questions for the JoyCheck Notes blog, and any privacy concern covered by our privacy policy.

  • Bug reports. Anything where the tool reads incorrectly, crashes, or fails to detect a controller.
  • Feature requests. Especially ones tied to a specific controller model or use case.
  • Pro tier questions. Account, billing, refund, or feature questions when Pro launches.
  • Press and partnerships. Coverage, integrations, or co-marketing requests.
  • Privacy concerns. Anything covered by GDPR or our privacy policy.
03

What is out of scope?

Manufacturer hardware troubleshooting beyond what JoyCheck can test in-browser is out of scope. We can confirm whether your controller exhibits stick drift, button bounce, or dead-zone slop, but we cannot authorize a warranty claim or replace a damaged unit.

For those, contact your platform vendor directly. The full JoyCheck FAQ covers most controller-by-controller diagnostics already, before you need to email anyone.

  • Sony PlayStation Support [3] for DualShock and DualSense warranty.
  • Xbox Support [4] for Xbox Series and Xbox One controllers.
  • Nintendo Support [5] for Switch Joy-Con and Pro Controller.
  • Third-party manufacturers (8BitDo, Logitech, GameSir) at their respective support pages.
04

How quickly will I get a reply?

We aim to reply within 48 hours on weekdays and 72 hours on weekends. Bug reports get triaged the day we receive them, and genuine bugs (the tool does not read your controller, crashes, or shows wrong data) usually get a fix or a workaround within the same week.

Feature requests get logged and reviewed monthly. No auto-responses; every reply comes from a human, usually the same engineer who shipped the code.

If you do not hear back within seven days, your message likely got spam-filtered. Re-send with a different subject line, or reach us through one of the social channels on the right of this page.

05

What should I include in a bug report?

A useful bug report has six fields. With all six, we reproduce the bug in five minutes. Without them, we lose a day asking back for the same information.

  1. Browser and version. For example, Chrome 130, Firefox 132, Safari 18, Edge 130.
  2. Operating system and version. For example, Windows 11 24H2, macOS 15.1, Ubuntu 24.04.
  3. Controller make and model. Xbox Series controller, DualSense, Switch Pro, 8BitDo Ultimate.
  4. Connection type. USB-C wired, Bluetooth pairing, or USB dongle (8BitDo, GameSir).
  5. What you expected to happen.
  6. What actually happened. Attach a screenshot if the issue is visual; paste the JoyCheck readings if numeric.

For repeated dropouts or drift, include the actual numeric values the JoyCheck tester shows. "Stick X reads 0.18 at rest" is actionable; "the stick is broken" is not.

06

How can I follow JoyCheck updates?

New articles, controller-support announcements, and tool changelogs publish on the JoyCheck Notes blog and the RSS feed. The blog is the source of truth; social channels mirror highlights. Subscribe to the RSS feed if you want updates without an account.

  • Instagram. @joycheck.io for visual short-form.
  • YouTube. @Joycheckio for tutorial and teardown videos.
  • Reddit. u/joycheck for diagnostic threads.
  • GitHub. Joycheck [6] for the open changelog and any open-source utilities we publish.
FAQ

Frequently asked questions

Do you offer phone support?

No. Email is faster and produces an on-record reply that both parties can refer back to. Phone support would slow the queue and create reply-time inconsistency.

Can I get a refund?

The free tester has nothing to refund. Once the Pro tier launches, the published refund policy will live on this page and in the Pro signup flow.

Do you take pull requests?

The core JoyCheck tester is closed-source. Public utilities and templates published under github.com/Joycheck accept issues and PRs under their respective licenses.

Can I license JoyCheck for a clinic, school, or workplace?

Yes. Email support@joycheck.io with the use case, target volume, and required integrations. We respond within two business days with terms.

Where do I report a vulnerability?

Email support@joycheck.io with subject prefix [SECURITY]. We acknowledge within 24 hours and credit you in the changelog after a fix ships, unless you ask to stay anonymous.

REF

Sources & references

  1. Irish Data Protection Commission, dataprotection.ie
  2. JoyCheck Notes RSS feed, joycheck.io/feed
  3. Sony PlayStation Support, playstation.com/support
  4. Xbox Support, support.xbox.com
  5. Nintendo Support, en-americas-support.nintendo.com
  6. JoyCheck on GitHub, github.com/Joycheck