Glossary

End-to-end encryption

E2EE

Definition

Encryption designed so that only the communicating endpoints can read the message contents, including while an intermediary carries them.

It keeps message contents encrypted between the sender and intended receiving endpoints. It does not prevent a recipient or compromised endpoint from revealing the content.

A customer may include “End-to-end encryption” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

End-to-end encryption is designed to keep message contents readable only at the communicating endpoints. The service carrying the messages should not hold the means to decrypt those contents in ordinary operation. This differs from a connection encrypted only between a customer and a service that can then read the information.

For example, two partners in a small firm could use an end-to-end encrypted messenger to discuss a confidential negotiation. The messaging provider carries protected content. Either partner can still copy the conversation, and malware on an unlocked phone may see what that partner can see.

“End-to-end” needs a clear boundary. Map group membership, linked devices, search features and message backups to understand who can decrypt the information. Metadata, such as who communicates and when, may receive different protection from the message itself.

There can also be operational trade-offs. Recovery, archiving, content inspection and employee departure need deliberate handling if the provider cannot restore access itself. Choose a service whose documented behaviour fits the business requirement. Do not assume that an encrypted upload, an encrypted database and end-to-end encryption describe the same arrangement.

Sources

Signal: how end-to-end encryption protects conversations

ICO: encryption and data transfer