Encryption

End-to-end encryption explained

What end-to-end encryption really means for email, how public-key cryptography works, and what it can and cannot protect.

Few phrases in technology are used as loosely as "end-to-end encryption". It appears on messaging apps, cloud drives, video calls and email services, and it is often stretched to describe things it was never meant to describe. This guide explains what end-to-end encryption actually is, how it works under the hood, why it matters so much for email in particular, and where its limits lie. By the end you should be able to read any provider's security claims and tell whether they describe real end-to-end protection or something weaker.

What "end-to-end" actually means

Every email travels through a chain of computers. It starts on your device, passes to your provider's servers, crosses the internet to the recipient's provider, and finally lands on the recipient's device. Each of those hops is a place where the message could, in principle, be read, copied or altered.

Most email services protect the individual links in that chain. The connection between your phone and your provider is encrypted, and the connection between two providers is often encrypted too. That is useful, but it is only encryption in transit. Every time the message arrives at a server, it is decrypted and stored in a form that the server operator can read.

End-to-end encryption changes where the locks and keys live. The message is encrypted on the sender's device before it leaves, and it can only be decrypted on the recipient's device. Everything in between, including both email providers, only ever handles scrambled data. The "ends" in end-to-end are the two people communicating, not the servers that carry their messages.

A simple way to picture it

Imagine posting a letter. Encryption in transit is like sending the letter in an armoured van between post offices, but letting the clerks open and read it each time the van stops. End-to-end encryption is like locking the letter in a box that only the recipient has a key for. The vans, clerks and sorting offices still do their jobs, but none of them can see inside the box.

The building blocks: public-key cryptography

End-to-end encryption for email is built on public-key cryptography, also called asymmetric cryptography. Instead of one secret password shared by both people, every user has a pair of mathematically linked keys.

  • The public key can be shared with anyone. Other people use it to encrypt messages to you.
  • The private key stays with you and never leaves your control. It is the only key that can decrypt messages encrypted with your public key.

The relationship between the two keys is one-way. Knowing someone's public key does not let you work out their private key, even with enormous computing power. That property is what makes it safe to publish public keys openly.

How a message is actually encrypted

Public-key algorithms are slow compared with ordinary symmetric ciphers, so real systems combine the two. When you send an end-to-end encrypted email, your device typically:

  1. Generates a fresh, random session key for this one message.
  2. Encrypts the message body and attachments with that session key using a fast symmetric cipher such as AES.
  3. Encrypts the session key itself with the recipient's public key.
  4. Sends the encrypted message together with the encrypted session key.

When the recipient opens the email, their device uses their private key to recover the session key, and then uses the session key to decrypt the message. Nobody without the private key can complete the first step, so nobody else can read the message.

Signatures: proving who sent it

The same key pairs can also be used the other way around to create digital signatures. The sender's device signs the message with the sender's private key, and anyone can verify that signature with the sender's public key. A valid signature tells the recipient two things: the message really came from the holder of that private key, and it has not been altered since it was signed.

OpenPGP: an open standard for encrypted email

Secbird uses OpenPGP, an open standard for email encryption that has been publicly specified, implemented and scrutinised for decades. Using an open standard has several practical benefits:

  • Its design and weaknesses are well understood by the security community, rather than hidden behind proprietary claims.
  • Independent implementations exist, so your encrypted messages are not locked into a single company's software.
  • You can exchange encrypted email with people who use other OpenPGP-compatible tools, not only with other Secbird users.

Secbird handles the complexity for you. Keys are generated automatically when you create your account, public keys of other Secbird users are looked up and verified in the background, and messages between Secbird users are encrypted end-to-end without any extra steps.

Where your keys live matters

An end-to-end system is only as strong as the protection around the private key. If a provider generates your private key on its servers, or stores it in a form it can read, then the provider can decrypt your mail whenever it likes. Calling that end-to-end encryption would be misleading.

At Secbird, your key pair is generated on your device during sign-up. Before your private key is backed up to our servers, it is encrypted with a key derived from your password. Because your password itself is never sent to us (we use the SRP protocol for sign-in), we never have what we would need to unlock that backup. Your devices download the encrypted private key and unlock it locally when you sign in.

If a service can reset your password and give you back access to all of your old messages, it holds a copy of the keys that protect them. True end-to-end encryption means the provider cannot do this.

What end-to-end encryption protects against

When it is implemented properly, end-to-end encryption protects the content of your messages against a wide range of threats:

  • Server breaches. If attackers break into your provider's systems, they find encrypted data they cannot read.
  • Insider access. Employees and contractors of the provider cannot browse your mailbox.
  • Bulk data requests. A provider cannot hand over readable message content it does not possess.
  • Network interception. Anyone watching the traffic between devices and servers only sees ciphertext.
  • Tampering. Signed messages reveal any alteration made after they were sent.

What it does not protect against

End-to-end encryption is powerful, but it is not magic. Being honest about its limits is part of using it well.

Compromised devices

If malware is running on your phone or computer, it can read messages after they are decrypted on screen. End-to-end encryption protects data on the way and at rest on servers; it cannot protect a device that is already under someone else's control. Keep your operating system updated and be careful about what you install.

The recipient

Once a message is decrypted on the recipient's device, the recipient can forward it, screenshot it or print it. Encryption protects a message from outsiders, not from the person you chose to send it to. For especially sensitive messages, Secbird lets you set an expiry time so that the message self-destructs, but no technology can stop someone from taking a photo of their screen.

Metadata

Email has to carry certain information in order to be delivered, such as the recipient's address. Encryption of the body does not automatically hide who you are writing to or when. Secbird encrypts subject lines and keeps metadata to the minimum needed for delivery, and we explain this topic in detail in our article on email metadata.

Messages to people outside the system

When you send ordinary email to someone whose provider does not support OpenPGP, the message has to leave in a form their provider can deliver. Secbird offers two ways to keep such messages private: encrypting with the recipient's public key if they have one, or sending a password-protected message that they open in their browser. You can read more in the help article on sending encrypted email to anyone.

End-to-end encryption versus "encrypted at rest"

Many services advertise that your data is "encrypted at rest". This usually means the disks in their data centres are encrypted. It protects against someone stealing a hard drive, but the provider holds the keys and decrypts the data whenever its software needs to process it. That is a long way from end-to-end encryption.

ProtectionWho can read your messagesTypical use
Encryption in transitThe provider, on its serversStandard email connections
Encryption at restThe provider, whenever it needs toDisk encryption in data centres
End-to-end encryptionOnly the sender and recipientSecbird messages between users
Zero-access encryptionOnly the mailbox ownerSecbird storage of incoming mail

When you evaluate a service, ask a simple question: if the company wanted to, or were forced to, could it read my messages? If the honest answer is yes, the service is not end-to-end encrypted.

How Secbird puts it together

End-to-end encryption is one of thirteen layers in Secbird's design. It works alongside:

  • Zero-access encryption for mail that arrives from other providers, so even messages that were never end-to-end encrypted are stored in a form only you can read. Our article on zero-access encryption explains how this works.
  • Hybrid post-quantum encryption, combining X25519 with ML-KEM to protect against future quantum computers. See post-quantum encryption for email.
  • Key transparency, which lets your apps verify that the public key they use for a contact really belongs to them. The help article on verifying recipient keys covers this.
  • SRP sign-in and two-factor authentication, so that your password never travels to our servers and a stolen password alone is not enough to get into your account.

You can explore every layer on our Security page.

Practical tips for getting the most out of it

  • Use a strong, unique password. It protects your private key, and we cannot reset it for you.
  • Turn on two-factor authentication with an authenticator app or, better still, a passkey or hardware security key.
  • Keep your devices and the Secbird apps up to date.
  • When writing to someone outside Secbird about something sensitive, use a password-protected message and share the password through a different channel.
  • Pay attention to key verification warnings. They exist to catch impostors.

The bottom line

End-to-end encryption means that only the people in a conversation can read it. For email, that requires public-key cryptography, private keys that never leave the user's control, and a provider that is honest about what it can and cannot see. Secbird is built so that the answer to "can the provider read my mail?" is simply no, by design rather than by policy.

Further reading

Ready for a private inbox?

Create your Secbird account in minutes. No phone number, no tracking, and encryption on every plan.