"Unless you think America is the only place you'll conduct business that needs secure communication", and you trust the US government in the general, and you tr

"Unless you think America is the only place you'll conduct business that needs secure communication", and you trust the US government in the general, and you trust each individual government agent or employee with that kind of access not be corrupt, and you trust each such agent or employee to be super-competent as to not be hacked by an hostile third party, and you trust the cloud company in the general, and you trust each employee of that company with access to not be corrupt and to be super-competent... and so on and so forth. The fact that we currently mostly use systems where we need to trust a large number of people with our data only to communicate with one another doesn't mean that those systems are the right ones to build, even at a relatively apolitical technical level. The early internet, before HTTPS was common, added a large number of interconnected ISPs to that list of 'fully trusted by design' parties. That was, as we have recognized for decades, a design bug. One which we are only now starting to fix adequately. Trusting the cloud providers with full access to all data stored or even processed by them is a similar design mistake. (Not saying that there isn't ever a use case to send data to a company so that they offer a service by processing it, but simply storing and transmitting private messages between two users shouldn't count as giving that data to the cloud provider anymore than it counts as giving that data to the ISP)