Privacy Policy

GamepadTest's privacy policy — controller readings stay inside your tab, what little we collect, and why the architecture makes misuse impossible.

Last updated: September 2026.

The short version

A controller tester exists to read your pad — and that data never leaves this tab. GamepadTest is a static site: files delivered to your browser, with everything after that running locally. No backend endpoint accepts gamepad data, so exfiltrating it isn’t merely disabled, it’s architecturally impossible — there is nowhere to send it. Load the page, cut the network, and the tester still works completely.

What the page can see

Until you press a button, browsers expose nothing at all — that gate is theirs, deliberately, so a page can’t fingerprint hardware you never touched. After the first press, the Gamepad API hands this page the pad’s ID string, mapping, button and axis state, a timestamp and its rumble capability — the minimum the API offers, and all of it stays in-page. No cookies, no localStorage, no session state: nothing is persisted, so there is nothing to clear.

Server-side data

Hosting is Cloudflare: to serve static files and fend off abuse it handles the usual connection metadata — IP address, user agent, request time and path. No application database stores gamepad data; the separate Google requests are described below.

Google Analytics 4

We use Google Analytics 4 (GA4) to understand traffic, feature use and site performance. Google processes this information for us and may process it outside your country. See Google’s Privacy Policy.

This root uses its own GA4 Measurement ID. Before GA is configured, Google Consent Mode sets analytics_storage, ad_storage, ad_user_data and ad_personalization to denied. We set ads_data_redaction to true, url_passthrough to false, and both allow_google_signals and allow_ad_personalization_signals to false. GA4 therefore sends cookieless measurement requests and may not read or write analytics or advertising cookies. Google receives each measurement request, including the IP address in transit, and may derive a coarse location. It also receives browser, device, language and network metadata.

Enhanced Measurement is currently enabled, so GA4 may also automatically measure page views, scrolls, outbound-link clicks, site searches, video interactions, file downloads and form interactions, together with relevant link, file or form metadata. Our integration does not send form values.

Our adapter supplies the page location as the origin and path only—never the query string or fragment—and reduces the referrer to its origin. Tool use is sent as a tool_action event with a normalized action_name. Our custom adapter never sends tool inputs or content, uploads or photos, form values, a user ID, or values from local storage.

You can block Google Analytics requests in your browser or a content blocker; the core tools continue to work.

Advertising

If ads run, networks like Google AdSense may set their own cookies for serving and measurement; personalization is controlled in your Google ad settings. Ad code runs in a separate world from the tester and has no access to gamepad state.

Questions

hello@tolerence.net, or the contact page.