End-to-End Encryption, Explained for Family Memories

What is end-to-end encryption? A plain-language guide to how it protects family photos, voices and letters, what stays visible, and how to check a service.

Key takeaways

  • End-to-end encryption locks your files on your own device, and only the people holding the key can open them again.
  • Encryption in transit and at rest is common, but the provider usually holds those keys; end-to-end encryption keeps them with you.
  • End-to-end encryption protects contents, not everything: account details, file sizes and upload times usually stay visible to the service.
  • The trade-off is responsibility: if you lose every key and recovery method, no company can open your files for you.

End-to-end encryption is a way of protecting data so that it is locked on your own device and can only be opened by the people who hold the key. Everything in between, including the company that stores it, handles only scrambled data it cannot read. For family memories, that means a video of your father telling how he met your mother can sit on a server for decades without the server ever being able to watch it.

That is the short answer. The longer one matters too, because "encrypted" appears on almost every storage service, and it does not always mean the same thing. This guide explains what end-to-end encryption is, how it works in plain language, what it protects, what it leaves visible, and the trade-offs worth knowing before you trust it with the family archive.

What is end-to-end encryption, in plain language?

Picture a wooden box with a good lock. You put a stack of letters inside, lock it at your kitchen table, and keep the only key in your house. A courier carries the box to a warehouse, and the warehouse stores it on a shelf. Both handle the box. Neither can open it. When your sister wants to read the letters, you give her a copy of the key yourself, and she opens the box at her own kitchen table.

That is end-to-end encryption. The "ends" are the devices of the people involved: your phone or laptop, and the devices of anyone you choose to share with. The encryption is the lock, a mathematical process that turns readable data into something that looks like random noise until the right key turns it back.

The important detail is where the locking happens. With end-to-end encryption, your photo or recording is scrambled on your device before it is uploaded, and it is only unscrambled on a device that holds the key. The service in the middle stores and moves the box without ever holding a usable key.

How end-to-end encryption works, step by step

You never have to see any of this, but knowing the shape of it helps you judge what a service is really promising. A typical end-to-end encrypted storage service works roughly like this:

  1. Your device creates a random key for each file, a long string of numbers nobody could guess.
  2. The file is encrypted on your device with that key, often using a well-studied cipher such as AES-256-GCM, which also detects tampering.12
  3. Only the scrambled version leaves your device and travels to the service.
  4. The file's key is itself locked, or "wrapped," with a master key that only you can open, usually protected by a password you choose.
  5. When you open the file later, your device unwraps the key and decrypts the file locally.

The password step deserves a moment. People do not choose passwords with the randomness of a computer-generated key, so good services run the password through a deliberately slow, memory-hungry function such as Argon2id before using it.3 That makes each guess expensive for an attacker who has stolen the encrypted data and is trying passwords offline. It does not rescue a weak password, which is why a long passphrase still matters. NIST's current digital identity guidelines treat length as a primary factor in password strength, and they ask for at least 15 characters when a password is the only thing protecting an account.4

Sharing adds one more idea: public-key cryptography. Think of a mailbox with a slot. Anyone can drop a letter through the slot, but only the owner has the key that opens the mailbox. When you share an encrypted album with your brother, your device locks the album's key using his public "slot," and only his private key can retrieve it.5 The service carries the locked key between you without being able to open it.

End-to-end encryption vs encryption in transit and at rest

Most services encrypt your data in some way. The question is who holds the keys. There are three common layers:

  • Encryption in transit protects data while it travels, like the padlock in your browser's address bar. The service decrypts it the moment it arrives.
  • Encryption at rest protects data on the service's disks, so a stolen hard drive is unreadable. The service holds the keys and can decrypt your files when its systems need to.
  • End-to-end encryption keeps the keys with you and the people you share with. The service stores data it cannot read.6

Many popular photo and file services use the first two by default, and that is a reasonable design for everyday use. Holding the keys is what lets a service search your photos for "beach," group faces, build previews on its servers, or restore your files after an email password reset. Some services also offer end-to-end encryption as an option. At the time of writing, for example, Apple's Advanced Data Protection setting extends end-to-end encryption to iCloud Photos for people who turn it on.7

Neither approach is wrong. They answer different questions. Encryption at rest asks you to trust the company and everyone who could gain access to its systems. End-to-end encryption asks you to look after your own keys.

What end-to-end encryption protects, and what it does not

End-to-end encryption protects the contents of what you store: the pixels of a photo, the words in a letter, the sound of a voice in a recording. Done well, it can also cover file and folder names, so the service sees an anonymous object rather than a name that gives the story away.

It does not automatically hide everything. A useful way to think about it is the envelope versus the letter. The postal service cannot read the letter, but it can see the envelope.5 Services usually still see things like:

  • Your account email address and billing details.
  • When you sign in and which devices you use.
  • How many files you store, how large they are, and when you uploaded them.
  • File types, such as whether something is a photo or a video.
  • Who you have set up as a contact or recipient, when the service needs to deliver something to them.

Large services say the same. Apple notes that even with Advanced Data Protection turned on, some metadata, such as when a file was modified and checksums of photo data, stays under its standard protection, where Apple holds the keys.7

End-to-end encryption also cannot protect against problems at the ends themselves. If your laptop is already compromised, or a malicious browser extension reads your screen, the files are visible there, because that is where they are decrypted.6 If someone you share with downloads a photo and forwards it, the encryption has done its job and the copy is now theirs. And if a service offers an AI feature to summarize your stories, that feature needs readable text, so a trustworthy service asks for your consent first and tells you exactly what it sends.

Why end-to-end encryption matters for family memories

Family archives are unusually personal. A single folder might hold a parent's medical letters, adoption papers, a grandmother's voice notes, old tax returns, and a hundred photos of a toddler in the bath. Many of the people in those files never chose to be there, including children who will one day be adults with opinions about their own pictures.

Family archives are also meant to last. A box of letters in an attic might be read fifty years from now. Digital files stored today may sit on servers for decades, through company acquisitions, policy changes and system migrations. End-to-end encryption means that whatever happens to those servers over the years, the copies they hold stay scrambled to anyone without the key.

This is not about fear. It is about choosing your audience. A family archive is written for specific people: your children, your siblings, a grandchild not yet born. End-to-end encryption turns that choice from a policy promise into a technical fact.

The trade-offs worth knowing before you choose

End-to-end encryption moves responsibility toward you. That is the point, and it comes with a few practical consequences.

You are the keyholder. If you lose your password and every recovery method, a truly end-to-end encrypted service cannot open your files for you, because it never had the key.7 On the day you set up an account, save the recovery key it offers, print it, and store it with your important papers. If the service supports passkeys, add one. If you want family members to reach your accounts one day, our guide on how to pass down passwords walks through calm, practical options, and our guide to crypto inheritance does the same for wallets whose keys only you hold.

Fewer server-side conveniences. A service that cannot see your photos cannot search them by content or build previews on its servers. Anything like that has to happen on your device after you open the vault. We cover these trade-offs in more depth in zero-knowledge cloud storage, explained.

Sharing takes a little more care. Recipients need their own keys, or you hand them a key through a separate channel, such as in person or over the phone. A few extra steps buy you confidence that only they can open what you send. Our guide to sharing family photos privately covers how to choose the right method for each circle.

How to tell if a service is truly end-to-end encrypted

Marketing pages can blur these lines. These questions cut through it:

  • Is my file encrypted on my device before it is uploaded?
  • If I reset my password by email, can I still see my files? If yes, the service holds a key.
  • Is there a published technical description that names the algorithms and explains how keys are handled?
  • Does the service say plainly which metadata it can see?
  • Can I export my files and open the export without the service?
  • Has the system been independently reviewed, and if not yet, does the service say so honestly?

A service that answers these clearly, including its limits, usually deserves more trust than one that promises perfection. Honest documentation names what it does not protect.

How Henedo applies end-to-end encryption

Henedo encrypts vault files in your browser before upload, with AES-256-GCM and a random key for every file. Those file keys are wrapped by a random master key, which is protected by a separate vault password run through Argon2id. Your sign-in password is not your vault password, so resetting one does not open the other, and Henedo cannot recover a lost vault password or key.

The limits are stated as plainly as the protections. Account, storage and delivery metadata remains visible to the service, and optional AI composition sends only the written answers you consent to share. When you share files with a partner in a shared vault, or a relative sends you an answer through a link, the key protecting that content is sealed with a hybrid of X25519 and ML-KEM-768 key exchange where the recipient's keys are available. We explain why that matters in post-quantum encryption for long-lived memories. The full design is on the security page, and the boundaries between components are described on the architecture page.

Sources

Each number in the article links to the published work it draws on.

  1. Advanced Encryption Standard (AES) (opens in a new tab)

    National Institute of Standards and Technology · 2023 · Standard

  2. Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC (opens in a new tab)

    Morris Dworkin · National Institute of Standards and Technology · 2007 · Standard

  3. Argon2 Memory-Hard Function for Password Hashing and Proof-of-Work Applications (opens in a new tab)

    Alex Biryukov, Daniel Dinu, Dmitry Khovratovich, Simon Josefsson · Internet Research Task Force (IRTF) · 2021 · Standard

  4. Digital Identity Guidelines: Authentication and Authenticator Management (SP 800-63B-4) (opens in a new tab)

    David Temoshok, James L. Fenton, Yee-Yin Choong, Naomi Lefkovitz, Andrew Regenscheid, Ryan Galluzzo, Justin P. Richer · National Institute of Standards and Technology · 2025 · Standard

  5. A Deep Dive on End-to-End Encryption: How Do Public Key Encryption Systems Work? (opens in a new tab)

    Electronic Frontier Foundation, Surveillance Self-Defense · Guidance

  6. What Should I Know About Encryption? (opens in a new tab)

    Electronic Frontier Foundation, Surveillance Self-Defense · Guidance

Questions

Frequently asked

Keep reading

More stories worth keeping

[ Security ]

Private by design. Readable by the people you choose.

Your files are encrypted in your browser before upload, so Henedo stores them only in encrypted form. The security page explains exactly how, and what it does not promise.