Privacy at JoyCheck

JoyCheck is built to send zero controller data anywhere: every check runs in your own browser, which you can confirm in DevTools.

Updated on 2026-05-26 by Taimoor Bamazai, founder of Elites Algorithm Limited (a registered tech company in Dublin, Ireland).

JoyCheck sends zero controller data anywhere. Every button press, analog reading, and vibration trigger stays inside your browser tab. The tester reads from the W3C Gamepad API the browser already exposes, writes to DOM elements only, and never opens a network connection for input. You can confirm this in DevTools in under a minute, without trusting our word for it.

Does JoyCheck collect any controller data?

No. JoyCheck does not transmit controller input to any server, ever. The tester reads from navigator.getGamepads() on every animation frame and writes only to DOM elements on the page. There is no fetch(), no XMLHttpRequest, and no WebSocket touching controller state.

In 15 years of building browser tools, I have not shipped a single line of code that sends gamepad input upstream from JoyCheck. The architecture would not survive a code review if it did, because the W3C spec lets us avoid the network entirely.

This separates us from a category of online controller-test sites that proxy input through their servers for analytics or A/B testing. Those sites can see every button you press while the tab is open.

JoyCheck cannot, by design. The full request-flow walkthrough lives on our how-it-works page, and the API itself is documented on the MDN Gamepad API reference.

How can I verify JoyCheck sends nothing?

Open your browser’s DevTools, switch to the Network tab, and exercise the tester for thirty seconds. No requests fire from joycheck.io for controller input events, because the Gamepad API resolves entirely inside the browser process. The check below takes under one minute, requires no install, and works on any modern browser.

1. Open the controller tester in Chrome or Firefox.
2. Press F12 or right-click and choose Inspect.
3. Click the Network tab and clear the log.
4. Press any button on your controller and exercise the sticks for 30 seconds.
5. Watch the Network panel; no requests fire from JoyCheck for controller events.

You will see a small number of static requests on first page load: fonts, CSS, the page HTML itself. After that, the tab stays silent for as long as you test. Any future request that did appear would be immediately visible with full headers and payload.

What about website analytics and cookies?

The controller tester still sends zero data. No analytics, no cookies, and no third-party scripts run inside the tester itself, and you can confirm that in DevTools exactly as described above. That does not change.

The website around it (the pages, guides, and menus) uses Google Analytics 4, loaded through Google Tag Manager, so we can see which guides are useful and how the site performs. This runs only if you accept in the cookie banner. If you decline, or simply ignore it, no analytics or advertising cookies are set and no analytics data is sent to Google: every measurement tag stays blocked until you opt in. The one Google request you would still see in DevTools is the Tag Manager script file itself, a static download that carries no data about you or your visit.

• Consent first. Analytics and any future advertising tags stay off until you opt in. You can change or withdraw your choice at any time from the Cookie settings link in the footer.
• What we measure, only after consent. Page views, scroll depth, outbound and download clicks, and anonymous performance (Core Web Vitals). We never collect names, emails, or controller input.
• No advertising trackers today. No Meta Pixel, no TikTok Pixel, and no Google Ads remarketing are active. If we ever add advertising, it runs through the same consent gate and we will update this page first.
• Server access logs. IP address, user-agent, page requested, response code. Retained 30 days for security and abuse prevention. Never tied to tester activity.

For the broader product story, see our trust comparison page.

What changes if I sign up for the planned Pro account?

If we launch the Pro tier (saved controller profiles plus advanced DualSense metrics, around $5 a month), the data story shifts only for users who explicitly opt in at signup. The anonymous browser-only experience stays unchanged, and the free tester continues to operate without any account requirement.

Even for paying account holders, we store profile preferences (deadzone, calibration, layout name), never raw input streams. Profiles save locally first, in your browser.

• Profiles save locally first in your browser (IndexedDB and LocalStorage).
• Sync to an account server is opt-in only at signup.
• Synced data is limited to deadzone settings, custom calibration values, and saved layout names. Input streams stay in-browser as today.
• Account-level data is covered by the GDPR rights below.

What GDPR rights do I have?

We operate from Dublin, Ireland, so the General Data Protection Regulation applies. Every user gets the same three rights worldwide: access to any data tied to your email, deletion of that data on request, and portability in machine-readable JSON. We respond to a request within two business days at no cost.

• Right of access (GDPR Article 15). Receive a copy of any data tied to your email within 30 days.
• Right to erasure (GDPR Article 17). Delete any data tied to your email within 30 days.
• Right to data portability. Receive your stored profiles in a machine-readable format (JSON).

Email support@joycheck.io for any of these requests, or use our contact page. We respond within two business days, on-record.

When did this policy last change?

This page was last updated on 2026-05-26. Material changes are noted at the top of the page with the new effective date, and we update this policy whenever we change what data the site or widget touches, not on a fixed schedule. The full terms-of-use are kept on the separate JoyCheck terms page.