Random chat explained
Are Video Calls Encrypted? What It Protects and What It Doesn't
Are video calls encrypted? Almost always, at least on the way between devices. Browser calls built on WebRTC, the technology behind most web video chat, are encrypted by default, and the standard doesn't allow switching that off. What varies is who else could hold the keys, and that's where "end-to-end" comes in.
Encryption also has a clear edge: it protects your call while it travels, not what happens on either screen. Here's what it covers, how relays fit in, and the risks it was never designed to stop.
Video call encryption explained
Encryption scrambles your audio and video into data that only devices holding the right key can turn back into sound and pictures. Anyone in between, such as the Wi-Fi owner, your internet provider or a router along the way, sees scrambled data. They can usually still see some metadata: that two addresses are exchanging data, when, and roughly how much.
| Term | What it means |
|---|---|
| Encryption in transit | Data is scrambled while it travels. It may be unscrambled at a server along the way. |
| End-to-end encryption | Only the people in the call hold the keys. Servers in the middle can't read the content. |
| Encryption at rest | Stored data, such as recordings or messages, is scrambled on disk. |
| Metadata | Who connected to whom, when and for how long. Call encryption usually doesn't hide it. |
Is WebRTC encrypted?
Yes. WebRTC requires encryption for everything it sends. Audio and video travel using a protocol called SRTP, with keys the two browsers agree on through a DTLS handshake, and data sent over WebRTC data channels is encrypted with DTLS. A browser won't make an unencrypted WebRTC call. If the acronyms are new, start with what WebRTC is.
The fine print on end-to-end
On a direct call, the two browsers create the keys themselves, so the stream is encrypted from one device to the other. The catch is that the browsers find each other through the site's signaling server, which passes along each side's key fingerprint. You're trusting the site not to interfere with that exchange. That's why apps that market end-to-end encryption often add a way to compare safety codes.
End-to-end encrypted video chat vs relayed and group calls
A one-to-one call usually tries to connect the two devices directly. When that isn't possible, for example on strict firewalls, some mobile networks or certain VPNs, the call goes through a relay called a TURN server. A standard relay forwards encrypted packets without receiving the keys, so it passes along data it can't read. More on relays in what a TURN server is.
Group calls are different. They often run through a media server that decrypts and re-encrypts each stream on its way to everyone else, unless the service adds its own extra end-to-end layer.
| Call type | Encrypted? | Can the server in the middle read it? |
|---|---|---|
| Direct peer-to-peer, one-to-one | Yes | There's no server in the media path |
| Relayed through a TURN server | Yes | No; a standard relay passes along encrypted data |
| Group call through a media server | Yes, in transit | Often yes, unless extra end-to-end encryption is added |
How Omlet's calls work
Omlet is one-to-one only. Calls are encrypted and peer-to-peer between the two people. When a direct connection isn't possible, the call is relayed through Omlet's network provider and stays encrypted.
- No recording. Omlet doesn't record or store calls.
- Messages are kept only for safety. They're stored only when part of a report or a safety review.
- Safety checks run on your device. The nudity check on your partner's video runs locally, and text is checked on your device first. A message flagged in a serious category gets a second review by an AI service, so encryption protects the trip while the endpoints can still check content.
The trade-off of a direct connection: it can share your IP address with the person you're talking to. An IP points to a rough area and provider, not your home. A reputable VPN hides it; see whether people can see your IP address on video chat.
What encryption can't stop
Encryption guards the pipe. Everything at either end is outside its reach:
- Screen recording. The other person can record their screen or film it with a second phone. Here's whether random video chats are recorded and how to act accordingly.
- What's on camera. Mail, ID cards, a window view or a work badge are all visible to the person you're talking to.
- What you say. Scams and pressure tactics work just as well over an encrypted line.
- Your IP address on a direct connection, as above.
- Malware on your own device. If your device is compromised, encryption in transit can't help.
- Site rules. Encryption doesn't stop reports, on-device checks or bans. If that's on your mind, read why people get banned from video chat.
Public Wi-Fi, VPNs and encrypted calls
On public Wi-Fi, encryption keeps others on the network from seeing or hearing your call. They may still see that you're connected to a video service, and some networks block video calls entirely. The full picture is in is it safe to video chat on public Wi-Fi.
A VPN wraps your traffic in another encrypted tunnel to the VPN's server. It doesn't make the call itself more encrypted, but it hides your real IP address from the other person and hides which services you're using from the local network. Distant VPN servers can add lag.
How to check whether a video app is encrypted
- Search its privacy policy or security page for "encrypted", "end-to-end" and "record".
- Check whether calls are peer-to-peer or routed through the company's servers.
- For group calls, look for the words "end-to-end" specifically, not just "encrypted".
- Look for what's stored and for how long: messages, recordings, snapshots.
- Make sure the site loads over HTTPS. Browsers require it before they'll share your camera.
Encryption is one part of privacy. What a site asks you for is another: some want ID, others only ask you to confirm you're an adult, as explained in why chat sites ask if you're 18.