Encryption in transit
What is encryption in transit?
Encryption in transit protects data while it travels across a network, so that anyone who intercepts it between a device and the server that receives it sees only unreadable bytes. It is the padlock of a web page and the standard protection of a video call. It protects the trip, not the destination: the server that receives the data can read it.
How does encryption in transit work?
Before any real data moves, the two ends run a short handshake. The server proves its identity with a certificate, and both sides agree on fresh keys that exist only for that connection. From then on, everything sent between them is encrypted and checked for tampering.
A video call uses two kinds of this protection. Web pages, sign-in and the call's control messages travel over TLS, the same protocol behind the padlock in the address bar. The live audio and video travel over DTLS-SRTP: DTLS performs the handshake over the fast, loss-tolerant connection that real-time media uses, and SRTP encrypts each audio and video packet. WebRTC requires DTLS-SRTP, so a browser call cannot be sent unencrypted.
Where does encryption in transit stop protecting a call?
It protects against people on the network path: a shared café Wi-Fi, an internet provider, any router in between. It does not decide what happens at the destination. When a call runs through a media server, an SFU, each connection is encrypted up to that server, and the server handles the media before passing it on. Only end-to-end encryption keeps the content unreadable to the server too.
| Situation | Covered? |
|---|---|
| Someone on the same Wi-Fi tries to listen | Yes: they see only encrypted packets. |
| A relay forwards the call through a strict network | Yes: the media stays encrypted inside the relay connection. |
| The service's own servers handle the call | No: the server receives readable media. |
| A recording stored after the call | No: that is data at rest, protected by storage and access controls. |
How does Meeto use encryption in transit?
Meeto uses WebRTC (DTLS-SRTP) encryption in transit for every call's audio, video and screen sharing, between each device and Meeto's media servers. The website and the call's control connection are protected with TLS (HTTPS and secure WebSockets). When a network blocks the usual routes, a TURN relay over TLS on port 443 carries the call, and the media inside stays encrypted.
Meeto is not end-to-end encrypted. Recording and AI summaries are opt-in features for Pro and Team hosts, shown to everyone with an indicator, and meeting content is not used to train AI models. The security overview describes these controls, and the privacy policy covers retention.
Frequently asked questions
Does encryption in transit protect a saved recording?
No. A saved recording is data at rest, and it is protected by how the service stores it and who can open it. In Meeto, recorded media is kept for 90 days by default, and the owner decides whether its share link works.
Can my Wi-Fi provider or employer see my call?
They can usually see that your device connects to a meeting service and how much data flows. They cannot see or hear the audio and video inside the encrypted stream.
Is DTLS-SRTP secure?
DTLS-SRTP is the encryption that WebRTC requires for every call, and browsers will not send media without it. It reliably protects each connection; the question that remains is who operates the server at the other end of that connection.
Put it to work
Open your Meeto account to set it up, or explore the working product first.