Post by @phillip@social.lol

2026-04-09 14:35 UTC

RE: https://infosec.exchange/@josephcox/116374994792773696 To stop leaking your Signal messages: Signal &gt; Settings &gt; Notifications &gt; Notification Content &gt; Show &gt; “Name only” or “No name or content” iOS and Android notifications all go through Apple and Google’s servers respectively and are not end to end encrypted. The feds have known and used this for years now. Edit: That last bit doesn’t affect Signal, my bad. The settings change does still protect from the on-device notification DB storing message preview. See this reply for more info https://tech.lgbt/@becomethewaifu/116375432389206118 #privacy #PrivacyMatters #cybersecurity

Replies (1)

@becomethewaifu@tech.lgbt 2026-04-09 15:22

@phillip Two entirely unrelated things, though the notification settings mitigation may close this particular hole. (Depends on whether it's the app or the OS acting on those settings) This particular issue has nothing to do with "unified push" and concerns only an internal detail of iOS, where notifications are stored in a local on-device file outside of the signal app, which the phone also has to be jailbroken to access. Signal already mitigates "unified push" to the point it exposes nothing to google/apple other than "this user possibly received a message." They only send a push to 'wake up' the app to fetch the content directly from signal's servers, with no content exposed (because they can't expose the content to apple/google, as they don't know it themselves)

Open ##1524219