End-to-end encryption allows only the sender and the recipient of an RCS message to see it. However, RCS Universal Profile 2.4 features in-transit encryption. The latter secures messages as they travel from the sender to a server, where they are decrypted before being re-crypted and arrive on the recipient’s phone. There are moments during the message’s journey when it is vulnerable to being intercepted and read. With end-to-end encryption, the message is encrypted throughout its journey from the sender to the recipient.
Currently, Google Messages does support end-to-end encryption on Android-to-Android messaging through the app. Apple iPhone users sending an iMessage to another iPhone user also can relax with the knowledge that these messages are also secured with end-to-end encryption.
“End-to-end encryption is a powerful privacy and security technology that iMessage has supported since the beginning, and now we are pleased to have helped lead a cross industry effort to bring end-to-end encryption to the RCS Universal Profile published by the GSMA. We will add support for end-to-end encrypted RCS messages to iOS, iPadOS, macOS, and watchOS in future software updates.”
-Apple
Apple’s testing shows that it has been working on end-to-end encryption (E2EE) in iOS 26, which means that, while it is possible that the feature will arrive next month with the release of stable iOS 26, there is no guarantee that it will be included with this release. However, Apple could leave some of the functionality of RCS Universal Profile 3.0 off the upcoming software updates. For example, we don’t expect to see group icons or mentions included. Still, adding end-to-end encryption to RCS would probably make many iOS and Android users happy.
#Endtoend #encryption #coming #iOSAndroid #RCS #chats #month
