GearCheck Lab is designed so hardware diagnostics run in the browser whenever server processing is unnecessary. This policy explains what the current site code does with device information, media permissions and ordinary website request data.
Controller tools read values exposed by the browser Gamepad API, such as axes, buttons, mappings, timestamps and connection state. Keyboard and mouse tools read browser input events while the relevant test is active.
The current diagnostic implementations use those values to update the page locally. They do not include code that uploads individual hardware input telemetry to a GearCheck Lab server.
Display test patterns are generated in the page. Audio-output diagnostics generate tones using the Web Audio API. These tools do not need to send your display observations or generated tone settings to a server in order to function.
Your actual acoustic output remains controlled by your device, operating system, browser, amplifier, speakers or headphones.
Webcam and microphone tools request access through the browser's MediaDevices API. The live webcam preview is attached to a local page element. Microphone tests analyze short waveform buffers for a level meter.
The current site code does not record, save or upload camera video or microphone audio. Media tracks are stopped when you press the tool's stop control or leave the page, subject to normal browser behavior.
Like most websites, loading GearCheck Lab requires network requests to the hosting infrastructure. The hosting and network providers can receive ordinary request information such as IP address, user-agent/browser information, requested URL, timestamps and security-related metadata.
GearCheck Lab is currently deployed through Vercel. Provider-managed request logs and security processing are governed by the hosting provider's systems and policies rather than by the browser-local diagnostic code.
The shared interactive React interface currently requests stylesheet/font resources from Google Fonts for the site's display typography. A request to that external provider can expose ordinary network metadata such as IP address, browser information and request timing to the provider.
This font request is used for presentation, not for GearCheck Lab analytics or advertising. Standalone diagnostic and policy pages use local/system font fallbacks where configured.
As of the policy date above, the current GearCheck Lab repository contains no Google Analytics, Google Tag Manager, AdSense or equivalent advertising/analytics scripts.
If analytics, advertising or other third-party tracking is introduced later, this policy should be updated to describe the relevant provider, purpose, cookies or storage and consent choices where applicable.
The current public diagnostic pages do not require a GearCheck Lab login or account session. Individual tools mainly keep temporary state in page memory for the current session.
Hosting, browser or future third-party services can have their own necessary storage behavior. This policy will be updated if GearCheck Lab intentionally adds persistent first-party preferences or tracking storage.
Pages can link to third-party services, including the public project issue tracker used for technical feedback. Once you follow an external link, the third party's privacy terms and data practices apply.
Do not post passwords, authentication tokens, private account information or other sensitive personal data into a public issue or public troubleshooting report.
Browser-local diagnostic readings are not designed to be retained by GearCheck Lab after the page session. Reloading or leaving a tool normally clears that in-page test state.
Ordinary hosting logs can be retained by infrastructure providers according to their operational and security practices. GearCheck Lab does not promise a specific provider log-retention period that it does not directly control.
GearCheck Lab is a general hardware utility and is not designed to create profiles of children or intentionally collect child-specific information. Camera and microphone permissions should be used under the normal supervision and account controls appropriate for the device.
This policy should change when the site's actual data behavior changes. In particular, advertising, analytics, accounts, persistent preferences, server-side file processing or new third-party integrations should be reflected here before or when they become active.