Privacy, plainly.

All demos on this site — MixLab Analyzer, VoiceLab QA, HearLab Companion, SignalLab Indexer, CueLab Monitor, SkillLab Challenge — run entirely inside your browser. No audio data is uploaded to any server.

When you upload an audio file, the file is decoded by your browser’s WebAudio API. The analysis runs as JavaScript on your own device. The file is never copied or transmitted. When you close the page, the audio is gone.

When you use the live microphone in VoiceLab QA, HearLab Companion, or SkillLab Challenge, the same applies: the audio is captured via the browser’s standard MediaRecorder API and processed in-place. Nothing leaves the browser.

One exception with explicit notice: HearLab Companion’s live captions feature uses the browser’s built-in Web Speech API. On most browsers, this routes audio to a provider (typically Google) for transcription. We do not send anything to our own servers, but if you use captions, the browser’s speech provider sees the audio. This is a browser-level integration, not an AudioLab choice. HearLab will work without captions if you prefer to keep audio strictly local.

SkillLab Challenge stores your scores in your browser’s localStorage so progress survives a page refresh. This data lives only on your device. If you clear your browser storage, your progress is gone.

HearLab Companion check-ins are also stored in memory during your session. The "Export summary" button generates a JSON file you can download or share — but the file is only created on click, never uploaded.

We store your theme preference (dark/light) in localStorage. That’s it for cookies and local state on AudioLab.tools itself.

We do not use Google Analytics, Meta Pixel, or any third-party tracking. If we add analytics in the future, it will be a privacy-respecting platform with no cross-site tracking, and this page will be updated to reflect that.

Standard server-side request logs (IP, user-agent, referrer) may be retained briefly for security and abuse prevention. They are not joined to any user identity, and they are not shared with third parties.

If you email any of the addresses on the contact page, we keep your email and any data you send for as long as it’s relevant to the conversation. We do not add you to a marketing list.

Several labs (especially SignalLab and VoiceLab) are heading toward server-side products via the AudioLab API. Those products will have their own clearly-stated data handling policies, including what we process, where it’s stored, and for how long. This page covers AudioLab.tools today; the API will have its own terms when it launches.

HearLab is a non-medical companion app. It does not diagnose, treat, or replace audiological care. It does not collect medical information. If you log notes through the HearLab demo and you want them deleted, refresh the page — there is no server side to this preview.

Production HearLab will be more explicit about consent, encryption-at-rest, and data export rights. We will publish that policy before any production version goes live.