Originally Posted by
plunet
That's the exact point. I have no relationship with Meta but they surely know my number and name from others who have shared it via their WhatsApp or other contacts sharing.
So Meta could now join the dots and assume that my phone number and name is a customer of BA, and I am probably about to or am travelling. They might even be able to see the content of the message BA have tried to send to me but can't be encrypted because end to end encryption can't be established. I have no desire for Meta to know this, and BA have no need to use an invasive data mining social network provider to send customer confidential messages.
That.
WhatsApp is a rich source of metadata and it's the reason I've never used it. Meta may boast about its 'end to end encryption' but there's so much more to a message than that. Perhaps the name of the company 'Meta' is the clue here.
My previous post was, of course, in jest but I have been told by another FTer that WhatsApp is indeed used by staff at their organization to get round firewall restrictions meaning that the risk in a corporate environment is greater than many realize. Even though WhatsApp is fully encrypted it's still possible to block it explicitly with a decent firewall.
They aren't sharing any personal data though, a booking reference isn't personal data and a phone number isn't personal data and that is all that is in their messages
Methinks you're a tad out of date. An IP address can often be personal data, a vehicle registration number too.
If I ever became aware that BA had tried to contact
me by WhatsApp I'd certainly be making a complaint to the ICO.