Test data
A started tool may read `deltaX`, `deltaY`, `deltaZ`, `deltaMode`, modifier states, relative timestamps, and logical middle-button events inside its target. The data is kept in component memory, used to draw metrics, and removed when reset, refreshed, or closed. JSON and CSV downloads are created locally at your request. The testing code does not submit its in-memory sample arrays or the contents of those downloads to an API route, Server Action, database, or account system.
The event tester deliberately omits pointer screen coordinates. Exports do not add a name, email, device serial number, advertising identifier, or account identifier. A file you download is under your control; review it before sharing it with another person or service.
Browser storage
The key `swt-theme` stores a light or dark theme choice and `swt-locale` may store a language choice. `swt-test-history-v2` stores versioned summary records, including optional counter and virtual-challenge summaries, only after an explicit Save results on this device action. It keeps at most 20 records per test type and 100 total. A legacy `swt-speed-runs-v1` value is backed up and explicitly migrated when valid; unparseable V2 data is preserved in a backup key where storage permits. PNG score cards are drawn and encoded on demand and are not added to localStorage. Microsoft Clarity and Google Analytics may separately set cookies or similar identifiers for analytics.
localStorage remains on the device and browser profile where it was created. Other people with access to that profile may see saved preferences, labels, summaries, and baselines. Test Results lets you delete one record or clear all records. Do not save history or include a label in a score card on a shared device if you do not want that data retained or exported.
Analytics, ads, and external links
The site uses Microsoft Clarity for behavioral analytics such as page interactions, session recordings, and heatmaps, and Google Analytics 4 for traffic and site-usage measurement. These third-party tags send usage information to Microsoft and Google and may use cookies or similar browser identifiers according to their configurations. Tool areas are explicitly masked from Clarity recordings. The analytics adapter may send only allow-listed lifecycle actions such as tool view, start, pause, completion, save, export, related-tool click, and language switch with low-cardinality context. It does not send raw WheelEvent fields, timestamp sequences, labels, local result IDs, or exact scores, and the site does not run advertising code.
Microsoft and Google process analytics information under their respective terms and privacy statements. The tests do not depend on analytics and continue when a tag is blocked or unavailable. You can control or delete site cookies through your browser, and browser privacy tools may block these tags without disabling the core wheel tests. Links to technical references or manufacturer support open resources controlled by their respective operators; their privacy practices apply after you leave this site.
Changes and questions
Material changes will be reflected in this policy and its stated update date. A change to storage, external requests, analytics, contact handling, or exports requires a matching policy review. You can use the Contact page for privacy questions once the deployment owner has configured a real address.