Back in November, Google announced that it would start testing end-to-end encryption in Messages for Android. After being limited to the beta channel, E2EE is now rolling out to all stable users.
With end-to-end encryption enabled, Google or other third-parties cannot read the contents of your RCS chats as it’s in transit between the sender and receiver. Google is using the Signal Protocol and offers a technical paper with more details.
E2EE requires both parties to have Chat features enabled. It does not work for SMS/MMS or group messaging, thought it’s available when you’re using the Messages for web app. If those requirements are met, this layer of security is automatically active for both existing and new conversations. It cannot be disabled in a privacy-conscious stance by Google.
You will see a lock icon in the “Chatting with” banner, timestamps, and on the send button when end-to-end encryption is enabled/used for delivery. Meanwhile, if E2EE is temporarily lost, the default behavior will be to hold the message until that secure connection is regained, though you can decide to send with SMS.
End-to-end encryption in Google Messages was quietly announced alongside other summer Android announcements today. We’ve reached out to Google for additional confirmation.
FTC: We use income earning auto affiliate links. More.