The Digital Envelope
To understand what email encryption doesn't hide, it helps to separate an email into two parts: the 'content' and the 'metadata'. The content is the body of your message and any attachments—this is what end-to-end encryption protocols like PGP and S/MIME
are designed to protect. The metadata is everything else. It’s the information on the outside of the digital envelope, which email servers need to read in order to deliver your message. Just as a postal worker needs to see the 'To' and 'From' addresses on a physical letter, mail servers need this metadata in a readable format to route your email correctly. This is a structural requirement of how email works, not a flaw in encryption itself.
Who Sent It and Who Received It?
The most fundamental pieces of metadata are the sender ('From') and recipient ('To' and 'Cc') addresses. Even with the strongest end-to-end encryption, these fields almost always remain unencrypted. An observer, such as your email provider, the recipient's provider, or anyone with access to mail server logs, can see who is communicating with whom. Over time, this information alone can reveal patterns about your personal and professional relationships, even if the content of your conversations remains secret. For an email to get from point A to point B, the system has to know where A and B are.
The Subject Line: A Telltale Clue
The subject line is one of the most commonly misunderstood parts of an encrypted email. In many common encryption systems, including standard implementations of PGP and S/MIME, the subject line is treated as a header and is not encrypted along with the body of the message. While some modern providers are developing ways to protect subjects, it is not safe to assume it's covered. This is often a conscious trade-off; unencrypted subjects allow email clients to group conversations and enable server-side search functions. The safest practice is to always write neutral subject lines, as if they were a postcard anyone could read. Avoid including names, account numbers, or sensitive details.
Timestamps and Your Digital Footprint
Every email carries timestamps that detail when it was sent and when it was processed by each server along its route. This data remains readable and provides a clear record of your communication timeline. In addition to the time, email headers often log the IP addresses of the servers that handled the message. In some cases, especially with older or misconfigured email clients, the sender's own IP address can be included in a header like 'Received' or 'X-Originating-IP'. This could potentially reveal your general geographic location and internet service provider. While many privacy-conscious providers like Gmail and ProtonMail now strip the user's IP address, it's not a universal practice.
What About Transport Encryption (TLS)?
Most emails today are protected by Transport Layer Security (TLS), which encrypts the connection between email servers. This is crucial for stopping casual eavesdropping on a public Wi-Fi network, for instance. However, TLS is 'hop-to_hop' encryption, not end_to_end. The message is decrypted, read, and then re_encrypted at each server it passes through. This means your email provider, the recipient's provider, and any server in between can access the full unencrypted content and all of its metadata. End_to_end encryption with PGP or S/MIME is what truly protects the content from everyone except the final recipient.
