{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidiwkbck3e565u3dynnk7myqbqenam2oycigbalhv3fyomsazjori",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mmieyazoh552"
  },
  "path": "/t/is-the-best-sms-app-a-closed-source-one-with-permissions-revoked/38080#post_4",
  "publishedAt": "2026-05-23T00:20:19.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "Google Messages for RCS unfortunately means giving Google more access to your (GrapheneOS) phone.\n\nIt requires sandboxed play services with minimum network, phone, SMS, and contact (scopes) permissions. On most carriers, it will also require device identifiers. And you’ll need to continuously opt for phone number verification with Google in your phone’s Sandboxed Google play settings.\n\nAND this all has to happen on your Owner profile, which means it’s running all the time rather than a dedicated profile that is turned off in the background.\n\nI’m not convinced that Google isn’t managing to do client side scanning of your messages even if promising E2EE RCS. You already have to give them access to the necessary permissions just to get Google Messages and RCS to work.\n\nI’m not saying not to do it. I’m currently using this RCS setup on my GrapheneOS phone. But I am constantly questioning if this is a net positive or net negative as far as privacy is concerned.",
  "title": "Is the best SMS app a closed source one with permissions revoked?"
}