Privacy Policy

Camera Test (/camera-test)

When you click “Start Test,” your browser prompts for one-time camera access via navigator.mediaDevices.getUserMedia(). The resulting live video stream is bound directly to a local HTML5 <video> element on your screen. DeviceChecker reads only technical stream telemetry (such as negotiated width, height, and frame rate) directly from the active track.

Optional Local Snapshot: You can optionally click “Take Snapshot” to capture a single still frame from the active video track using an in-memory HTML5 <canvas> element to inspect image clarity and resolution. This feature is 100% user-initiated, processes entirely in your browser's local volatile memory, and is never uploaded, transmitted, or saved to any remote server. You may optionally download the generated PNG file directly to your device. When you dismiss the preview, reset the test, or navigate away, the image data is wiped from browser memory.

When you stop the test, click “Test Again,” or close the page, all media tracks are explicitly terminated, instantly releasing hardware resources and shutting off your webcam LED indicator.

Microphone Test (/microphone-test)

Microphone testing requests audio input access to connect the stream to a client-side Web Audio API AnalyserNode. The browser computes real-time volume energy (Root Mean Square) inside local memory at 30 frames per second to drive the visual level meter. During standard volume testing, audio data is never saved, transcribed, or sent to any remote server.

Optional 3-Second Playback Loopback: To verify voice quality, volume balance, and background static, you can optionally click “Test Playback (3s)”. This uses your browser's standard MediaRecorder API to buffer exactly 3 seconds of sound into an in-memory audio Blob held in volatile RAM, plays it back once through your speakers via a temporary object URL, and immediately revokes the URL upon completion. The audio sample is never written to disk, never transcribed, and never leaves your computer.

When the test ends, audio tracks and the Web Audio context are explicitly closed, shutting off the microphone sensor.

Speaker Test (/speaker-test)

The speaker test plays audio outward and does not require or request any browser permissions. Test frequencies are synthesized client-side in real time using a standard Web Audio OscillatorNode. No audio files are downloaded, and no microphone or recording capability is activated.

Keyboard Test (/keyboard-test)

The keyboard test listens for standard browser keydown and keyup events while the page is focused, temporarily updating the visual key highlight states in local React memory. Keystrokes are never logged, stored in persistent storage, or sent over the network.

Mouse Test (/mouse-test)

The mouse test observes standard pointer and wheel events (such as left, right, middle clicks, scroll wheel deltas, and drag gestures) strictly within the interactive test pad element. No cursor trajectories, click patterns, or movement histories are recorded, tracked, or uploaded.

Browser & Device Info (/browser-info)

The browser and device info tool reads standard, benign browser and display properties (such as screen resolution, active viewport, preferred language, and User-Agent) that are already routinely exposed by web browsers to any website you visit. No permissions are requested or required. We strictly prohibit canvas fingerprinting, WebGL vendor inspection, or audio hashing. All telemetry is evaluated solely in your device's local memory and is never transmitted, collected, or stored.

Touchscreen Test (/touchscreen-test)

The touchscreen test evaluates touch contact coordinates and multi-touch point counts directly within your browser session to render the interactive coverage grid. Touch coordinates and gesture movements are processed entirely in your device's local memory in real time. No touch trajectories, handwriting inputs, or touch point histories are recorded, logged, or transmitted to any server.

Screen & Dead Pixel Test (/screen-test)

The screen and dead pixel test generates solid RGB color patterns directly within your browser DOM using standard HTML5 and Fullscreen APIs. It measures hardware refresh rate via high-precision client-side animation frames. No display contents, screenshots, or webcam streams are ever recorded, captured, or transmitted. All diagnostic visual fields execute 100% locally on your device.

Gamepad & Controller Test (/gamepad-test)

The gamepad test reads real-time controller telemetry — including button presses, analog trigger pressure values, and dual analog thumbstick axis coordinates — strictly in local browser memory via the standard W3C Gamepad API (navigator.getGamepads()). Controller input states are processed exclusively in volatile RAM to drive visual diagnostic highlights and deadzone visualizations. Controller inputs, device identifiers, and button press histories are never logged, stored in persistent storage, or transmitted across the network. The optional haptic vibration test triggers local actuator pulses directly through your browser without communicating with any remote servers.

Full System Diagnostic Checkup (/system-check)

The full system checkup wizard sequentially guides you through testing your browser environment, webcam video feed, microphone input, audio speakers, and screen display specs. Each hardware subsystem adheres strictly to the isolated privacy boundaries detailed above: webcam video and microphone audio streams are held exclusively in volatile browser RAM and all media tracks are explicitly terminated upon advancing between steps or exiting the page. The printable diagnostic verification receipt is rendered entirely client-side; no diagnostic results, device summaries, or hardware logs are ever transmitted to or stored on remote servers.