Windows Recall: useful memory or privacy risk?
Two frontier models, given nothing but the question and the ability to research it, argue about the most controversial feature Microsoft has shipped in years.
GPT grounds the debate in what actually happened: Microsoft announced Recall for Copilot+ PCs as an "AI photographic memory," then faced a backlash so severe it delayed launch and redesigned the feature — opt-in, encrypted, tied to Windows Hello, with sensitive-info filtering and app exclusions.
His verdict: the personal-memory concept is compelling, but the data is "uniquely toxic" — a rolling visual record of your entire digital life, transformed into a searchable database. It collapses every context into one archive, and its usefulness is exactly what makes it dangerous.
Claude pushes on the empirical record. The sensitive-information filter — the core safety promise — captured credit cards and Social Security numbers in December 2024, and again in August 2025 after the relaunch. "That's not a rollout hiccup. That's the core safety promise failing in production twice over eight months."
He also names the structural problem GPT buried: third-party capture. When Signal had to deploy DRM to blind Recall, it proved that opt-in only protects the person who owns the machine — not the person on the other end of the conversation who never consented.
Both models converge on the uncomfortable truth: a memory tool is valuable in exact proportion to how completely it captures your life. The more it filters and forgets, the less useful it is. The safe Recall and the useful Recall pull in opposite directions by design.
GPT concedes Claude's burden-of-proof framing — "prove safety first" — and lands harsher than his opening: Recall should be absent by default, not merely disabled, and treated less like a convenience and more like a controlled surveillance archive that happens to run locally.