Google cannot implement what you’re proposing (nor can any email provider). Whatever mail service you choose must be able to send and receive email on your beha

Google cannot implement what you’re proposing (nor can any email provider). Whatever mail service you choose must be able to send and receive email on your behalf and to do this, they must have access to the email in unencrypted form [1]. Yes, they could encrypt at rest. And yes, they could even encrypt with your public key at rest. This doesn’t eliminate the need to completely trust them [2] but it does completely break critical features like search and a usable mail archive. [1] Yes, if you use gpg and the party you’re communicating does as well, then you don’t need to trust the email service. Good luck with that. [2] If you can’t trust them to not look at your email then you can’t trust that they’ll actually encrypt without keeping a copy (or that they’ll actually encrypt at all). Encryption at rest is a great feature, but not for eliminating the need to trust the organization running the email service.