When you use this website to test your webcam, microphone, screen, or mouse, zero video frames or audio recordings are uploaded to any server. Every calculation, frame rate measurement, and color analysis runs entirely inside your browser's local sandbox memory.
1. Client-Side Processing Architecture
The WebcamTest Diagnostic Laboratory operates on a strictly client-side architecture utilizing modern W3C web standards, including the HTML5 MediaStreamTrack API, WebRTC MediaStream, Web Audio API, and HTML5 Canvas API.
When you initiate a diagnostic test (such as starting your camera or speaking into your microphone), your browser directly communicates with your operating system's hardware driver. The raw video and audio streams are piped directly into in-memory DOM elements (<video> and <audio>) rendered on your computer's screen. At no point in this pipeline does any audio or video packet pass through an external server, proxy, or relay.
2. Camera and Microphone Permissions
To provide diagnostic functionality, our tools request access to your input devices via the standard browser permission prompt (navigator.mediaDevices.getUserMedia):
- Permission Scope: Permission is requested exclusively for active diagnostic sessions. You are never forced to grant permanent access.
- Hardware LED Indicators: Modern cameras feature physical LED indicator lights wired directly to the sensor. The moment you click "Stop Camera" or navigate away from the page, our scripts call
track.stop()on all media tracks, immediately cutting the hardware link and turning off the indicator light. - Revoking Access: You can permanently revoke access at any time by clicking the padlock or tune icon next to your browser's address bar and setting Camera/Microphone permissions to "Block" or "Ask".
3. Snapshots, Recordings, and Exported Reports
Several of our tools allow you to capture test snapshots, record sample video clips, or export diagnostic reports:
- Snapshots: Image files are generated locally via
canvas.toDataURL()orcanvas.toBlob()as base64 memory URIs. When you click download, the file transfers directly from your browser memory to your hard drive. - Video Recordings: Captured clips (using
MediaRecorder) are buffered in temporary browser RAM and discarded as soon as the session closes or the page is refreshed. - Diagnostic Reports: JSON telemetry reports generated by our tools (listing measured resolution, frame rate, lux, and device names) are created on your machine via
URL.createObjectURL()and saved directly to your local files.
4. Local Storage Usage
We do not use tracking cookies or persistent identifier beacons. We use the browser's standard localStorage API for a single user-preference purpose:
wt_theme: Remembers your preferred interface visual appearance (Dark Mode or Light Mode) between visits so you don't have to toggle it every time you load the site.
5. Independent Verification
We believe privacy claims should be verifiable, not merely promised. You can independently confirm our zero-upload architecture using your browser's built-in developer tools:
- Press F12 or Ctrl + Shift + I to open Developer Tools.
- Switch to the Network tab and filter by WS (WebSockets) or Media.
- Click "Start Webcam" and speak or move in front of the lens.
- Observe the network log: you will see that no media data or video streams are transmitted across the network while testing.
6. Third-Party Hosting and Infrastructure
Our static HTML, CSS, JavaScript files, and vector icons are hosted on standard web servers. Standard HTTP access logs (including client IP address, user-agent string, and requested page URL) may be logged by web server infrastructure (such as Apache or Nginx) for security auditing, DDoS mitigation, and server maintenance purposes. These server access logs do not contain any biometric, video, or microphone audio data.
7. Changes to This Policy
We may periodically update this statement to reflect new browser capabilities or diagnostic features. Any modifications will be posted directly to this page with an updated revision date.
8. Contact Us
If you have questions, feedback, or technical inquiries regarding our privacy standards or hardware test implementations, please reach out through our project repository or contact our team via the About Us page.