“Despite being an inherently AI-powered feature, it can’t distinguish between ordinary computer usage and genuinely sensitive information — like passwords, health information, or trade secrets that must be protected at all costs.”
Our reading, the sentence that was checked:
Microsoft's AI-powered Recall feature cannot distinguish ordinary computer usage from sensitive information such as passwords or health data.
Assessment: Supported Evidence as of
Where and when Ed Zitron wrote it
Where's Your Ed At, The Rot-Com Bubble, paragraph 12.
- Said
- Source observed
- live page, full text, public
- Evidence as of
- the cutoff for this assessment
- Assessment recorded
- assessment wyea-rotcombubble-920267-a1
We recorded 17 claims from this post. See every claim from this post.
The wording above is the version this site observed on 2026-10-28. The source may have been edited after 2024-06-03. This page does not claim the wording was captured then.
What the claim commits to
- Kind
- Observation
- Deadline, as the speaker wrote it
- None stated. This site does not add one.
- Deadline state when assessed
- No horizon
- Deadline state on 2026-10-29
- No horizon (the release’s reference date)
From the speaker
- it can’t distinguish
- ordinary computer usage
- genuinely sensitive information
- passwords, health information, or trade secrets
Our interpretation
- It refers to the original Recall preview announced shortly before the post.
- The ordinary reading is that Recall did not automatically recognize sensitive screen content and exclude or redact it because of its sensitivity.
- User-selected app or website exclusions, private-browsing exclusions, and password masking performed by another application do not establish automatic sensitive-content recognition.
- The target period is the announcement-era preview from May 20 through June 3, 2024. Later implementations are outside scope.
Counts as supported if: Publication-era documentation or testing establishes that Recall captured visible sensitive information without automatic content-sensitive filtering or redaction.
Counts as contradicted if: Documentation or reproducible tests establish that the original preview automatically recognized and protected sensitive content of the kinds described.
Retrospective: these criteria were written after the outcome was public.
Current assessment
Was it true for the period described?
Outcome: Supported
The dated evidence matches what the claim committed to, under the criteria frozen before grading.
Scored on a plain reading. The speaker named no measure for this claim, so it was judged on the reading an informed reader would take, stated below under our interpretation. Both reviews had to find that reading fair.
- Evidence as of
- Deadline state when assessed
- No horizon
- Assessment recorded
- Policy version
- 2026-10-28.7
Rationale
The original preview documentation explicitly said Recall did not perform content moderation and would not hide passwords or financial account numbers. That supports the ordinary reading that it lacked automatic protection based on content sensitivity. Manual exclusions and other privacy controls do not contradict this narrower claim. The conclusion applies to the announcement-era preview.
Limitations
- The primary wording survives here in a contemporary secondary source.
- This does not mean Recall lacked all privacy controls.
- Later versions are outside the target period.
Evidence (1 item)
Supports the claim: Gibson Research Corporation, Security Now!,
does not perform content moderation.
Why it matters here: The contemporary reproduction of Microsoft's own FAQ explicitly says that the preview did not hide sensitive information. The surrounding FAQ lists manual and application-based exclusions, which do not amount to automatic sensitivity recognition.
- Publisher
- Gibson Research Corporation, Security Now!
- Kind of source
- Secondary summary
- Describes events of
- Public from
Where it was said (1)
Said once in the sources this register covers.
: Where's Your Ed At, The Rot-Com Bubble
Despite being an inherently AI-powered feature, it can’t distinguish between ordinary computer usage and genuinely sensitive information — like passwords, health information, or trade secrets that must be protected at all costs.
- Where
- paragraph 12
- Published
- 2024-06-03
- Source observed
- , live page
- Access
- full text, public
History
Assessment versions
- Assessment wyea-rotcombubble-920267-a1: Current. Outcome: Supported. Evidence as of 2026-10-28. Public date not recorded.
Recorded events
Assessment publishedBy this site
First assessment published after both reviews and the final-text check passed.