How Windows Recall put a possible public record where no records officer could reach it

The week

On May 20, 2024, Microsoft announced Copilot+ PCs, a new class of Windows laptops with on-device AI features. The most discussed was Recall, which periodically saved snapshots of the screen and made them searchable in natural language. Security researchers soon showed that preview builds stored the captured data in a form other software running as the user could read. In early June Microsoft said Recall would be opt-in, would require Windows Hello authentication and would encrypt its data. On June 13 it pulled the feature from the Copilot+ PC launch and moved it to its Windows Insider testing program. Microsoft later published a redesigned security architecture in September 2024, and the feature returned to testers that autumn.

Recall was debated as a consumer privacy and security problem, and Microsoft’s fixes addressed that debate directly. For public agencies, the fixes created a different problem. Earlier in this series we argued that a chatbot’s history sidebar is a records system with someone else’s retention policy. That history at least lived in a cloud service an organization could, in principle, search, hold and export. Recall’s redesigned store sits somewhere harder to reach. Three properties of the design explain why: where the snapshots live, who can open them, and when they disappear.

Where the snapshots live

Recall’s snapshots and the index built from them are stored and analyzed on the device. Microsoft’s documentation states that they are not sent to Microsoft and need no cloud connection. For privacy, that is exactly what the design intends.

For records management it moves the content outside every tool an agency uses to find records. Public records searches and e-discovery collections in most agencies run against central repositories: email, document libraries, collaboration platforms, case systems. Endpoint collection exists, but it is slow, forensic and usually reserved for investigations. A records request for everything an official saw about a contract award would never touch a laptop’s Recall store under normal procedures.

Whether the snapshots are records at all is a jurisdictional question. Many state laws define a public record by content and use rather than format. A snapshot of a draft memo or a constituent’s case file could be a copy of a record, a transitory record or, in some readings, a record in its own right. Records officers and counsel need to classify it before the feature is turned on, not after a request arrives.

Who can open them

The redesign tied access to the individual user. Snapshots are encrypted, with keys protected by the device’s security hardware and released only after the user authenticates with Windows Hello. Microsoft’s documentation states that IT administrators cannot access or view snapshots on users’ devices. Other users of the same machine cannot either.

That is a sound defense against malware and curious colleagues. It also means the agency cannot retrieve the content without the user. A departing employee, a public official under investigation or a staff member on leave holds the only key. Records law generally makes the agency, not the individual, the custodian of public records. A store that only the individual can open inverts that relationship.

Offboarding shows the problem in practice. Agencies typically preserve a departing employee’s mailbox and files by policy, then reimage the laptop. If Recall was enabled, reimaging destroys a store that no one else could have read. Exit procedures would need a step in which the user, before leaving, either confirms the store holds nothing of record or works with records staff to capture what it does.

Data protection regimes add a separate layer. Criminal justice information under the FBI’s CJIS Security Policy, federal tax information under IRS Publication 1075 and health information under HIPAA each come with handling rules. A local, user-sealed copy of screens showing such data sits outside the audit trails those regimes expect. Recall offers app and website filters and a hook for data loss prevention tools to exclude sensitive windows. Those filters help, but they depend on someone maintaining the lists for every system that displays regulated data.

When they disappear

Recall deletes on its own schedule. Administrators can cap storage and set a maximum retention of 30 to 180 days. When the cap is reached, the oldest snapshots go first. Turning Recall off by policy deletes saved snapshots.

Each of those behaviors can collide with a litigation hold. Once an agency reasonably anticipates litigation, it must preserve relevant information, and automatic deletion of relevant material is precisely what a hold is meant to stop. An administrator who disables Recall fleet-wide in response to a records concern could, in the same action, destroy content that a hold already covered. The reverse risk exists too. An agency that leaves retention at maximum keeps months of screen history it has no business purpose for, all of it potentially discoverable.

The practical consequence is that the enablement decision belongs with records, legal and privacy officers as much as with IT. Microsoft ships Recall disabled and removed on managed commercial devices, and administrators must take deliberate steps to allow it. That default protects agencies with current device management. It does not cover unmanaged devices. Microsoft’s guidance notes that Recall is available by default on unmanaged Copilot+ PCs, subject to user opt-in. Agencies that allow personal devices, or that have pockets of unmanaged hardware, have users who can create a sealed screen archive of agency work without any policy decision.

A workable agency position has three parts. Keep the allow policy disabled until records counsel has classified snapshots. Treat any future enablement as a records schedule change, with retention set to match the classification and a documented procedure for holds. Address unmanaged devices through acceptable use policy and access controls, since device policy cannot reach them.

With hindsight

Recall returned to Windows Insiders in late 2024 and began reaching Copilot+ PCs more broadly in 2025, opt-in, encrypted and gated by Windows Hello. Microsoft’s management documentation, updated through late 2025, confirms the properties discussed here. They include local storage, no administrator access to snapshots, retention limits of 30 to 180 days, removal by default on managed devices, and availability by default on unmanaged Copilot+ PCs. In the European Economic Area, Microsoft added a user-initiated export option that administrators can permit.

The redesign largely settled the security argument. The records question did not go away, because the same pattern spread. More endpoint and productivity AI features now retain user content by default in places central records tools were not designed to search. Agencies that classified the content and set retention before enabling features were in a position to answer requests and holds. Those that relied on vendor defaults depended on those defaults staying the same.