Tutanota vs ProtonMail for vendor communications

Both are end-to-end encrypted email providers marketed on privacy. After using both for different purposes over the past two years, here is an honest comparison relevant to the specific use case of vendor communications.

ProtonMail

ProtonMail is based in Switzerland and subject to Swiss privacy law, which is generally considered favorable for data protection. The free tier provides 1 GB of storage and access to standard email features. The interface is polished and works well on both desktop and mobile.

End-to-end encryption applies automatically between ProtonMail accounts. For communications with vendors who do not use ProtonMail, messages are encrypted in transit using TLS but not end-to-end — ProtonMail can read the content of messages you send to non-ProtonMail recipients. This is the same situation as any other email provider for external communications.

Tutanota

Tutanota is based in Germany and encrypts both message content and metadata (subject lines, sender/recipient in some contexts) for messages within the Tutanota ecosystem. The free tier is functional but more limited than ProtonMail's. The interface is slightly less polished.

Tutanota's approach to external email encryption differs from ProtonMail's — they offer a password-protected link system for sending encrypted emails to non-Tutanota recipients, which requires the recipient to access a web interface rather than receiving a standard email. This is more secure but adds friction for recipients who are not expecting it.

Which to use for vendor communications

For straightforward vendor email communications, ProtonMail's free tier is sufficient. Create an account with a pseudonymous name, do not associate it with any other accounts, and use it exclusively for vendor-related email. The specific encryption provider matters less than having a clean account with no connection to your real identity.

The operational security benefit of separating your vendor email account from your personal account extends beyond just the email address. Using a separate device or browser profile for vendor communications prevents browser fingerprinting from linking your vendor activity to your everyday browsing behavior. The combination of a privacy-focused email provider and an isolated browser session provides better operational separation than either measure alone.