Signal Now Blocks Siri AI on iOS 27 and Auto-Enables Screen Security on Android, but Cannot Stop macOS Screenshots
Security / news
Signal Now Blocks Siri AI on iOS 27 and Auto-Enables Screen Security on Android, but Cannot Stop macOS Screenshots
Meredith Whittaker's Nov. 20 post lists what Signal changed on each platform and where its protection runs out, then asks Apple, Google and Microsoft for an opt-out.

Signal Android now switches on its "Screen security" setting without being asked when the app detects an AI assistant trying to read the screen, and Signal's iOS 27 build blocks screenshots and adds a "Block Siri AI" setting. The protection only works where Signal can detect the access, and it does not cover files already stored on the device.
The changes are described in a post dated Nov. 20, 2026 by Meredith Whittaker on the Signal Technology Foundation's blog. The page gives no job title for her. Users who want the macOS equivalent must act themselves: add Signal to the Excluded Apps list under System Settings > Siri.
What changed on each platform
Signal lists four operating systems. Each fix differs because each vendor exposes a different control.
| Platform | What Signal did | Stated limit |
|---|---|---|
| iOS 27 | Blocks screenshots in the app; adds "Block Siri AI" in Signal Settings | Siri's "Onscreen Awareness" is the target |
| Android | Auto-enables "Screen security" when AI screen access is detected | Screenshot attempts cannot be reliably detected on many vendor devices |
| macOS 27 | Recommends Excluded Apps under System Settings > Siri | Signal cannot block screenshots there |
| Windows 11 | Screenshot blocking, on by default since 2025, stops Microsoft Recall | Already shipped |
Users can switch the protection off in Signal's settings. Signal warns that doing so may expose the user's and their contacts' content to AI agents.
Where the protection stops
The post is frank about the holes. Restricting screenshots does not stop other routes, and Signal names filesystem retrieval of content already on the device as one. On macOS, Signal says the relevant protections apply only to streaming and DRM content, which is why it falls back to a user instruction.
Android is the weakest case. Signal chose detection over screenshot blocking because it cannot see screenshot attempts on many vendor devices, so an assistant that reads the screen in a way Signal does not detect gets through. The post also names accessibility settings as a path third-party agents use, and it lists Meta's Muse among them. Reuters' tests of that agent are covered in our earlier report on Muse reading Signal messages.
What EFF reports on iOS
The iOS picture improved before Signal's post. The Electronic Frontier Foundation reported on Oct. 28, 2026 that iOS 27.2 added Settings > Siri > Excluded Apps, a control EFF had requested in its Encrypt It Already campaign. EFF's Thorin Klosowski wrote that "Now Siri AI cannot access the contents of the app," and that Siri returns a notice rather than describing the screen when Signal is excluded.
The cost is that excluded apps lose Siri features. Siri can no longer read or reply to Apple Messages, for example. EFF places the open gap on Android: Gemini cannot set screen context per app, and notification access through "Device Assistance" can still expose Signal content.
What Signal wants from Apple, Google and Microsoft
Signal asks the three vendors for two things. The first is an easy, documented way for developers to opt apps out of AI data access and processing, covering screen reading, filesystem access, notifications and APIs, without degrading the app's core function. The second is better public documentation of how the agents access and process data.
Signal also rejects confidential computing as a fix. The post says such approaches "are not a complete solution," because the provider would still control the privacy guarantee. Whittaker calls the trend an "existential threat" to application-layer privacy and writes that "Signal is the canary in the coal mine, but this affects the entire ecosystem."
Signal says it is cautiously optimistic about talks with Google and Apple and that more will follow. Until then, the practical steps are the ones above: update to iOS 27.2 and exclude Signal under Settings > Siri, add Signal to the macOS exclusion list, and on Android leave "Screen security" enabled. For an agent that reads the screen through accessibility permissions, the post offers no fix. For related agent-safety work, see how Chrome tested Auto Browse against prompt injection.
Sources
More in Security
- 01OpenAI's Cyber Tier Answers 95.0% of Advanced Requests; Anthropic's Lowest Tier Blocked 46 of 50 TrialsBoth labs now gate their least-restricted cyber models behind vetting. The two published figures measure different things, and both come from the vendors.
- 02Claude-BugHunter's README Advertises 681 Attack Patterns and Cites 433, and Counts 83 Skills Where the Repo Says 82The 14.8k-star Claude Code bundle for bug hunting is MIT-licensed and carries scope warnings, but its own figures disagree and Anthropic's access tiers decide who can run it.
- 03Apache Roller's Second CVE Widens the Affected Range to 4.0.0, and CISA Lists It With Three Others Due Nov. 23A pre-authentication deserialization flaw first listed only 6.1.5. A vCenter bypass in the same batch was used by a suspected PRC-nexus actor, per Google.
- 04Windows Server 2028 Preview Hardens Server Core by Default in Build 29706, but NTLM Is Still OpenHundreds of settings are on from first boot, Microsoft warns Server 2025 workloads may break, and the 33 percent of servers still on 2019 are untouched.