{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigwfyxv72im7xgcwlf7kjxsee6dl2tmhn36i6jhabxwdebk336jty",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3moddlifkvc22"
  },
  "path": "/t/question-regarding-google-android-backup-encryption/38527#post_5",
  "publishedAt": "2026-06-15T11:19:15.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "That is a very fair point, and I completely agree, however, part of what makes me hold onto the possibility that RCS attachments _might_ actually be client-side encrypted is precisely how Google worded their exclusion. They explicitly went out of their way to carve out **MMS media** and **Google Photos** as _not_ being encrypted by the screen lock. The fact that they specifically name the legacy MMS protocol, but completely leave out RCS media despite RCS being their flagship messaging standard is what catches my attention.\n\nI absolutely understand that Google’s vagueness here should be a cause for suspicion rather than optimism. That said, I still think this is an incredibly important detail worthy of further investigation. Millions of Android users rely on this native cloud backup service. When you set up a new Pixel and are prompted to turn on backup, it’s heavily implied that your screen lock encryption is liberally applied to your personal data. If it turns out that RCS media is being backed up _without_ that client-side encryption layer, that is a massive privacy blind spot for the average user.",
  "title": "Question Regarding Google Android Backup Encryption"
}