With RCS, you’ve got multiple components to deal with. There’s the clients, but there’s also the servers. RCS is tied to your phone number and IMEI. This means that it’s the telcos who route the messages.
But unlike SMS, where the line level protocol had a back channel designed to transmit these short messages, RCS goes over LTE, which means it needs a network server to send and receive these short messages (more like email).
This means that someone needs to set up and manage the servers for each telco, and route the messages from there to the related numbers.
In the US, the vast majority of ISPs have hired a third party to handle this for them. That third party is Google.
So while the message contents are e2e encrypted, the trunking information and encrypted data can all flow through Google’s servers, even if both recipients are using iMessage, if they’re communicating by RCS instead of iMessage protocol and their telco uses Google for RCS trunking.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
With RCS, you’ve got multiple components to deal with. There’s the clients, but there’s also the servers. RCS is tied to your phone number and IMEI. This means that it’s the telcos who route the messages.
But unlike SMS, where the line level protocol had a back channel designed to transmit these short messages, RCS goes over LTE, which means it needs a network server to send and receive these short messages (more like email).
This means that someone needs to set up and manage the servers for each telco, and route the messages from there to the related numbers.
In the US, the vast majority of ISPs have hired a third party to handle this for them. That third party is Google.
So while the message contents are e2e encrypted, the trunking information and encrypted data can all flow through Google’s servers, even if both recipients are using iMessage, if they’re communicating by RCS instead of iMessage protocol and their telco uses Google for RCS trunking.