Privacy
Your voice stays with you.
Umbot is built so we couldn't listen in even if we wanted to. Here is exactly what happens to your audio, in plain language.
The short version
- All inference is local. The detection model runs in your browser, on your device. Audio is never uploaded.
- Nothing you say is stored. Audio exists in memory for about a second, then it’s overwritten by the next second.
- Detections stay on your screen. The recent-cues list lives in the open tab and is gone when you close it.
- No accounts, no analytics, no ads. And no audio “samples collected to improve our service.”
Optional local evaluation recording
Local development builds include an evaluation control in Advanced. It is off by default and records one complete listening session only after you explicitly enable it. The audio, model scores, speech-activity observations, and annotations remain in this tab until you discard them or begin another session; downloading creates local copies that you control. Umbot does not upload them. The recording control is not included in production builds.
How inference stays local
When you press start, your microphone streams into a short in-memory buffer. A compact filler model and a speech-activity model, running via WebAssembly inside your browser, inspect that buffer. They produce filler candidates, speech probability, and temporary input-condition measurements, all of which stay in your tab’s memory. No audio, transcript, detection, or room measurement ever appears in a network request.
What’s stored on your device
To start fast and work offline, Umbot keeps a copy of the app and the model files in your browser’s local caches, alongside a record of which model version was verified. That’s it. Clearing this site’s data in your browser removes everything.
What actually touches the network
Downloading the app, fetching the model, and checking for model updates are ordinary web requests to our servers. Like any website, our hosting provider sees standard request metadata such as IP address and browser version in its logs. Those requests carry no audio and no detection data, because that information never leaves your device.
Permissions
Umbot asks for microphone access only when you press start, and you can revoke it in your browser at any time. While listening, it may also hold a screen wake lock so your device doesn’t doze off mid-session. That’s the full list.
Changes and contact
Umbot is test software operated by Zaks.io, LLC, and this page will evolve with the product. When our practices change, the plain-language explanation here changes with them. Questions go to isaac [at] zaks.io.
Effective July 19, 2026.