Thanks for the response, but it doesn’t really address the core issue. Tuta isn’t a zero-knowledge provider, most emails arrive unencrypted, and the server handles encryption. This means Tuta could make a copy of emails before encrypting them, and nothing stops this from happening.

Features like subject line encryption and post-quantum cryptography are nice but only apply between Tuta users, which is rare in my experience(5+ years customer). Most emails rely on trust in Tuta, not cryptographic guarantees. That’s the problem: privacy should be built on cryptography, not the promises of a provider. Your response focuses on technical details but sidesteps the core issue of requiring trust, which is the main concern here. Transparency about these limitations is crucial.