Give your demo three privacy checkpoints
Why now: Signal’s screenshot restrictions put attention on what screen-reading assistants can access; a demonstration plan can avoid relying on those restrictions.
Prompted by today's lead: Screenshot limits target AI access to Signal chats
What you'll need
- A non-sensitive description of a planned AI demonstration, including its duration, audience and demonstration material.
Steps
- Describe the demonstration without including real messages or personal details.
- Paste that description into the prompt to generate a timed run-of-show.
- Check that the plan uses dummy material and fits your available time.
The prompt
Plan the demonstration described below. Return plain text with no Markdown formatting, under 150 words. Produce exactly three timed blocks that add up to the stated duration. For each block, give its start and end time, presenter action, and an explicit privacy pause to check what is visible before proceeding. Use only dummy material; do not suggest opening real messages or claim that any privacy control guarantees protection. Do not invent software features. If a demonstration action is unspecified, use explanation rather than a live software action. Description: [paste your non-sensitive demonstration notes]
What you should get
Exactly three timed blocks total six minutes. Each includes a presenter action and a privacy pause. The plan uses dummy material, invents no software features, and stays under 150 words.
Tested example: Tested on sample input
Input
I have six minutes to introduce screen-reading AI assistants at a neighborhood bicycle repair class. The audience is new to AI. I want to explain the idea using a made-up repair request, then discuss when not to use it. I can show a plain text document with dummy content. I do not need to demonstrate a particular app or open any messages.
Output
0:00–2:00 Presenter action: Explain that screen-reading AI assistants can use visible screen content to help answer questions. Show a plain text document containing only: “DUMMY REQUEST: My bicycle chain slips when I pedal. What should I check?” Explain the idea without running an app. Privacy pause: Check that only the dummy document is visible before proceeding. 2:00–4:00 Presenter action: Explain a hypothetical response: the assistant might suggest possible causes and questions to ask a mechanic. Clarify that it can misunderstand information and cannot physically inspect the bicycle. Do not present its suggestions as a diagnosis. Privacy pause: Check all visible screen areas for unintended content before proceeding. 4:00–6:00 Presenter action: Discuss when not to use it: with private information, without someone’s permission, or as the sole authority for safety-critical repairs such as brakes. Privacy pause: Recheck what is visible before concluding.
How we tested it: How we checked this: an AI model ran this prompt on the sample input on November 20, 2026, and a separate model call checked the result against what the Move promises.