Local processing policy

Privacy Policy

This privacy policy explains how controller diagnostics run locally, what permissions may appear, and what data the site does not need.

Local Processing Summary

Controller input values, MIDI notes, HID choices, and haptic settings stay in the browser.

Controller Data Stays In The Browser

GamepadTesterOnline.org is designed so controller data privacy is simple: core diagnostics run locally in the browser. Button presses, stick axes, trigger values, raw mapping data, vibration choices, polling samples, MIDI notes, and HID permission results do not need to be uploaded to a server for the gamepad tester to work. This privacy policy treats gamepad tester privacy as a product requirement, not an afterthought.

The site has no user account system, no login, and no file upload. It does not ask for names, addresses, payment details, or controller serial numbers. The privacy policy is written around the actual behavior of the controller diagnostics rather than generic collection claims, so controller data privacy remains tied to what the browser tools actually do.

If a user contacts the project manually, they may choose to include diagnostic details such as browser, operating system, controller model, connection type, or observed values. Those details are provided by the user outside the live tester. The site cannot see local controller values unless the user sends them through a separate communication channel.

Permissions And Browser APIs

The standard Gamepad API generally does not show a browser permission prompt, but it may require a connected controller and a button press. Haptic commands are user initiated. WebHID and Web MIDI are permission-based APIs and are requested only after a clear click on pages that need them. The prompt comes from the browser, not from a hidden background process.

A permission denial should not break the whole site. Pages that use optional APIs display unsupported or denied states and keep non-permission diagnostics available where possible. That approach protects controller data privacy by avoiding unnecessary prompts and by limiting advanced access to explicit workflows.

Embedded widgets follow the same principles. An iframe gamepad tester should run local browser diagnostics and should not collect raw controller input for the embedding site. Site owners who add their own analytics around an iframe are responsible for their own privacy practices.

Privacy protection does not make browser test results official or complete. The testing process still depends on browser support, permissions, connection mode, and local device behavior. If a user manually sends screenshots, logs, or values through contact or feedback, those details are no longer only local to the browser and should avoid unnecessary personal information.

Analytics, Logs, And Future Changes

Microsoft Clarity and Google Analytics are used for ordinary page-level analytics, such as page views, referrers, approximate device and browser information, and general interaction patterns. These tools are not required for the core gamepad tester and should not be used to capture raw controller values, HID reports, MIDI messages, exact input sequences, or haptic settings.

Static hosting and routine server logs may record standard request information such as page URL, timestamp, user agent, and IP address depending on the hosting provider. Those logs are separate from controller diagnostics and are not needed to read gamepad input.

The policy may be updated as features evolve, especially if multilingual pages, analytics settings, or additional embed controls are added. The guiding rule should remain the same: collect as little as possible, keep controller diagnostics local, and explain permission-based browser behavior clearly.

Cookies, Local Storage, And Third-Party Services

The site may use browser local storage for interface preferences such as theme settings. Local storage stays in the user's browser unless the user clears it or the browser removes it. It is not needed to read live controller input.

Microsoft Clarity and Google Analytics may use cookies or similar browser identifiers to provide page-level analytics. Those services are separate from the Gamepad API, WebHID, Web MIDI, vibration controls, and raw diagnostic values.

Users can limit or clear cookies, local storage, and site data through browser settings. Blocking analytics or clearing storage may affect preference persistence or aggregate page metrics, but it should not prevent the core controller tests from processing live input locally.

Questions Users Ask

Short answers for common diagnostic decisions on this page.

Does the gamepad tester upload my button presses?

No. Button and axis values are processed locally in the browser.

Why do WebHID or MIDI prompts appear?

Those APIs require explicit browser permission and are only requested after a user click.

Are analytics installed?

Yes. Microsoft Clarity and Google Analytics are used for page-level analytics, but core controller diagnostics run locally and analytics should not capture raw controller input.

Useful Next Checks

About the project

Read how local browser diagnostics and original content are handled.

Read troubleshooting paths

Fix detection, Bluetooth, permission, browser, and mobile issues.

Open all tools

Choose the right diagnostic page for the controller symptom you see.