End-to-end encryption, explained plainly

“Bank-grade encryption.” “Military-grade security.” “Your data is encrypted.” Nearly every app that holds something private says one of these, and they are meant to end the conversation. They don’t. They answer a question you weren’t asking and skip the one that decides whether your data is actually private.

Here is the real question, without the math. It comes down to three ideas that build on each other: what encryption is, where it happens, and why the where is the whole game.

What encryption actually is

Encryption is a lockbox. You scramble readable data with a key into what looks like random noise, and only the same key turns it back. Without the key, the scrambled text is useless.

The method almost everyone uses is AES-256. For practical purposes it is unbreakable: there is no known way past it, and there won’t be for a very long time. That is the twist, because it means the lock is not the weak point. Your bank, your messaging app, and a password manager all use the same effectively unbreakable lock.

So if everyone uses the same lock, only one thing is left to differ: who holds the key.

Where the encryption happens

This is where “bank-grade” and “military-grade” fall apart. They describe the lock, not who holds the key. “Military-grade” almost always just means AES-256, the same cipher everyone uses, including you when you load a normal website. It is true, and it tells you nothing.

The question that matters is where the encryption happens. There are three answers.

01In transit

Your data is scrambled while it travels to the company’s server, so nobody can read it in flight. This is the padlock in your browser bar. Good, and almost everything has it. But it protects the journey, not the destination.

02At rest

Your data is scrambled on the company’s disks, so a stolen drive is unreadable. Also good, also common. But in both of these the company holds the key. It has to, because it decrypts your data every time it shows it to you or processes it. So the company can read your data, and so can its employees, a hacker who breaks in, or a court order.

This is even true of your bank, and for a bank it is right: it has to read your transactions to process them. The model isn’t wrong. It just isn’t private from the company.

03End-to-end

The third model is rarer. The key is created on your own device and never leaves it. The server only ever receives already-scrambled data, and never holds the key to open it. It stores locked boxes it genuinely cannot open. Your devices are the only “ends” that can read the contents, which is where the name comes from.

Why “where” is the whole question

Three things eventually happen to almost every company that holds data: a breach, a subpoena, or a dishonest employee.

Against a service that encrypts only in transit and at rest, all three end the same way, because the company holds the key. The attacker, the court, or the insider gets your readable data. The strong lock didn’t matter; the key was sitting right next to it.

Against an end-to-end encrypted service, they get noise. There is no key on the server to take. A breach exposes scrambled boxes. A subpoena can only compel data the company cannot read. The insider has nothing to sell.

For most everyday apps this is academic. For a will, a list of accounts, passwords, and the documents your family would need if you couldn’t tell them yourself, it is the whole decision.

How this works in MyLifePapers

MyLifePapers is built on the third model. Here is how the key is handled, in plain terms.

When you set up your vault, the key that protects your records is generated on your device, at random, and never sent anywhere. Your passphrase doesn’t travel either. It runs through a deliberately slow process (a method called Argon2id) to derive a second key that wraps the first, so only your passphrase can unlock it, on your device.

Your records sit in a database fully encrypted with AES-256, the same lock from the start of this guide. The difference that counts is that the key lives with you.

If you sync to the cloud, what leaves your device is already scrambled. What we hold is locked boxes and wrapped keys we cannot open, for anyone who asks or anyone who breaks in.

That comes with an honest catch, which is the truest test of real end-to-end encryption. Because we never hold your key, we cannot reset your passphrase. You get a recovery code to keep instead. Lose both your passphrase and that code, and your data is gone for good, and no one, including us, can bring it back. A company that could rescue you there could also be made to hand your data over.

The short version

Everyone uses the same strong lock, so the lock is not the question. The question is who holds the key. In transit and at rest, the company holds it, so the company, and any breach, subpoena, or insider, can read your data. End-to-end puts the key on your device alone, so the company holds only boxes it cannot open. “Bank-grade” and “military-grade” aren’t lies; they just describe the lock and stay quiet about the key. For your most sensitive records, the key is the only part worth asking about.