What information can Google access from RCS chats?

RCS privacy can vary when messaging people on different platforms or using different apps. Older or non-encrypted RCS conversations may not have the same protection as fully encrypted Google Messages chats. Availability of encryption for cross-platform conversations can also change as providers add support, so it’s best not to assume every RCS thread is encrypted.

Even when message content is protected, the service can still have metadata such as phone numbers, device and account information, timestamps, delivery status, IP or network details, and diagnostic or usage data. End-to-end encryption protects the message contents, not necessarily all of that surrounding information.

When end-to-end encryption is active for everyone in the conversation, Google shouldn’t be able to decrypt the message content. However, encrypted copies and related service data may still be processed or stored temporarily. Encryption depends on the messaging clients and features being used, so check whether the conversation shows the end-to-end encryption indicator.