Encrypted Can Mean Three Very Different Things
Almost every app and service says your data is encrypted. They're usually not lying. But "encrypted" on its own tells you surprisingly little, because there are three different situations it can refer to, and they protect you from different people. The question that sorts it out is simple: who has the key?
Let's take a photo you upload to some cloud service and follow it.
In transit is the photo traveling from your phone to the company's servers. This is encrypted with TLS, the same thing behind the padlock in your browser. Anyone sitting between you and the server (someone on the same coffee shop Wi-Fi, your ISP, a network along the way) sees scrambled data. Nearly everything on the internet does this now, and it's genuinely important. But the moment your photo arrives at the server, that layer is done. The server decrypts it so it can work with it.
At rest is the photo sitting on the company's disks. Most services encrypt stored data too. This protects against someone physically stealing a hard drive out of a data center, or a disk being thrown out without being wiped. Good stuff. But the company holds the keys, because their software needs to read your photo to show you thumbnails, run search, scan it, or hand it over if a court asks. So encryption at rest protects your data from outsiders who get the hardware. It doesn't protect it from the company or from anyone who gets into the company's systems with the right access.
Your own devices have at-rest encryption too. FileVault on a Mac, BitLocker or Device Encryption on Windows, and the built-in encryption on modern phones. That's what keeps a stolen laptop from being a stolen life. If yours isn't on, turn it on. In this case you hold the key (it's tied to your password or PIN), which is exactly the point.
End-to-end is the strongest. Your photo gets encrypted on your phone before it leaves, and only gets decrypted on a device that belongs to you or the person you're sharing with. The server in the middle stores and passes along data it can't read. The company doesn't have the key. That's the important bit. Signal and WhatsApp messages work this way, as do services like Proton and some optional modes in big cloud platforms.
End-to-end comes with trade-offs, which is why not everything uses it. The server can't search your stuff for you, so search happens on your device. If you lose your password and recovery key, the company genuinely can't get your data back for you. Some features just don't work.
A couple of things trip people up even with end-to-end encryption.
Metadata often isn't protected the same way. The service may not be able to read your message, but it might still know who you talked to, when, and how often. How much is collected varies a lot by service.
Backups can quietly undo it. If your end-to-end encrypted chats get backed up to a cloud service that isn't end-to-end encrypted, there's now a copy the cloud provider could read. Several apps and platforms offer encrypted backups as an option you have to turn on yourself. Worth checking.
And the endpoints are still the endpoints. End-to-end encryption protects data between devices. If someone has your unlocked phone, or malware on it, they see what you see.
So when a service says "your data is encrypted," ask the follow-up: in transit, at rest, or end-to-end? And who holds the keys? If the answer is "us," that's normal and probably fine for a lot of things. For your most private stuff, I'd want the answer to be "only you."

Comments