Cookies and browser storage.

A cookie is a small value stored by the browser that can be sent with web requests to the relevant domain. Cookies are commonly used for sessions, preferences, analytics, and advertising.

localStorage is separate browser storage available to website JavaScript. Values in localStorage are not automatically attached to every web request. GPADLAB uses localStorage in selected tools for local-only history, presets, or readings.

GPADLAB's diagnostic tools do not require account, login, shopping-cart, or preference cookies. The site has no public diagnostic-tool account system, so there is no login-session cookie required to run a controller test.

Analytics cookies, where present, are separate from the core diagnostic functions. Blocking them does not prevent the browser-based controller tools from operating.

When Google Analytics 4 is enabled on GPADLAB, the Google tag can set first-party analytics cookies. Google's current gtag.js documentation lists _ga, used to distinguish users or browser instances, and _ga_<container-id>, used to persist session state.

GPADLAB's current site code does not override Google's default cookie-expiration setting. Google documents a default expiration of two years for these cookies, with the expiration generally refreshed when analytics hits are sent. These are analytics identifiers, not GPADLAB login credentials.

GPADLAB does not have a diagnostic-tool account User ID connected to GA4 in the application code.

When Plausible Analytics is enabled, Plausible is used for aggregate site measurement without setting cookies or persistent identifiers in the visitor's browser. Plausible states that raw IP addresses are not stored and that its visitor identifier changes daily.

Plausible's cookieless measurement is separate from any localStorage that GPADLAB's own diagnostic tools may use.

Selected GPADLAB tools save data locally so useful history or configuration can survive a page refresh or later visit. Current examples include recent Controller Health Score runs, recent audio-latency and FPS-test runs, controller-mapping presets or the current mapping, and battery-health readings.

This information remains in your browser's site storage until it is cleared, removed by the browser, or overwritten by the relevant tool. Saving it locally does not itself upload the record to GPADLAB.

You can block or delete cookies through your browser's privacy or site-data controls. You can also clear GPADLAB's local site data to remove locally saved tool histories and presets.

Blocking Google Analytics cookies or scripts does not disable the core GPADLAB controller tests. Clearing localStorage can remove locally saved histories, mappings, or battery records, so those local features may start fresh afterward.

Google also provides a Google Analytics Opt-out Browser Add-on for users who want to prevent Google Analytics measurement across supported sites.

GPADLAB's current application code does not implement a site-specific Do Not Track switch that conditionally prevents Google Analytics from initializing. Enabling the browser's DNT preference alone should therefore not be treated as a guarantee that analytics scripts will not load.

If you want to block analytics measurement, use your browser's cookie or content-blocking controls or Google's Analytics opt-out tooling.

GPADLAB does not currently rely on social-media widgets, advertising widgets, or embedded login providers for its core controller tools. Ordinary outbound links to other websites do not by themselves set those sites' cookies on GPADLAB.

If GPADLAB later adds an embedded service that stores information in visitors' browsers, this policy will be updated to describe that use.

For broader information about analytics, controller diagnostic data, contact and contributor submissions, IP-based abuse protection, data retention, and privacy requests, see our Privacy Policy.

Questions about cookies or browser storage can be sent to contact@gpadlab.com.