The privacy claim is not just marketing copy. The site is built and tested so microphone audio, camera video, snapshots, and recordings stay in the browser.
The microphone meter reads audio samples with Web Audio. Webcam preview uses the browser video element. Snapshots are drawn to a local canvas. Recordings and downloads are local blob URLs. Speaker tones are generated by the browser instead of streamed from a server.
Those features do not require a media upload. The page can do the useful work locally because modern browsers already include the media APIs needed for preview, metering, recording, playback, and download.
The privacy bar watches network activity and reports requests that carry media plus uploaded media bytes. During a normal mic, camera, or speaker check, the expected media-upload count is zero.
Optional analytics is separate. If you accept analytics, MicAndCam sends only whitelisted interaction events such as a tool starting or completing. Those events do not include audio, video, snapshots, recordings, device names, or media blobs.
The automated privacy proof runs the tools with fake media devices, records all HTTP and HTTPS requests, and fails if it sees media-like payloads, blob URLs, device labels, audio files, video files, or unexpected third-party requests before consent.
The live verifier repeats the same idea against the deployed site. This makes the privacy message a tested release gate, not only visitor-facing copy.
No. Analytics events are whitelisted to basic interaction names and safe categories. Media bytes, blobs, frames, device names, and labels are not included.
Open your browser Network panel, run a mic or webcam test, and watch for uploads. The privacy bar also shows a live media-upload counter while you test.
It can be when the tool runs locally. MicAndCam analyzes microphone levels, camera preview, snapshots, and recordings in your browser and does not upload media. You can verify this with the live counter or your browser's Network panel.