Is leaving WiFi Calling and RCS enabled a privacy concern for even basic threat models?

It seems to me that these two options are enabling VZW/Google to continuously log your IP and probably device identifiers, even while on a VPN. So wouldn’t this just be one future data-sharing deal away to correlating your VPN exit IP with basically all your browsing activity?

I realize we share IP’s, but we’re split up between so many VPN nodes. And it seems like within the time of a browsing session, there can’t be that many users with the same specific device type on that specific IP. Am I understanding the potential of this correctly?

1 Like

Yes, assuming you are referring to either legal data disclosure or other third-party malicious attacks, including data breaches/exfilitration.

Generally yes, although it depends on how many VPN endpoints are available for usage at any given time.

Well, shit, I would put these two features in the same category then as IMAP or push notifications on closed apps. Ways to persistently track a “logged in” user’s VPN exit points.

I don’t see any threads of people talking about these, but I really don’t think it’s that far fetched for Carriers/Google to be selling users’ IP’s, and then combining that with data from the sites you visit (if they don’t already have Goog/FB tracking anyways). Granted, this still hinges on there being minimal ppl connected to your specific VPN exit during that browsing session, but it does feel like it goes against the whole strategy of “ephemeral” browsing that won’t just get correlated back to you at some point in the future.

Anyone know of any other “background” things like this to disable? You kinda give a pass to your device manufacturer (Apple) cause there are so many phone-homes going on, but I didn’t realize how prevalent all these Google pings are when nothing is even opened on your phone.

1 Like

Sure, here is an abstract:

See also:

1 Like