Microsoft Recall and the case for on-device screenshot control
Short answer: Recall is a Windows feature that records your screen in the background so you can search what you saw, and the debate it set off is worth paying attention to even if you never run it. The first preview shipped with a snapshot store that was not properly protected, Microsoft pulled it, and the version that returned is opt-in, gated behind Windows Hello, encrypted on disk and able to exclude apps and sites. The useful thing to take from all of it is a principle, not a verdict: the safest screen content is the content you choose to capture and redact on your own machine, with nothing uploaded. This guide explains what Recall actually does, treats it fairly, and draws the line between an always-capturing system and a deliberate capture-and-scrub loop.
Two ways your screen becomes data
Recall is one example of a wider shift: screen content turning into searchable, stored data. There are broadly two models for how that happens, and they have very different default postures. One captures on its own and asks you to carve out exceptions. The other captures nothing until you ask, and gives you a moment to clean the result before it travels.
| Capture model | What gets recorded by default | Your control |
|---|---|---|
| Ambient background capture | Snapshots of the active screen on a timer or when the window changes, indexed for search, until you exclude something. | Opt out per app or site, pause, delete; the burden is on you to remember |
| Deliberate capture | Nothing, until you press a shortcut for one specific shot. | Total, by default; you decide each capture |
| Upload-to-edit tool | Your unredacted original, sent to a server before any redaction happens. | Limited; the sensitive version has already left your device |
| On-device capture and scrub | One shot you asked for, redacted on your machine; only the cleaned copy is shared. | Total; nothing is uploaded and the secret never leaves |
What Recall actually does
Recall is a feature of Windows 11 on Copilot+ PCs. When it is turned on, it takes snapshots of your active screen every few seconds and whenever the content of the active window changes. It then runs optical character recognition over those snapshots and builds a semantic index, so you can later search for something you saw, a document, a message, a page, by describing it rather than remembering where it was. The pitch is a searchable timeline of your own screen, kept on the device.
The part worth holding onto is that this is automatic by design. The value of a searchable timeline depends on it capturing things you did not think to save, which is also exactly why the privacy questions are sharp. A tool that records what you did not choose to record will, sooner or later, record something you would never have chosen to keep.
The privacy questions it raised, fairly stated
When Recall was first previewed in 2024, security researchers found that the snapshots and the text extracted from them were stored in a local database that was not properly encrypted, which meant anyone with access to the machine, including malware running as the user, could read a rolling record of everything on screen. Testing at the time also showed the automatic filters for sensitive content, things like card numbers, did not reliably catch them. Microsoft postponed the rollout in response.
The version that returned is meaningfully different, and it is only fair to say so plainly. Recall is now opt-in, so nothing is captured unless you switch it on. The snapshot store is encrypted, with the keys protected by the device's secure hardware and tied to your Windows Hello sign-in, and the data is decrypted only inside a protected enclave when you authenticate. You confirm it is you with Windows Hello each time you open Recall or change its settings. You can pause capture, exclude specific apps and websites, and delete snapshots. Those are real mitigations, and they move the feature a long way from where the first preview sat.
The honest caveat is that researchers have continued to probe it, and the open questions tend to cluster around what happens to data once it has been decrypted for display, rather than the encrypted store itself. None of that makes Recall reckless. It makes it a feature with a privacy model you should understand before you opt in, which is a reasonable thing to ask of any system that records your screen.
Why the default posture is the whole game
Set the specifics of any one feature aside and a pattern shows up across the whole category of screen capture. The thing that decides your exposure is the default. An ambient recorder starts from capture everything and relies on you to subtract: to remember to pause before you open your bank, to keep the exclusion list current as you install new apps, to trust that the filter caught the card number this time. Every one of those is a chance to forget, and forgetting is the normal case, not the exception.
A deliberate capture tool starts from the opposite default. Nothing is recorded until you ask for a specific shot, so the question is never what did I forget to exclude. It is what did I choose to capture, which you answered the moment you pressed the shortcut. The same logic is why a privacy-conscious habit beats a one-off effort, a point worth its own walkthrough in the guide to a privacy-first screenshot workflow on Mac. The default does the heavy lifting, so you do not have to be vigilant on the tenth screenshot of the day.
On-device is the second half of the principle
Choosing what to capture is one half. The other is making sure the cleaning happens where the image already is, rather than somewhere it has to travel to. This is the trap that catches people who do try to redact: they reach for a web tool, and to redact a screenshot online you first upload the unredacted original, so the sensitive version reaches a server before anything is hidden. The mechanics of that trade are laid out in what actually happens when you upload a screenshot to redact it. The point made loudly by the Recall debate, that screen data should stay on the device, applies just as much to the tool you use to clean a single shot.
On-device redaction closes that gap. The capture, the scrub and the saved result all happen on your own machine, and the only thing that ever leaves is the cleaned copy you deliberately share. There is no upload of the original, no copy sitting in a service's logs, and nothing to ask a third party to delete later.
The redaction has to be the kind that holds
Keeping the image on your machine only helps if the redaction itself cannot be undone. A draggable box on a layer, a soft blur, or a highlight over text can all look hidden while leaving the original recoverable, and a screenshot is the easiest possible case for that kind of recovery, as the guide to redacting screenshots on a Mac sets out. The redaction has to be written into the pixels and underived from what it hides.
That is how ScrubShot's Scrub tool works: each block in a scrubbed region is filled from color samples taken at random across the region, not from an average of the pixels underneath, so there is no relationship between the mosaic and the content it covers and nothing to work back from. While we are on what a screenshot carries, the pixels are usually the real leak rather than the file's metadata, a distinction unpacked in the piece on what metadata Mac screenshots actually contain.
About this guide
I make ScrubShot, a Mac app for redacting screenshots on the device, so I have a clear interest in the on-device side of this argument and I would rather be upfront about it than pretend otherwise. I have tried to be fair to Recall rather than use it as a bogeyman: the first preview had genuine problems, the shipped version added genuine mitigations, and researchers still have genuine questions. ScrubShot is a Mac app and Recall is a Windows feature, so this is not a head-to-head between products. It is a guide to a principle, deliberate capture and on-device redaction, that holds regardless of which operating system you are sharing a screenshot from.
FAQ
- Does Microsoft Recall run on a Mac?
- No. Recall is a Windows 11 feature for Copilot+ PCs, and there is no Mac version. This guide is not about your Mac running Recall. It is about the principle the Recall debate put on the table, which applies to anyone who shares screenshots on any operating system: the safe posture is content you deliberately capture and redact on-device, with nothing uploaded to a service to be processed.
- Is Microsoft Recall a privacy disaster?
- That is not the fair reading. The first preview had real problems, including a snapshot store that was not properly encrypted, and Microsoft pulled it. The version that shipped is opt-in, gates access behind Windows Hello, encrypts the data on disk and lets you exclude apps and sites. Researchers still raise questions about what happens to data once it is decrypted on screen. The honest summary is a feature that is far better protected than its first preview, with a privacy model you should understand before you turn it on.
- What is the difference between ambient capture and deliberate capture?
- Ambient capture means a background system records your screen on a timer or whenever the active window changes, so the default is that everything is captured unless you remember to exclude it. Deliberate capture means nothing is recorded until you press a shortcut for a specific shot, so the default is that nothing is captured. With deliberate capture you also get a natural moment to redact the sensitive parts before the image goes anywhere, which an always-on recorder does not give you.
- How does ScrubShot fit the on-device principle?
- ScrubShot only captures when you press the shortcut, redacts on your Mac, and never uploads the image. You scrub the sensitive parts into a random mosaic that cannot be worked back, then copy or save the cleaned version. The original and the cleaned copy both stay on your Mac unless you choose to share the cleaned one. There is no background recorder, no snapshot store and no server in the loop.
Try it
ScrubShot is built around the principle in this guide. It captures only when you press the shortcut, you drag the Scrub tool over anything sensitive to write a random mosaic straight into the image, then you copy or save the cleaned version. There is no background recorder and no upload, so the only thing that ever leaves your Mac is the copy you chose to share. There is a free 7-day trial with no card required. After that it is $30 once.