Yes. If you are talking through a browser, the audio is encrypted and there is nothing to switch on — encryption is part of the protocol rather than a feature somebody chose to add. That is the short answer, and it is also where most articles stop, which is a shame: encryption is not the thing that decides whether a call is private. What the service does with the audio is.
What "encrypted" means on a browser call
Browser voice and video use WebRTC, and WebRTC does not offer an unencrypted mode. Before any sound moves, the two browsers run a handshake (DTLS) that produces keys neither the website nor your network ever sees, and every packet of audio afterwards is encrypted with them (SRTP). Someone sharing the café wifi, your internet provider, or anyone watching the wire in between gets ciphertext and packet sizes.
So "is it encrypted" is nearly always yes, for every site in this category. It is not a differentiator, and a site advertising it as one is telling you about the floor rather than the ceiling.
What encryption does not do
Four things, and all four are where the actual risk lives:
- It does not hide your IP address. Addresses have to be exchanged for a
call to connect at all, and they are not part of what gets encrypted. On a direct peer-to-peer call the other person can read yours out of the connection. See can people see your IP on chat sites for what that gives away.
- It does not stop the other person recording. Encryption protects audio
in transit between two endpoints. At each endpoint the sound comes out of a speaker, and a phone held next to one records it perfectly.
- It does not hide metadata. That you connected, for how long, and from
where is visible to whoever runs the service, encrypted call or not.
- It does not mean the service cannot listen. This is the big one, and it
depends entirely on the shape of the plumbing.
The question that actually matters: where does the audio go?
There are three arrangements, and they differ in who holds keys.
Direct, peer to peer. The two browsers talk to each other. Nobody in the middle can decrypt anything, because there is nobody in the middle — and the price is that each side learns the other's IP address.
Relayed through a TURN server. The packets go out to a relay and back down to the other person. The relay forwards them without keys, so it carries ciphertext it cannot read. You get the privacy of the direct call plus the hidden address, and you pay in bandwidth: all the audio goes through the relay instead of roughly a fifth of it.
Mixed on a server (an SFU or a conference bridge). The server terminates the encryption, handles the audio, and re-encrypts it on the way out. This is how large group calls scale, and it means the operator is technically capable of hearing and storing the call, whatever the policy says.
That is the whole spectrum. "Encrypted" is true of all three. Only the first two make listening impossible rather than merely forbidden.
How to tell which one a site uses
You do not have to take anyone's word for it:
- Look for features that require decoded audio. Recording, transcription,
live translation, audio moderation and "highlights" all mean the server has the sound in the clear. A site cannot offer them and also be unable to listen.
- Check the connection type. In Chrome, open `chrome://webrtc-internals`
during a call and look at the selected candidate pair. `relay` on both sides means a TURN relay; `host` or `srflx` means you are connected straight to the other person, with your address visible to them.
- Read the policy for the word "cannot". A promise not to record is a
policy, and policies change with ownership. An architecture that carries nothing readable does not.
Where this site sits
WaveTalk relays every call, deliberately. The browser is configured so that only relay candidates are used, which means the person you are talking to sees a Cloudflare address and never yours — and the relay sees encrypted packets it has no keys for. Nothing is recorded, in-call text is not stored after the call ends, and the only form of your IP address that is kept at all is a keyed hash, which cannot be turned back into the address.
Private group calls work the same way, with one honest trade: everyone's browser connects to everyone else's, which is why a room holds sixteen people and not six hundred. A server that mixed the audio could hold far more, and would be able to hear it. That is the swap, and how group voice calls work describes the rest of it.
"Encrypted" versus "end-to-end encrypted"
Worth keeping straight, because marketing blurs them. Encrypted in transit means nobody between the endpoints can read it. End-to-end encrypted means nobody but the endpoints can, including the service. A two-person relayed call is end-to-end encrypted in the strict sense. A server-mixed conference is not, no matter how much encryption appears on the diagram.
If this is the kind of thing you want to check before using a site rather than after, what to look for in an anonymous voice chat site is the longer checklist.
Related
- Can People See Your IP Address on Chat Sites? How to Stay Hidden
- What to Look For in an Anonymous Voice Chat Site
- How Does Random Voice Chat Work? A Plain Explanation
- Is Random Voice Chat Safe? What to Know Before You Start
- Do Chat Sites Save Your Conversations?
Questions people ask
Is WebRTC encrypted by default?
Yes, and there is no way to turn it off. Browser calls negotiate keys directly between the two browsers with DTLS and encrypt every audio packet with SRTP, so your network, your internet provider and anyone on the same wifi see only ciphertext.
Can a relay server listen to a relayed call?
No. A TURN relay forwards packets without the keys that were negotiated between the two browsers, so it carries audio it cannot decrypt. A server that mixes audio instead of relaying it — the arrangement large conference calls use — does hold the keys and is technically able to listen.
Is encrypted the same as end-to-end encrypted?
No. Encrypted in transit means nobody between the two ends can read the call. End-to-end encrypted means nobody but the two ends can, including the company running the service. A two-person relayed call is end-to-end encrypted; a server-mixed group call usually is not.
Does encryption stop the other person from recording me?
No. Encryption protects audio while it travels. At each end the sound is played out loud, and anything played out loud can be recorded by the device playing it or by a phone next to it. Treat any voice call the way you would treat a phone call.