Secbird encrypts your email so that only you and the people you write to can read it. You do not have to do anything special to make this happen; it is built into every account. This article gives a practical overview of how it works, what is protected, and how to tell whether a particular message was end-to-end encrypted. For a deeper background, read our blog article end-to-end encryption explained.
Your keys
Every Secbird account has a set of encryption keys, created on your device when you signed up:
- A public key, which others use to encrypt messages to you. It is shared with Secbird and published so other Secbird users can find it.
- A private key, which decrypts messages sent to you. It is encrypted with a key derived from your password before it is stored on our servers, and is only ever unlocked on your devices.
Secbird keys combine a classical algorithm (X25519) with a post-quantum algorithm (ML-KEM), so messages are protected against today's computers and future quantum computers.
Sending a message to another Secbird user
When you write to another Secbird user, encryption happens automatically:
- Your app looks up the recipient's public key and verifies it using key transparency.
- It generates a random key for this message and encrypts the subject, body and attachments with it.
- It encrypts that message key with the recipient's public key, and with your own public key so the message is readable in your Sent folder.
- It signs the message with your private key so the recipient knows it came from you and was not altered.
- It sends the encrypted message to Secbird.
The recipient's app decrypts the message key with their private key, decrypts the content and checks your signature.
Sending a message to someone outside Secbird
For recipients on other providers you have three options:
- They use OpenPGP. If you have their public key, Secbird encrypts the message end-to-end just like a message to another Secbird user.
- Password-protected message. You set a password, and the recipient opens the message in their browser. See sending encrypted email to anyone.
- Regular email. The message is sent like normal email, protected in transit by the connection between providers. Your copy in Sent is still stored under zero-access encryption.
Receiving mail from outside Secbird
Mail from other providers often arrives unencrypted. Secbird encrypts it with your public key the moment it arrives, before storing it. This is called zero-access encryption, and it means your whole mailbox is stored in a form only you can read.
How to tell if a message is end-to-end encrypted
Secbird shows a lock icon next to each message:
| Icon | Meaning |
|---|---|
| Green lock | End-to-end encrypted between you and the other party |
| Green lock with a check | End-to-end encrypted and the sender's key has been verified |
| Grey lock | Stored with zero-access encryption; arrived unencrypted from outside |
| Lock with a warning | Signature could not be verified; read the warning before trusting the message |
Select the icon for details about how the message was protected.
What is protected
- Message bodies and attachments.
- Subject lines.
- Your contacts and calendar data, which are encrypted before storage.
- Your search index, which is built and encrypted on your device.
What is not hidden
Some information is needed to deliver email and cannot be encrypted between providers:
- Sender and recipient addresses.
- The time a message was sent and received.
- The approximate size of a message.
Secbird keeps this information to a minimum, does not log your IP address, and removes your device's IP address from outgoing message headers. Read more in our article on email metadata.
Your password protects your keys
Because your private key is protected by your password, we cannot reset your password and restore access to old messages. Store your password safely and read recovering account access to prepare for the unexpected.
Verifying who you are writing to
To prevent someone from substituting a fake public key, Secbird uses key transparency. For high-stakes conversations you can also verify a contact's key fingerprint manually. See verifying recipient keys.