Privacy Policy
MicTest's privacy policy — your voice never leaves the tab, what the site can and cannot see, and the data that never exists.
Last updated: October 2026.
A microphone tool lives or dies on its privacy story, so here is ours in concrete terms rather than reassuring adjectives.
Your audio
Nothing you say is transmitted, stored, or logged — by design, not just by policy. MicTest is a static site: files served to your browser, with no application server and no endpoint that accepts audio. The mic stream feeds a local audio graph (meter, waveform, recorder) that lives inside the tab. The test recording is an in-memory blob; closing the tab destroys it. If you want proof, open your browser’s Network panel while you talk, or run the whole test with the network cable unplugged.
Granting mic permission lets this page hear the mic for as long as the tab is open. Your browser shows a recording indicator the whole time, and closing the tab ends the capture — the permission model is enforced by the browser, not by our goodwill.
What we collect
- No accounts, no analytics of our own beyond the small cookieless usage-count ping described on this page. Nothing is persisted — the tester doesn’t use cookies or localStorage, so every visit starts clean.
- Standard server logs. Cloudflare, our host, processes routine request metadata (IP address, user agent, timestamp) to deliver the static files and defend against abuse. That’s the entire server-side data trail.
- Device labels. Only after you grant permission does the page see device names — a browser rule, described in how mic permissions work. We never transmit them.
Usage counts
The only analytics here is a small cookieless ping per page view. It sends the page address, the referring site’s domain, the page language and any campaign tag in the link, and when you leave it sends how many seconds the page was open.
When it arrives, our server adds the time, the country and network provider Cloudflare reports, a device type guessed from your browser’s user-agent (phone, tablet, desktop or bot), what kind of source the visit came from, and a label for filtering out automated traffic. For a count of visitors per day, it saves a hash of your IP address, browser, the date and a secret value instead of the IP itself; the hash is different every day. Grades, test results and anything else you enter are not sent, and there are no cookies.
Advertising
If ads are enabled, partners such as Google AdSense may set cookies to serve and measure advertising; personalization can be switched off in your Google ad settings. Ad code has no access to the mic stream — capture and ads run in separate worlds.
Contact
Privacy questions or requests: hello@tolerence.net, or the contact page.