Fact · Voice privacy and security
HoldSpeak's security document says that for browser mic capture the WAV goes to the user's own hub, local Whisper transcribes it, and HoldSpeak does not keep the audio. The document gives no number of days.
Quote found word for word on the live source, last checked October 25, 2026
In the source's own words
“The WAV goes to your own hub, local Whisper transcribes it, and HoldSpeak does not keep the audio (16 MB cap).”
HoldSpeak SECURITY.md: Security and privacy (GitHub repository), karolswdev, GitHub (karolswdev/HoldSpeak), 2026, Section 4, Egress points, Browser mic capture row.
Open the original- What it measures
- The row covers the browser route, used when the user holds the mic or talks in the browser, or when open-mic detects an utterance. Open-mic posts one WAV per utterance, and the browser detects speech with energy and no model. The 16 MB cap is a limit on the upload.
- What it does not show
- The document covers this route only. It does not state retention for the other audio paths it lists, such as the paired device link or the iPad meeting recording. It is the maker's own description and has not been audited.
In the data
A row of How Long Voice Assistants Keep Your Recordings, as HoldSpeak, browser mic capture: HoldSpeak does not keep the audio days.
- Service
- HoldSpeak
- What is kept
- Audio recordings
- When
- Other
- As of
- 2026-10