E2EE isn’t really relevant, when the “ends” have the functionality, to share data with Meta directly: as “reports”, “customer support”, “assistance” (Meta AI); where a UI element is the separation.

Edit: it turns out cloud backups aren’t E2E encrypted by default… meaning: any backup data, which passes through Meta’s servers, to the cloud providers (like iCloud or Google Account), is unobscured to Meta; unless E2EE is explicitly enabled. And even then, WhatsApp’s privacy policy states: “if you use a data backup service integrated with our Services (like iCloud or Google Account), they will receive information you share with them, such as your WhatsApp messages.” So the encryption happens on the server side, meaning: Apple and Google still have full access to the content. It doesn’t matter if you, personally, refuse to use the “feature”: if the other end does, your interactions will be included in their backups.

Cross-posting my comment from the cross-posted post

"Your honor, end to end encryption is a marketing term that we have trademarked and we would like to counter sue anyone using it"

It'a still end-to-end encryption when they have backdoored both ends.

Correct, WhatsApp fails to include a libre software license text file. We do not control it. So, it has never been secure.

Is that new? I remember reading about this years ago.

yes communication is encrypted end to end which means no one could evedrop but once the information arrive to your app and get saved to your device there is nothing preventing whatsapp from sending to its parent company,

E2E encryption doesnt mean whatsapp is trustworthy

I don’t know if they still do it but they actively gaslight you into believing you have e2e even with peers you have not scanned the public key of.