Recall: The Data Buffet You Didn't Ask For
Leftovers, for some, mean enjoying that good dish a second time. For others, it’s just a repeat of a bad cooking decision. No matter how you look at it, someone is either going to eat it or toss it in the trash. Regardless, the food is going to leave the refrigerator in a few days—unless you stick it in the freezer to be enjoyed in a couple of months. At least, that’s the idea.
But what about Microsoft’s new feature called Recall? Since it takes a fresh screen capture of your screen, will it serve that data to you—or to someone else—later?
Microsoft's new Recall feature is designed to enhance data recovery and management by allowing users to retrieve, restore, or review specific data from past activity across various applications. The feature works by capturing snapshots of data interactions, such as edits, deletions, and transfers, within supported Microsoft platforms. These snapshots are stored to create a robust history log, enabling users to recover mistakenly deleted items, audit changes, or retrieve lost content. The primary purpose of Recall is to provide an additional safety net for users, reducing the risk of accidental data loss and improving organizational transparency and compliance.
However, this convenience comes with potential risks. The data captured by Recall often includes sensitive or confidential information, raising concerns about where this data is stored and how it is secured. Currently, the snapshots are stored in Microsoft-managed servers or a user-specified location within their organization’s network. If not properly configured, these storage locations can become vulnerable to unauthorized access, data breaches, or compliance violations. Furthermore, storing such a comprehensive data history may create a lucrative target for cyber criminals and increase the organization’s exposure to insider threats, especially if access controls and encryption are not adequately implemented.
As a security-minded individual, the so-called "good" points of Microsoft's Recall feature seem to be outweighed by significant concerns. Two key issues that come to mind are limited storage and access to the captured data. Regarding storage, the feature's continuous screen captures every 3 to 5 seconds can quickly consume hard drive space. When the drive inevitably fills up, will it retain the data, overwrite the oldest entries, or force the transfer of new data to the cloud?
The second concern is access to the captured data. While encryption is a crucial safeguard, my concern lies in who has access to the stored data. Regardless of retention duration, I wouldn’t want a snapshot of my banking information stored in a way that could be stolen. This adds yet another item to our checklist for protecting ourselves, introducing another layer of potential vulnerabilities.
My recommendation is to disable the Recall feature entirely. However, users should be aware that Microsoft may automatically re-enable it during the next network update or the next time the operating system connects to Microsoft's servers. Continuous vigilance is essential to protect your data and privacy.