Privacy policy

1. Short version

You press Start test, the browser asks for microphone access, and the audio stream goes straight into an AudioContext in this tab. That is the whole audio path: there is no audio upload endpoint and no server receives your voice. The analytics scripts described in section 6 make their own requests for visit data, but they cannot read the microphone stream.

2. Microphone permission

The page calls getUserMedia only after you press Start test, not on load. The browser decides whether to prompt, and the permission is stored by the browser, not by us. You can allow it once, allow it permanently, or decline it.

Device names appear in the microphone selector only after permission is granted, because browsers hide them beforehand. Those labels are read locally to fill the dropdown.

3. Local processing

Level, waveform, spectrum, peak, speech level, noise floor, signal to noise ratio and clip counts are computed from the stream in memory. The three processing switches (Denoise, Echo cancel and Auto gain) are browser constraints applied to the local stream; the browser may ignore a constraint it cannot satisfy.

Listen live routes the live input to your own speakers. It is an output path on your device, not a transmission.

4. Audio data and visit data

We do not receive your voice, your recordings, the device names shown in the microphone selector, or any audio derived data. There is no sign in and no contact form on this page, and the test never asks for your name or email address.

Third party analytics on this page do collect visit data: pages viewed, referrer, browser and device type, approximate region derived from IP, and interactions such as clicks and scrolling. Microsoft Clarity may also record session replays and heatmaps of the page. These providers may set cookies or similar identifiers. None of them receive microphone audio, readings or the five second clip.

5. Recording and storage

The 5 second recording is assembled in memory from the same audio samples used for the visualisations and encoded into a WAV file in your browser. Play and Download use a temporary object URL created locally. Nothing is written to a server, and the clip disappears when you reload or close the tab.

Readings and audio are never written to localStorage, sessionStorage or cookies by the tool itself. The only value the tool stores locally is your colour theme preference, under a single localStorage key, which is a display setting and contains no audio or personal data. Analytics providers may write their own cookies or identifiers, as described in section 6.

6. Third party scripts

Three analytics services: Baidu Tongji (百度统计), Microsoft Clarity, and Google Tag Manager, which in turn loads Google Analytics. They only load after you choose Allow all in the consent bar; until then the page makes no request to them. Once loaded they measure visits and page interactions, and may set cookies or similar identifiers on their own domains. Clarity can record session replay and heatmaps of the page interface. None of these scripts are given access to the microphone stream, the readings or the recording.

Fonts are served from this same domain, so rendering text makes no third party request. The optional 3D view loads a three.js file hosted on this same domain too; it is a rendering library and sends no data anywhere. You can block analytics scripts with browser tracking protection or an extension without affecting the mic test.

7. Your choices and revoking access

Press Stop in the tool to end the stream immediately. To revoke permission entirely, open the site settings in your browser address bar and set Microphone back to Block or Ask. On mobile the same control lives in the system app settings for your browser.

You can clear the theme preference at any time by clearing this site data in your browser. Clearing it simply returns the site to following your system colour scheme. Your analytics choice is saved the same way, in this browser alone, under the local storage key mt-consent. The Cookie settings link in the footer reopens the bar: choosing Essential only there stops the analytics scripts immediately, and clearing this site data erases the choice as well. Analytics cookies can be blocked with browser tracking protection or removed by clearing cookies for this site.

8. Changes and contact

If this policy changes, we update the date above and describe the change here. Questions about this page can be sent to ha0719#gmail.com (replace # with @).

This page is written for a general audience and does not assert a specific legal jurisdiction or a named data controller. If you need a formal determination for your region, contact us and we will respond with the details that actually apply.