{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibr3teutzumizc7irldn6erbxqhwxtihr7x75rkrwaaokkpogbqvi",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3moqy4jl6kff2"
  },
  "path": "/t/android-17-launched-what-new-privacy-security-features-does-it-bring/38585#post_2",
  "publishedAt": "2026-06-20T22:54:41.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "Android 17 features and changes list",
    "Restricted message access",
    "Behavior changes: all apps",
    "Android 17 release notes",
    "[1]",
    "[2]",
    "↩︎"
  ],
  "textContent": "Does anyone know what this is all about? From the Android 17 features and changes list:\n\n> Category | Type | Name\n> ---|---|---\n> Privacy | Change (all apps) | Restricted message access\n> Most apps now cannot access end-to-end encrypted messages.\n\nClicking on the “Restricted message access” link takes me to the Behavior changes: all apps page, but it doesn’t appear to make any mention of this change. It does mention that more detailed information is available in the Android 17 release notes, but I read through them and still couldn’t find anything.\n\nIf “most” apps cannot access E2EE[1] messages, then “some” still can. What are those “some”? Obviously, apps performing E2EE can access their own messages, but if that’s all that’s happening, surely there are better ways to word this, no? It seems to imply other apps not responsible for the messages still can. Why? What E2EE messages are we even talking about here? RCS[2] specifically? Any and all E2EE messages (including those sent from Signal, for example (seems unlikely, but this is awfully vague))?\n\nIf anyone knows anything, I’d be interested in knowing.\n\n* * *\n\n  1. end-to-end-encrypted ↩︎\n\n  2. Rich Communication Services ↩︎\n\n\n",
  "title": "Android 17 Launched, What New Privacy/Security Features Does it Bring?"
}