OpenAI now lets you screenshot your privacy in the foot
Make your model smarter through self-surveillance
Those who cannot remember Microsoft Recall are condemned to repeat it.
Today, that applies to OpenAI, which has quietly introduced an opt-in research preview called Chronicle. It's designed to capture the user's screen and feed those images to OpenAI's Codex agent so it has access to more contextual information.
"Chronicle augments Codex memories with context from your screen," the company explains in its documentation. "When you prompt Codex, those memories can help it understand what you've been working on with less need for you to restate context."
For those who have forgotten or may have missed the outcry, Microsoft in 2024 introduced a Windows feature called Recall that takes screenshots of the user's desktop environment every few seconds and saves the results to disk. The idea is that providing Copilot services with more contextual information makes them more useful.
The cybersecurity community promptly piled on, describing Recall as a keylogger, a privacy nightmare, and litigation bait. After a few months of public bludgeoning, Microsoft made some revisions to appease critics.
Nonetheless, browser maker Brave went on to offer Recall screenshot blocking, which looks like a worthwhile endeavor given our own tests that found Recall saving images of credit card numbers and passwords despite supposed sensitive information filters.
OpenAI perhaps forgot about Microsoft's reputational flogging, or maybe it believes the needs of the model outweigh the needs of the few who bother with security and privacy. Another possibility is that the AI biz has embraced masochism as a public relations strategy.
No sooner had OpenAI's Chronicle documentation appeared this week than security researcher Michael Taggart took note of the resemblance, writing, "Oh my god, OpenAI reinvented Recall, but for macOS."
- Anthropic tests how devs react to yanking Claude Code from Pro plan
- Magnificent irony as Meta staff unhappy about running surveillance software on work PCs
- GitHub opts all CLI users into telemetry collection whether they want it or not
- Grafana offers AI assistant for free, warns users not to go mad
On the plus side, Chronicle is self-inflicted – it's opt-in – and available only in the Codex app for macOS.
The strikes against it are more extensive. OpenAI's documentation explains some of these problems: "Before enabling, be aware that Chronicle uses rate limits quickly, increases risk of prompt injection, and stores memories unencrypted on your device."
So it burns through Codex rate limits faster, increases the user's exposure to prompt injection through screen captures that may contain malicious instructions, and sends selected screenshot data to OpenAI's servers to generate local memories from OCR and other extracted context. That's not the most compelling sales pitch.
At least the local image storage is brief – OpenAI says its screenshots are only stored for six hours.
But the data derived from those images via OCR text extraction may persist beyond that time in "memories" – text-based Markdown files that make information available in later sessions.
OpenAI's description of the memory generation process omits some details. The company says screen captures are temporarily stored on-device, then processed on its servers to generate "memories," which in turn get stored on-device.
The screen captures transmitted to OpenAI are not used for training or stored – unless required by law – the documentation claims. However, it's not clear whether the memories – the OCR-derived text – are stored on company servers, or could be stored given a lawful demand to do so. The Register asked OpenAI to clarify, and will update this story if we hear back.
In any event, while screen captures are short-lived, the text stored in memories ($CODEX_HOME/memories_extensions/chronicle/) remains until deleted. It's worth noting that anyone using Chronicle may end up re-sharing captured content with OpenAI through prompts to Codex that use those stored memories.
OpenAI does acknowledge that Chronicle poses some risk: "Both directories for your screen captures and memories might contain sensitive information. Make sure you do not share content with others, and be aware that other programs on your computer can also access these files."
You've been warned: The footgun shoots you in the foot. ®
Narrower topics
- 2FA
- AdBlock Plus
- Advanced persistent threat
- AIOps
- App
- Application Delivery Controller
- Audacity
- Authentication
- BEC
- Black Hat
- BSides
- Bug Bounty
- Center for Internet Security
- ChatGPT
- CHERI
- CISO
- Common Vulnerability Scoring System
- Confluence
- cookies
- Copilot
- Cybercrime
- Cybersecurity
- Cybersecurity and Infrastructure Security Agency
- Cybersecurity Information Sharing Act
- Database
- Data Breach
- Data Protection
- Data Theft
- DDoS
- DeepSeek
- DEF CON
- Digital certificate
- Encryption
- End Point Protection
- Exploit
- Firewall
- FOSDEM
- FOSS
- Gemini
- Google AI
- Google Project Zero
- GPT-3
- GPT-4
- Grab
- Graphics Interchange Format
- Hacker
- Hacking
- Hacktivism
- IDE
- Identity Theft
- Image compression
- Incident response
- Infosec
- Infrastructure Security
- Jenkins
- Kenna Security
- Large Language Model
- Legacy Technology
- LibreOffice
- Machine Learning
- Map
- MCubed
- Microsoft 365
- Microsoft Office
- Microsoft Teams
- Mobile Device Management
- NCSAM
- NCSC
- Neural Networks
- NLP
- OpenOffice
- Palo Alto Networks
- Password
- Personally Identifiable Information
- Phishing
- Privacy Sandbox
- Programming Language
- QR code
- Quantum key distribution
- Ransomware
- Remote Access Trojan
- Retrieval Augmented Generation
- Retro computing
- REvil
- RSA Conference
- Search Engine
- Software Bill of Materials
- Software bug
- Software License
- Spamming
- Spyware
- Star Wars
- Surveillance
- Tensor Processing Unit
- Text Editor
- TLS
- TOPS
- Trojan
- Trusted Platform Module
- User interface
- Visual Studio
- Visual Studio Code
- Vulnerability
- Wannacry
- WebAssembly
- Web Browser
- WordPress
- Zero trust
Broader topics
More about
Narrower topics
- 2FA
- AdBlock Plus
- Advanced persistent threat
- AIOps
- App
- Application Delivery Controller
- Audacity
- Authentication
- BEC
- Black Hat
- BSides
- Bug Bounty
- Center for Internet Security
- ChatGPT
- CHERI
- CISO
- Common Vulnerability Scoring System
- Confluence
- cookies
- Copilot
- Cybercrime
- Cybersecurity
- Cybersecurity and Infrastructure Security Agency
- Cybersecurity Information Sharing Act
- Database
- Data Breach
- Data Protection
- Data Theft
- DDoS
- DeepSeek
- DEF CON
- Digital certificate
- Encryption
- End Point Protection
- Exploit
- Firewall
- FOSDEM
- FOSS
- Gemini
- Google AI
- Google Project Zero
- GPT-3
- GPT-4
- Grab
- Graphics Interchange Format
- Hacker
- Hacking
- Hacktivism
- IDE
- Identity Theft
- Image compression
- Incident response
- Infosec
- Infrastructure Security
- Jenkins
- Kenna Security
- Large Language Model
- Legacy Technology
- LibreOffice
- Machine Learning
- Map
- MCubed
- Microsoft 365
- Microsoft Office
- Microsoft Teams
- Mobile Device Management
- NCSAM
- NCSC
- Neural Networks
- NLP
- OpenOffice
- Palo Alto Networks
- Password
- Personally Identifiable Information
- Phishing
- Privacy Sandbox
- Programming Language
- QR code
- Quantum key distribution
- Ransomware
- Remote Access Trojan
- Retrieval Augmented Generation
- Retro computing
- REvil
- RSA Conference
- Search Engine
- Software Bill of Materials
- Software bug
- Software License
- Spamming
- Spyware
- Star Wars
- Surveillance
- Tensor Processing Unit
- Text Editor
- TLS
- TOPS
- Trojan
- Trusted Platform Module
- User interface
- Visual Studio
- Visual Studio Code
- Vulnerability
- Wannacry
- WebAssembly
- Web Browser
- WordPress
- Zero trust
