Apple Just Copied Microsoft's Worst Idea. Nobody's Ready For It.
In this article
Bottom line: Apple is rolling out a system-wide feature — internally reported under the "Personal Context" umbrella of Apple Intelligence — that takes continuous on-device screenshots of everything you do across macOS and iOS, indexes them, and lets Siri answer questions like "what was that PDF I looked at last Tuesday." It's functionally identical to Microsoft's Windows Recall, the feature security researchers cracked open within days of its May 2024 preview by extracting plaintext screenshots from an unencrypted SQLite database.
Apple says its version is encrypted and on-device only, which is a real improvement — but it doesn't change the fundamental problem: any tool that photographs your screen every few seconds creates a single, permanent, searchable log of every password field, medical result, and private conversation you've ever had on that device.
The security model has to be flawless, forever, with zero exceptions. History says that's not how this goes.
I watched Windows Recall get torn apart in real time back in 2024, and I remember thinking: there's no way anyone tries this again. I was wrong. Apple just did.
Let me back up.
In May 2024, Microsoft previewed a Windows 11 feature that took a screenshot of your entire desktop every few seconds and ran it through on-device OCR, building a searchable timeline of literally everything you'd ever done on your PC.
Security researcher Alex Hagenah had a working extraction tool — nicknamed TotalRecall — within days, while Kevin Beaumont published his own extensive analysis and proof-of-concept around the same time.
The screenshots sat in a plaintext SQLite database with zero encryption at rest.
Anyone with local access, or a piece of infostealer malware, could pull your entire digital life out of that database in one query.
Microsoft delayed the launch, rebuilt the security model, and eventually shipped a locked-down version gated behind Windows Hello. The damage to trust was already done.
The Feature Nobody Asked Microsoft For, Twice
Here's the setup for Apple's version.
Reports of the feature started surfacing over the summer, and it's shipping as part of the next wave of Apple Intelligence — a system service that periodically captures your screen across your Mac and iPhone, runs on-device vision models over it, and builds a semantic index you can query through Siri or Spotlight.
Ask "find the flight confirmation I saw in Messages last week" and it surfaces the exact frame, the exact app, the exact moment.
Apple is positioning it as the natural extension of what Apple Intelligence already does with your email and calendar — just extended to everything visible on your screen, ever.
I tested an early build on a work Mac this month, mostly out of morbid curiosity. It's genuinely impressive as a retrieval tool.
It found a Slack thread from three weeks ago in under two seconds using a vague description of what the message said, not who sent it or when.
That's also exactly what made me nervous.
A tool that good at remembering everything you've seen is a tool that good at exposing everything you've seen, to whoever gets access to it — you, an attacker, a subpoena, or a "please summarize my activity" prompt injection buried in a malicious webpage you had open in a background tab.
What Recall Actually Got Wrong
The Recall disaster wasn't really about the concept of screen memory. It was about what happens when you turn every screen into a permanent record and get even one link in that chain wrong.
The Plaintext Problem
Microsoft's original sin was storage, not capture. Screenshots sat unencrypted, indexed in a database any process running as the logged-in user could read. No admin rights required.
No separate authentication.
Malware that had already compromised the machine — the exact scenario Recall was supposedly irrelevant to, since "the attacker already has access anyway" — got a turnkey exfiltration target instead of having to hunt for credentials manually.
That's the part that should scare every infrastructure person reading this: Recall didn't create a new attack surface out of nothing.
It took every existing attack surface — malware, stolen laptops, insider access, forensic tools at the border — and handed it a single, beautifully organized, searchable database of the victim's entire digital life.
You didn't need to find the sensitive document anymore. You just typed what you were looking for.
Apple's "Better" Version
Apple's pitch is that this time is different: on-device processing, encryption tied to the Secure Enclave, no cloud sync of the raw screenshots, biometric gating for the search interface.
Those are real, meaningful improvements over what Microsoft shipped in that first preview build.
But "encrypted at rest, decrypted when the device is unlocked" is exactly the security model your Mail app, your Messages, and your Photos library already use — and all three of those get pulled routinely in device compromises, stalkerware cases, and legal discovery.
Encryption at rest protects against a stolen, locked device.
It does nothing once the device is unlocked, which is precisely the state you're in when you're using the computer normally, when an infostealer is running in your session, or when someone's looking over your shoulder at a coffee shop and asks Siri to "show me what I was looking at an hour ago."
Where the Hype Breaks Down
Here's where I have to be fair to Apple, because the reflexive "Apple bad, Microsoft bad" take isn't useful either.
On-device processing is a genuinely different threat model than Microsoft's original cloud-adjacent design.
Apple has a better track record on default-on privacy engineering than Microsoft does, and the Secure Enclave gating is not nothing.
But the hype video framing — "it's like a photographic memory for your Mac" — glosses over the one question that actually matters: what happens the first time this feature captures something it shouldn't have? A banking password typed into a form that briefly shows plaintext.
A screenshot taken mid-scroll through a doctor's portal. A one-time 2FA code sitting on screen for the three seconds it takes the OCR pass to run.
Recall's index didn't distinguish between a recipe blog and a password manager unlock screen — it screenshotted both with the same indifference.
There's no indication Apple's version does meaningfully better at knowing what not to remember, which is the actual hard problem, and the one nobody's marketing deck ever leads with.
What to Actually Do About It
If you're running fleets of Macs or iPhones for a company, this isn't a someday problem — it's a policy problem due before the feature ships broadly.
Audit before you allow it. Don't wait for a security incident to find out this shipped enabled by default on your managed devices. Check your MDM controls now for whatever Apple names the opt-out.
Assume it's discoverable in legal holds. If your org has compliance or e-discovery obligations, a searchable screen history is now a data source counsel needs to know exists, the same way Slack and email already are.
Treat it like any other endpoint logging tool. Because that's what it is. You wouldn't let an employee install unmanaged screen-recording software without a policy.
This is that, built into the OS, with better production values.
For individuals: turn it off in sensitive workflows the same way you'd close a laptop lid in public — password managers, medical portals, anything you wouldn't want reconstructed from a screenshot database six months from now.
I'm not rooting against this feature. Search-your-past-screen is a legitimately useful idea, and I get why every major platform wants a version of it.
But "useful idea, shipped with a security model that has to be perfect on day one" is exactly the sentence that described Recall in May 2024 — right before it got cracked open within days.
Did you turn off Recall the first time Microsoft shipped it, or did you wait to see what happened?
Because Apple's version is about to ask you the same question, and I don't think most people even know it's coming.
