GEARCHECK LABGearCheck Lab is designed so hardware diagnostics run in the browser whenever server processing is unnecessary. This policy explains how diagnostic data, private contact messages, permissions, ordinary website requests, analytics and advertising-related services are handled.
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 diagnostic implementations use these values to update the page locally. They are not designed to upload individual hardware input telemetry to a GearCheck Lab server.
Touchscreen and stylus tools use browser pointer or touch events to display coverage, multi-touch, pressure, tilt, twist and related input values where supported. Motion-sensor tools use browser motion or orientation events after any required permission step.
These measurements are used locally to update the active diagnostic. Browser availability and permission behavior vary by device and operating system.
Display test patterns are generated in the page. Audio-output diagnostics generate tones with browser audio APIs. 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 level and spectrum-style visualizations.
Live camera and microphone preview pages do not upload the stream. The dedicated Mic Record & Playback Test can record a short audio clip locally after you start it; playback stays in the browser and is not sent to our server. Media tracks are stopped when you stop the test, when a device is removed, or when you leave the page, subject to normal browser behavior.
If you use the Contact page, GearCheck Lab processes the name, reply email, topic and message that you choose to submit. Those details are sent through a server-side mail handler to a private mailbox and are not displayed publicly.
The contact form does not intentionally attach hardware diagnostic readings, account details or device telemetry to your message. Contact messages are handled by our first-party server contact service and private inbox. Delivery or replies may use an email provider. Messages may remain in the private mailbox for as long as reasonably needed to read, reply to, prevent abuse, or maintain relevant correspondence.
The Internet Speed Test sends generated test bytes to our server and downloads test bytes from it. It does not upload your files. The server receives ordinary connection information needed to handle these requests. Internal Site Command measurement records page visits, referrer and campaign information, browser/device categories, a session identifier and engagement duration. It does not intentionally collect your diagnostic input readings or media streams.
Loading GearCheck Lab requires ordinary network requests to hosting and network infrastructure. Providers can receive information such as IP address, browser or user-agent information, requested URL, timestamps and security-related metadata.
GearCheck Lab is hosted on our own server at OVHcloud. Website requests pass through our web server and reverse proxy. Infrastructure and security logs are separate from the browser-local diagnostic readings.
GearCheck Lab retains the Google AdSense account metadata; the live production build currently removes the AdSense JavaScript loader associated with publisher account ca-pub-8048023190382309. Publisher account metadata identifies the site for review; it does not itself load an ad. If Google advertising resources are enabled in a later release, those services can receive ordinary web-request and device/browser information.
Depending on Google configuration, region, consent choices and whether ads are being served, Google and its advertising partners may use cookies, local storage or similar technologies for ad delivery, measurement, fraud prevention, frequency control and personalization where permitted. If Google ad serving is enabled, regions where Google requires it must use a Google-certified consent management platform.
Google Analytics uses Consent Mode. The Google tag can load before you make a choice so Google can recognise the measurement configuration, but analytics_storage is denied by default. Until you accept Analytics, the site does not allow Google Analytics cookies or Analytics storage. Google may receive limited cookieless measurement and consent signals.
The Metricool tracker is not loaded until you accept Analytics. Your Analytics choice is stored locally so the site can remember it, and you can reopen the Analytics preference control later. Advertising consent is separate from this Analytics preference. Before enabling Google advertising in the EEA, UK or Switzerland, a Google-certified consent mechanism must be configured where required.
GearCheck Lab uses Google Analytics 4 with measurement ID G-YT75XTBVM4 in Advanced Consent Mode. Before Analytics consent, Analytics storage remains denied and Analytics cookies are not permitted. If you accept Analytics, the site updates analytics_storage to granted so GA4 can use Analytics cookies and fuller measurement.
After Analytics consent, GearCheck Lab also loads the Metricool web tracker from tracker.metricool.com to measure site usage and content performance. Metricool is not loaded before Analytics consent.
GearCheck Lab does not intentionally send controller axes, button presses, keyboard input, mouse movement, camera video, microphone audio or other hardware-test readings to Google Analytics or Metricool. If Analytics is rejected, Analytics storage remains denied and the site attempts to clear accessible Google Analytics cookies that may have existed from an earlier acceptance.
The public diagnostic pages do not require a GearCheck Lab account session. Individual tools mainly keep temporary diagnostic state in page memory for the current visit.
The site stores your Analytics preference in browser local storage. If you accept Analytics, Google Analytics may set cookies such as names beginning with _ga, and Metricool may use browser storage or similar measurement technologies as part of its analytics service. If you reject Analytics after previously accepting it, GearCheck Lab changes Google Analytics storage back to denied and attempts to remove accessible Google Analytics cookies. You can also clear site storage through your browser settings.
GearCheck Lab relies on service providers for functions including hosting, private email delivery, optional Analytics and advertising, including Google AdSense. Those providers process information needed to provide their services under their own policies and applicable contractual or legal obligations.
Pages can also link to external documentation or services. Once you follow an external link, the third party's privacy terms and data practices apply.
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.
Private contact messages may be retained in the site's mailbox while reasonably needed for correspondence, corrections, support, abuse prevention or legal obligations. Hosting, Analytics, advertising and infrastructure providers can retain their own service data according to their operational, legal and security requirements.
GearCheck Lab is a general hardware utility and is not designed to create profiles of children or intentionally collect child-specific diagnostic information. Camera, microphone and sensor permissions should be used under the normal supervision and account controls appropriate for the device.
When Google’s consent API is available, the footer shows a separate Privacy and cookie settings control. It reopens Google’s advertising consent message so you can change your decision. This is separate from the Analytics preference control. If the advertising control is absent, Google’s consent API has not loaded on that page; browser blocking or advertising availability can affect it.
This policy changes when the site's actual data behavior changes. Advertising, Analytics, accounts, persistent preferences, server-side processing or new third-party integrations should be reflected here before or when they become active.
The Webcam Photo Quality Test can capture a local PNG after you choose Capture local photo. The Audio–Video Sync Clap Test records a short local camera-and-microphone clip only after you explicitly start recording. These photos and clips are not uploaded to our server. Stop releases device tracks; Delete clears the local displayed result. Downloaded copies remain on your own device. The Microphone Channel Test analyzes relative channel levels without creating a recording.
The SHA-256 File Checksum Verifier reads the local file you select, up to 50 MiB, and calculates its checksum in your browser. It does not upload or execute that file. MIDI input testing requests browser permission without system-exclusive access and does not send MIDI output commands. The USB/HID inspector displays selected-device descriptors without opening devices or sending commands; it does not display serial numbers. Browser permissions you grant can remain until changed in your browser site settings.
The Network Stability Monitor sends small HTTP probes to our speed-test server after you start it. The Bufferbloat and Loaded Latency Test sends temporary upload payloads and downloads test bytes, with up to 64 MiB per direction per run. These are network test requests, not uploads of your files. Ordinary server connection metadata may be logged. Hidden tabs and Stop interrupt active runs.
The Browser Storage Test stores one small diagnostic marker containing a random token and creation time in this browser for up to seven days. Its Clear test marker action removes only that marker. Reload or leaving a page normally clears in-memory diagnostic samples, but it does not remove this deliberately saved marker or files you downloaded.
The live site currently uses labelled promotions for our other websites. The AdSense publisher account metadata is retained for site review, but the production build removes Google ad-serving loaders and other external ad-network loaders. Google ads are not enabled by the new tools. If Google ad serving is enabled later, the implementation must use the required consent controls, including a Google-certified consent platform where Google requires one.
Creating or joining a WebRTC test temporarily stores your connection descriptions in GearCheck Lab server memory for up to three minutes. The pairing code is a temporary access token; share it only with a device you control. The test uses Google STUN at stun.l.google.com:19302, which receives your network address. The connected peer can learn network addresses through WebRTC. Test data travels between the paired browsers; there is no camera or microphone capture. Close disconnects the peer. Local inspection notes, comparison reports, video files and microphone processing clips are not uploaded. Downloaded reports and clips remain on your device until you delete them.
The DNS Record Lookup sends the public domain and record type you request to GearCheck Lab and the Cloudflare public DNS-over-HTTPS resolver. Do not submit confidential internal names. We query a fixed resolver and do not fetch the entered website. Bluetooth selection and an optional standard battery-service read begin only after your action; device names stay in your browser. Musical pitch, local audio files, battery observations, pen strokes and level-history logs are processed locally and not sent to analytics. Network consistency tests can download up to 32 MiB of generated payload plus protocol overhead. Hidden tabs interrupt active observations and device access. Multi-monitor synchronization shares pattern choices only between same-origin tabs.