Proton Mail Encryption: What It Protects and What It Doesn’t

Proton Mail encrypts messages so Proton generally cannot read the contents of end-to-end encrypted mail, and it protects stored mailbox data against access by someone who lacks the necessary keys. It does not encrypt every email in every situation: messages to ordinary email services, subject lines, account activity, and data on an unlocked or compromised device have important limits.

How Proton Mail encryption works

Encryption scrambles readable information into ciphertext; a key is needed to turn it back into readable text. Proton Mail uses more than one form of encryption, and the protection depends on where a message is going and how the recipient accesses it.

• End-to-end encryption (E2EE): When both people use Proton Mail, messages can be encrypted so that they are readable on the users’ devices, not by Proton while stored or delivered. Proton’s services help deliver the message, but the design is intended to keep the message content inaccessible to the provider.
• Password-protected email: A Proton user can send an encrypted message to someone outside Proton and protect it with a password. The recipient uses a link and the password to view the message in a browser. The sender should share the password through a separate channel, not in the same email.
• TLS in transit: Email connections commonly use Transport Layer Security (TLS) when available. TLS protects data between mail systems during a connection, but it is not end-to-end encryption: the receiving provider may be able to read the message.

Proton also encrypts mailbox data at rest. That is useful if storage systems or infrastructure are accessed without authorization, but it is not a substitute for a strong account password, device security, or E2EE. Encryption at rest and end-to-end encryption address different points in the journey.

What encryption protects

For an end-to-end encrypted message, the main protection is its content: the body and, where supported by the message format, attachments. A network observer who intercepts encrypted traffic should not be able to read that content merely by capturing the connection. A storage intruder who gets encrypted mailbox data should likewise not automatically gain readable copies of E2EE message contents.

Encryption can also limit exposure to the email provider itself. With E2EE, Proton’s stated architecture is designed so it does not possess the private decryption key needed to read the protected content. That is a meaningful difference from services that store messages in a form their provider can decrypt, though it does not prevent access through a user’s own account or device.

For a message sent to a non-Proton address using password protection, the contents are protected from ordinary email delivery and from the recipient’s email provider until the recipient opens the secure message. The recipient still needs the password, and can copy, screenshot, forward, or otherwise disclose what they can read.

What encryption does not protect

Encryption does not hide all information about an email. Standard email routing and service operation require some information to be available, and a recipient must be able to identify and respond to a message. In particular, subject lines and sender/recipient information are not generally protected by Proton’s E2EE in the same way as the message body. Proton may also process certain metadata needed to provide the service. The precise data retained or exposed can depend on the feature and circumstances.

• Messages to regular email accounts: Unless you use a protected-message option such as password-protected email, a message to a non-Proton recipient is not end-to-end encrypted. TLS may protect it in transit, but the recipient’s provider may store or process readable content.
• Compromised endpoints: Malware, a malicious browser extension, keylogging, or someone using an unlocked phone can capture text before it is encrypted or after it is decrypted.
• Recipients’ actions: Encryption cannot stop an intended recipient from copying content, taking a screenshot, or sharing it with someone else.
• Account access: A stolen password, an active session, or a phishing attack can let an attacker access messages as the account holder. Encryption does not make weak login security harmless.
• Backups and copies elsewhere: A message may also exist in a recipient’s inbox, forwarded email, notification preview, downloaded file, or backup, each with its own protections.

These limitations are not unique to Proton. End-to-end encryption protects data against particular kinds of access; it does not guarantee secrecy against every person, device, provider, or legal process.

Choosing the right way to send a message

Before sending sensitive information, check the recipient’s service and select a method that matches the risk. If both parties use Proton Mail, use the normal encrypted workflow and verify the recipient address. If the recipient uses another email provider, consider Proton’s password-protected message option where available. Use a long, unique password and communicate it through a different channel, such as a phone call or a separate messaging app.

For highly sensitive information, consider whether email is appropriate at all. A secure file-sharing system with access controls or an in-person exchange may reduce exposure. Avoid putting confidential details in the subject line, since subject lines are not protected like encrypted message content. Also review the recipient list carefully: encryption cannot undo a message sent to the wrong address.

Security practices that complement encryption

Encryption works best as one layer of protection. Use a unique, strong Proton account password and enable two-factor authentication. Keep the operating system, browser, and Proton apps updated, and use a screen lock. Be cautious with links and attachments, especially messages that ask you to sign in or reveal recovery information.

For password-protected messages, never send the password in the same email as the secure link. Choose a password the recipient can enter reliably, but do not reuse a password that protects another account. If a message contains information that should not persist, remember that a recipient can still make a copy; a disappearing-message setting is not a guarantee against capture.

Frequently Asked Questions

Can Proton Mail read my emails?
For end-to-end encrypted messages, Proton’s design is intended to prevent the service from reading message contents because it does not hold the needed decryption key. This does not apply to every message type: mail sent to ordinary providers without password protection may be readable by the recipient’s provider.

Are Proton Mail subject lines encrypted?
Subject lines are not protected in the same way as E2EE message bodies. Avoid placing sensitive details in a subject line; use the message body for confidential content and choose an appropriate encrypted sending method.

Are emails to Gmail or Outlook end-to-end encrypted?
Not by default. TLS may protect a message during transfer, but it does not prevent the recipient’s provider from accessing it. A Proton sender can use password-protected email for an external recipient, subject to the feature’s availability and setup.

Does Proton Mail encryption protect me if my phone is stolen?
Encryption does not protect messages already displayed in an unlocked or compromised device. Use a strong device passcode, automatic locking, and account security measures. If the account or device may be exposed, secure the account from a trusted device and review active sessions and recovery options.

Can the recipient save a password-protected email?
Yes. Once a recipient can read a message, they can copy its text, take screenshots, or share it. Password protection helps secure delivery and access; it cannot control what a recipient does with readable content.

The practical takeaway

Proton Mail’s strongest confidentiality applies when a message is end-to-end encrypted, the account and devices are secure, and the recipient is trustworthy. For external recipients, password-protected email can add meaningful protection, while ordinary email generally relies on transport encryption rather than end-to-end secrecy. Treat metadata, endpoints, account access, and recipient behavior as separate parts of the security picture.

Related

• Compress Images in React Before Uploading
• Is Chromecast Still Worth Buying? What to Know
• Action Thriller Movies on Hulu This Weekend