YOUR TEST DATA
What the tester stores.
Controller input processing takes place in your browser. Here is how the tester’s own features use data.
Live readings
The tester JavaScript reads inputs locally. It does not send button presses, axis readings or test reports to a ControllerTester reporting server.
Optional snapshots
Choosing “Save snapshot on this device” stores a report in this browser’s local storage under ct-snapshots-v1. Up to ten are retained. A report includes the device name exposed by the browser, mapping, observations, browser user agent, time and any setup note you enter. New snapshots replace the oldest once the limit is reached.
Use “Clear saved snapshots” in the tester to remove these records. Clearing site storage in your browser also removes them. Private browsing, blocked storage or different devices may prevent saved records from appearing.
Downloaded reports
A report download creates a JSON file on your device. You control whether to keep it or share it. Review the device name, browser details and setup note before sharing a report publicly.
Theme preference and normal website requests
The colour-theme preference is saved locally under ct-theme. Your browser also requests website pages, scripts and images in the usual way. Hosting logs, analytics, advertising, affiliate links or other WordPress plugins operate separately from the tester and are governed by the website’s applicable policies. This page describes the tester feature; it is not an exhaustive statement about every service installed on the website.
Demo mode
Demo inputs are simulated and identified in saved reports. They are useful for exploring the interface and must not be interpreted as readings from a real controller.