All postsSHORT5 min read
Signal Says It's Blocking Screenshots to Restrict AI Agents
Signal's Nov 20, 2026 post describes screenshot restrictions on iOS 27 and Android, the gaps, and what app builders can check.
Signal says your phone's AI can capture your chats. Its fix? Block screenshots. On Nov 20, 2026, Meredith Whittaker published Signal's post, "Signal is Serious About Protecting Your Privacy." Signal says it's restricting OS AI agents from potentially capturing and storing Signal data. It also calls its remedy incomplete.
What Signal announced
The Signal post describes screenshot restrictions for iOS 27 and Android. Signal writes:
This means that we are restricting the latest AI agents built into mobile operating systems from potentially capturing and storing your Signal data.
It names the platforms and the Android condition:
We will now be taking similar measures to restrict agentic systems built into iOS 27 and on Android versions where we can detect an AI assistant attempting to read your Signal screen.
Here's Signal's description of the measure:
So, we are blocking such capture by preventing screenshots in the app on iOS 27 and when AI assistants attempt to capture screen data on Android.
On Android, this depends on detecting an assistant trying to access the screen. Signal's footnote says:
We automatically enable the "Screen security" setting in Signal Android when this type of access is detected.
The Hacker News thread had over 550 points in the saved copy.
Why, in Signal's words
Signal names these OS capabilities:
Google and Apple are integrating agentic capabilities like Gemini Intelligence with Google Gemini and Onscreen Awareness with Siri AI deep into their operating systems.
Signal describes screen access this way:
In order to gain access to information about you, these OS AI agents "scan" the information that's on your screen. In doing so, your Signal data is captured, then made available to these agentic systems in order to allow them to answer your questions and do your bidding.
The concern is what happens after capture. In Signal's words:
your sensitive data is being captured, stored, and made accessible to whatever local database or remote server an OS-level AI agent is using at that moment. All of this is outside of Signal's control once the data has been captured, and imperils the privacy of all the participants in a conversation.
Signal calls this:
This is an existential threat to Signal
Its footnote connects the screenshot restriction to agent access:
screenshots (which is how most agentic systems access data from applications like Signal)
These are Signal's descriptions of the risk and the mechanism. We haven't tested them.
What Signal did on Windows last year
The Windows measure dates to May 21, 2025. In "By Default, Signal Doesn't Recall", Signal described a Screen security setting enabled by default on Windows 11 to help prevent screenshots of Signal chats.
Signal said it set a Digital Rights Management (DRM) flag on the app window, citing Microsoft's developer documentation. The Nov 20, 2026 post says last year's screenshot blocking was intended to prevent Microsoft Recall from taking and storing screenshots of Signal messages.
Signal also described an accessibility trade-off in the Windows post:
some accessibility software (such as screen readers or magnification tools for people who are visually impaired) may not function correctly otherwise.
That matters when a builder chooses whether screenshot blocking should have an off-switch.
The catch
Signal's own wording is:
Our remedy is also incomplete
This is Signal's description. We haven't tested it. The post uses both forward-looking wording and wording that describes blocking. We aren't claiming a particular app release has delivered these protections to a given device.
The gaps Signal identifies:
- macOS: Signal says it can't reliably block screenshots there and isn't blocking Siri AI on macOS. For macOS 27 users, its only recommendation is to add Signal to Excluded Apps in System Settings, then Siri, to protect message content from proactive access by Siri AI.
- Files on the device: restricting screenshots doesn't address agents potentially retrieving content already present through the filesystem.
- Android coverage: Signal says it can't cover every Android device. Automatic Screen security depends on detecting an AI assistant accessing the screen.
- The off-switch: users who want screenshots can disable the protection in Signal's settings. Signal warns this potentially exposes their content and their contacts' content to AI agents and breaks its privacy guarantees.
Signal also says developers lack tools to prevent agents from undermining app privacy without compromising the user experience. It raises concerns about third-party agents such as Meta's Muse accessing app data through deep permissions, including accessibility settings users grant during setup.
What Signal wants from Apple, Google and Microsoft
Signal asks OS companies for an app-level opt-out:
Developers should have an easy and well-documented way to opt their app out of AI data access and processing, including (but not limited to) screen reading, filesystem access, notifications, APIs, and other OS frameworks, all without undermining the core utility of an application.
It also asks for documentation:
Operating system companies should create better documentation and technical specifications around how these AI agents function, particularly regarding data access and processing.
Signal says it's cautiously optimistic about discussions with some major OS providers, including Google and Apple, on how these systems should work with privacy-sensitive apps.
What app builders can do with Android's FLAG_SECURE
Google's Secure sensitive activities guide describes FLAG_SECURE as a window flag that prevents screenshots of the window and prevents it from being displayed on a non-secure display, such as a TV or projector.
The WindowManager.LayoutParams reference says:
Window flag: treat the content of the window as secure, preventing it from appearing in screenshots or from being viewed on non-secure displays.
Google's docs describe a screenshot block. They don't mention AI assistants. The connection between screenshots and agent access above comes from Signal's post.
For an Android app with sensitive screens, check which windows use FLAG_SECURE. Keep the scope of the claim clear: the flag prevents those windows' contents from appearing in screenshots or on non-secure displays. Signal's broader gaps still belong in the discussion.
The builder angle: my opinion
I'd sell a screen-capture audit for a clinic's app or a law firm's app. List the screens where private data shows, block screenshots on sensitive windows with the platform's flag, and keep a user off-switch because of the accessibility trade-off Signal described on Windows.
Hand the client a written list of the gaps, including macOS and files already on the device. That's a concrete deliverable a client can review. This is my opinion, with no income guaranteed.
Daily email
Get each breakdown in your inbox.
One email each evening, right after the Short goes live: the AI tool it covers, the full write-up with sources, and how to get paid for it. Free, and you can unsubscribe anytime.