Signal announced on November 20, 2026, that it is restricting screenshots on iOS 27 and supported Android devices to limit operating-system AI assistants’ access to visible messages. The measures work differently across the two platforms, and Signal says they cannot provide complete protection against every route an assistant might use to access content. (Signal)
In the announcement, Signal president Meredith Whittaker identified Google’s Gemini Intelligence and Siri AI’s Onscreen Awareness as the integrations motivating the change. Signal’s concern is about access to messages displayed on a device, rather than a reported failure of its encryption. Its descriptions of the restrictions are company claims, not independently tested security guarantees. (Signal)
Different approaches on iPhone and Android
Signal says it is preventing in-app screenshots on iOS 27. Its announcement includes an illustration showing a setting labeled “Block Siri AI” switched on. That image establishes what the illustrated control looks like; by itself, it does not establish the default configuration that every user will receive. (Signal)
On Android, Signal says it automatically enables “Screen security” when it detects an AI assistant attempting to access the screen. It explicitly cautions that it cannot cover all Android devices. The distinction matters: this is a detection-dependent response, not an announcement that screenshots are universally blocked across every Android phone. (Signal)
Signal attributes that approach to differences between Android vendors. For many vendors, it says, attempted screenshots cannot reliably be detected when screenshots are already disabled. It chose to respond to detectable assistant access rather than leave users encountering screenshot failures without an explanation. That technical account remains Signal’s explanation, without a published device-by-device assessment in the approved reporting material. (Signal)
Users can disable the protection in Signal’s settings to regain screenshot capability. Signal warns that doing so could expose both their own content and their contacts’ content to AI agents. The trade-off is therefore not simply between two convenience settings: restoring screenshots also removes a barrier the company considers important for conversation privacy. (Signal)
The announcement should not be read as a universal rollout notice. Although it names iOS 27, it does not establish a completed rollout across supported devices or specify a distribution schedule. November 20 is the announcement date, not proof that every eligible installation received the same behavior that day. (Signal)
Screen access is becoming an AI feature
The broader industry direction helps explain the dispute. In its May 12 introduction of Gemini Intelligence, Google described app automation that can use screen or image context. Google also said Gemini acts on the user’s command and stops when the task is complete. Those statements describe Google’s intended interaction model; they do not independently establish how Signal’s restrictions perform. (Google)
For workplace devices, Google’s September 23 Android Enterprise announcement described Gemini workflows using real-time on-screen context across applications. It also said administrators can configure, restrict or disable AI automation, and described work-profile safeguards intended to prevent personal agents from accessing corporate apps and data. These are platform-provider assurances, rather than independent findings about isolation. (Google)
Together, those developments illustrate a distinction relevant to enterprise security teams: an organization’s device-management controls and an individual app’s screenshot restrictions address the problem from different positions. Google describes administrative control over automation; Signal is trying to limit access to its own displayed content. Neither announcement alone demonstrates how the two approaches interact on a particular managed phone. (Google)
A limited remedy, not an all-purpose shield
Whittaker acknowledges that screenshot blocking is incomplete. Other potential access routes could include retrieving content already on a device through the filesystem. That warning is a statement about the limits of screen protection, not evidence that an AI agent has extracted Signal’s protected message database or bypassed its encryption. (Signal)
Signal also says it cannot implement equivalent screenshot protection on macOS. For macOS 27, it recommends excluding Signal from proactive Siri AI access through system settings. The mobile measures follow its earlier use of screenshot blocking on Windows 11 to keep Microsoft Recall from capturing Signal messages by default, according to the company. (Signal)
Signal is asking Apple, Google and Microsoft for documented developer opt-outs covering AI access to screens, files, notifications, APIs and other operating-system frameworks without sacrificing ordinary app functionality. That request goes beyond screenshots: it seeks controls over the different ways operating-system assistants could encounter app content. (Signal)
For users, the supported conclusion is narrower than saying Signal now blocks all AI access. The company has announced screen-capture restrictions, described meaningful platform differences and acknowledged remaining gaps. No independent assessment retrieved for this article establishes their effectiveness across supported phones, so the measures should be understood as a stated privacy defense rather than a verified comprehensive guarantee.




