Controller input
The site reads button values, axis values, device names, mapping, and timestamps through the browser's Gamepad API. These values are rendered locally and are not uploaded to a server.
Generated reports are created in your browser. You decide whether to copy or download them.
Microphone recordings
Microphone access is requested only after you press the recording button. The browser permission dialog controls access. Audio clips are recorded and played locally through MediaRecorder and are not uploaded by this site.
You can delete the local clip from the page at any time.
Analytics boundary
The site uses Google Analytics and Microsoft Clarity for basic traffic, page-view, and usability analytics. Live controller testing areas are marked with Microsoft Clarity masking so controller names, button values, axis values, microphone status, and generated report contents are not captured in Clarity recordings.
What stays local
Button values, axis values, controller names, microphone clips, and local reports are shown in your browser session. The site does not need an account to display those readings.
If a future feature changes how data is handled, that change should be explained before the feature is used. The current site is built around local diagnostics and user-controlled sharing.
- Review the privacy note before recording microphone input.
- Local reports stay under your control.
- Controller identifiers are treated as diagnostic context, not account data.
Data choices you control
You decide whether to press a microphone record button, copy a report, download JSON, or clear local history. Browser storage can keep local report history on your device, but that history is not a server account.
For practical safety, review a report before sending it to another person. Remove device names or notes you do not want to share, especially when using a shared computer.
- Clear browser data to remove local history.
- Review reports before sharing.
- Do not record private audio for a simple device check.
Browser storage
Site data, localStorage, downloaded files, and screenshots are managed by your browser and operating system after the page creates them. If you use a shared computer, clear local history after testing.
Translated pages and embedded widgets follow the same local-processing model. A translated page does not change where controller readings are processed, and an iframe does not create a server account.