With unfortunate, I intended to refer to the way the situation was picked up by the general public: The change to the ToS necessary was only intended to make it

With unfortunate, I intended to refer to the way the situation was picked up by the general public: The change to the ToS necessary was only intended to make it easier for businesses to get started with the WhatsApp Business API, not a sneaky way to read user's messages. The delegation is still in place in terms of encryption: Everything the client sends or receives is encrypted or decrypted using a client-local private key, even if the client is running on AWS servers, rented by WhatsApp. In theory, noone but the business itself has access to the data the client processes, plus it's an optional service: You're still free to host the client yourself. It's just easy to mess up. Take a look at the documentation for a recommended production setup if you'd like to get a peek: https://developers.facebook.com/docs/whatsapp/installation/prod-multiconnect https://developers.facebook.com/docs/whatsapp/installation/p...