Secretus logo
newssignalscreen-securityai-assistants

Signal Restricts AI Screen Capture. Keep Secrets Off Shared Screens

Signal added screen-capture restrictions for iOS 27 and supported Android devices. Check both endpoints and plan a credential handoff that keeps the value out of view.

·5 min read·Secretus Editorial

Before you reveal a recovery code during a support call, check what else can see the recipient's screen. A meeting recorder, a remote support session or a device assistant may have access to the same display. On 20 November, Signal announced new screenshot restrictions to limit what operating-system assistants can read in its app.

This is a change to what can capture a message after it is displayed. End-to-end encryption protects the message on its way to the recipient. Once it is readable on a device, the screen and the tools with access to it become part of the handoff.

What Signal changed on each platform

  • iPhone running iOS 27. Signal says its new Block Siri AI setting is on by default and prevents screenshots inside the app. Check it in Signal under Settings → Privacy → Block Siri AI.
  • Android. Signal automatically enables Screen security when it detects an assistant attempting to access its screen. Detection varies across Android versions. To turn the setting on before showing a sensitive message, open Settings → Privacy → App security → Screen security in Signal.
  • macOS 27. Signal says it cannot reliably block screenshots on macOS. Its guidance for proactive Siri access is to add Signal to Excluded Apps in the system's Siri settings. Review other tools with screen access separately.

Reuters confirmed the announcement and reported that, in its earlier tests, Meta's Muse assistant could read Signal messages using device permissions on a Mac and an Android phone. That was an observation in a test setup. Whether an assistant captured any particular person's messages depends on their device, permissions and activity.

Plan for the moment the secret becomes visible

  1. Send the request without the value. Agree in chat on the person who needs the credential, which system it is for and when it should stop working. A support ticket can coordinate the work with an error code or request ID and a redacted example.
  2. Check both screens. End the screen share or remote session before revealing the value. Ask the recipient to check recording and assistant access on their device too. On managed devices, ask IT which capture and retention settings apply. If you need to test a setting, use a dummy value.
  3. Use the shortest useful access. Where the issuer supports it, give the verified recipient a temporary, narrowly scoped credential. Have them open it privately and enter it in the intended service or approved vault. Confirm receipt without copying the value back into the conversation.

If a usable secret was captured

Start with the credential's issuer. Revoke or rotate a token that appeared in a recording, and regenerate exposed recovery codes using the account's supported controls. Ask the owner of the recording or assistant history where copies may have gone, including exports and automatic transcripts. Handle those copies through the organisation's incident and retention process. Track the old credential's invalidation and the replacement's delivery as separate tasks.

Where Secretus fits

A Secretus one-time share can keep a text secret out of the chat transcript. Share the link only with the intended recipient and ask them to open it on a trusted device outside the call. Treat the link itself as sensitive while it is usable. The revealed value is still visible on the recipient's screen, so the same screen-access checks apply when they open it.

Sources