Why Chat Sites Ask for Microphone Access - and What They Get
What granting microphone permission to a website actually allows, what the browser will not let a site do, how to verify nothing is listening, and how to revoke it.
A voice chat site cannot work without your microphone, so it has to ask. That prompt still makes people hesitate, and reasonably so - it is one of the few permissions a browser treats as genuinely serious.
Here is what the permission does and does not grant, and how to check rather than trust.
What the site can do once you allow it
It can capture audio from the microphone you selected, while the page is open, and send that audio somewhere. On a voice chat platform, "somewhere" is the person you are matched with.
On TalkLive that transport is WebRTC. The audio is encrypted in transit and, in production, relayed through a TURN server for connections that cannot go directly peer to peer. TalkLive does not record or store it. What we can never prevent is the person on the other end recording what they hear on their own device - no platform can, and you should assume it is possible on any voice service.
The permission is per site and per browser. Granting it to one site grants nothing to any other.
What the browser will not let it do
It cannot capture audio when the tab is closed. Closing the page ends the stream.
It cannot take the permission silently. Browsers require an explicit grant, triggered by something you did, and they will not accept it from a hidden or background frame.
It cannot hide that it is listening. Every major browser shows an indicator in the tab and the address bar for as long as a page holds a microphone stream, and macOS and Windows add a system-level indicator of their own. This is the part worth knowing: a site cannot listen without the browser telling you.
It cannot reach your camera with a microphone grant. They are separate permissions, and a site that never requests the camera cannot obtain one. TalkLive contains no camera code at all - see random chat without a camera.
It cannot keep the permission after you revoke it.
Checking, in about ten seconds
Look at the tab. An active microphone puts a visible indicator on it in Chrome, Firefox, Safari and Edge. No indicator, no capture.
Look at the address bar. Clicking the padlock or the permission icon lists exactly which permissions the site currently holds.
Look at your operating system. Recent macOS versions show an orange dot in the menu bar whenever any application is using the microphone; Windows shows a microphone icon in the system tray. These are outside the browser's control, which is what makes them worth checking.
If a site claims to be text-only and asks for a microphone anyway, that is a reason to leave rather than a reason to click allow.
Revoking it
Chrome and Edge: click the icon left of the address bar, then toggle Microphone off. Site-wide control is under Settings → Privacy and security → Site settings → Microphone.
Firefox: click the padlock, then remove the microphone permission. Site-wide: Settings → Privacy & Security → Permissions → Microphone.
Safari: Safari → Settings → Websites → Microphone, then set the site to Deny.
iOS and Android: the browser app itself holds a system-level microphone permission, which you can revoke in the operating system's app settings. Doing so blocks microphone access for every site in that browser at once.
Revoking is instant and breaks nothing permanently. Grant it again when you next want a call.
The sensible posture
Granting a microphone to a voice chat site is not unusual or dangerous in itself - it is the same permission a video call at work uses. What matters is that you can see when it is active, that it stops when you close the tab, and that you can take it back in two clicks.
If you would rather not grant it at all, text chat needs no permissions whatsoever. If you do want voice, how anonymous voice chat works explains what happens to the audio after you allow it.