How to audit what Claude remembers about you (and what it can't show you)
Since March 2026, every Claude tier (Free included) keeps a persistent memory of you across conversations. Convenient. It also means Claude is building a running summary of your role, your preferences, and anything you've told it to remember. If you want to know what a product has stored about you, here's how to check.
Quick answer > To see what Claude remembers: Settings → Capabilities → Memory. You see a synthesized summary of facts Claude has gathered. You can edit individual memories, pause the whole feature (it keeps existing memory but stops Claude using or adding to it), or reset it (permanent delete). What you can't do: export it as a structured record, see which chat produced which fact, or hand it to a DPO as an audit trail.
When did Claude start remembering you?
Anthropic rolled memory out in stages. Team and Enterprise plans got it in September 2025. Pro and Max got it in October 2025. Free got it on March 2, 2026. By mid-2026 it's on by default for everyone on claude.ai, the Claude desktop app, and Claude mobile. It does not apply to the API or Claude Code; those calls are stateless.
It was announced as a feature. It's also a shift in how much Anthropic stores about each user. Memory before this existed only inside individual conversations. Now it persists across all of them.
What exactly does Claude store?
Claude's memory is a synthesized summary, not a transcript. Periodically, Anthropic scans your chat history and updates a profile of facts about you: your role, your preferences, and anything you've asked it to remember. When you start a new conversation, Claude reads that summary first.
You can also tell Claude directly: "remember that I work in regulatory compliance." It updates the summary immediately using a dedicated tool.
The summary is viewable and editable at Settings → Capabilities → Memory. You can delete individual facts, pause the whole feature (which keeps the existing memory but stops Claude from using or adding to it), or reset it entirely, which permanently deletes everything.
What can't you audit in Claude's memory?
Claude shows you the summary, not the underlying record. You can't:
- See which chat produced which fact. There's no provenance. The summary says "works in regulatory compliance" but doesn't tell you which conversation, on which date, Claude inferred that from.
- Export it as a structured record. You can read the summary on screen, but you can't download it as a fact ledger or move it to another tool.
- Hand it to a DPO. A compliance officer can't review the full memory store on behalf of an organization. Only the individual user sees their own.
- Self-host it. The memory lives on Anthropic's infrastructure, with no option to run it yourself.
If you're in a regulated profession, this matters. A lawyer with client matter facts or a consultant under an NDA is now storing fragments of that with Anthropic, and can't fully see what's been kept. "Claude remembers things about me" is fine. "Claude remembers things about me and I can't fully inspect, export, or self-host the record" is a different thing.
How is auditable memory different?
An auditable memory store answers four questions that Claude's summary cannot:
- What is remembered? Each fact, individually, in plain language.
- When was it learned? A timestamp on every fact.
- Where did it come from? Provenance: which conversation, document, or explicit instruction it came from.
- Is it still true? A temporal validity range, so out-of-date facts are distinguished from current ones.
This is the bi-temporal model: every fact is a subject/predicate/object triple with a validity window. "Daniel | has_role | compliance officer | valid 2024-01-01 to present." When the role changes, the old fact's validity closes and a new one opens. The history is preserved.
Calmara is one example of a memory store built this way. The full record is exportable as schema-versioned JSON (Article 20 portability, available on every tier including Free), self-hostable via a Docker bundle, and readable in plain English by anyone you choose to share it with, including a DPO. There are a few other systems in this space. The distinguishing question is always the same: can you read every fact, see when it was learned, and take it with you when you leave?
Why this matters even if you're not in a regulated industry
You don't need a compliance officer to want to know what an AI remembers about you. Memory systems shape what the AI tells you next. A stale fact ("lives in Stockholm" when you've moved, "uses Windows" when you've switched) degrades every future answer. The audit isn't paranoia. It's hygiene.
The test for any AI memory system is simple: show me the record, let me edit it, let me take it with me. Claude passes the first two and fails the third. That's worth knowing before you tell it anything you wouldn't want summarized by someone else.
FAQ
How do I see what Claude remembers about me?
Settings → Capabilities → Memory on claude.ai, the desktop app, or mobile. You see a synthesized summary that you can edit, pause, or reset.
Can I export Claude's memory?
No. As of July 2026, Claude's memory has no structured export. You can read it on screen and delete it, but you cannot download it as a fact record or transfer it to another tool.
Does Claude's memory get used to train models?
Anthropic says memory content is not used to train models. The memory is used to personalize your conversations. If training-data concerns are the priority, the cleaner posture is a system where the memory store never leaves infrastructure you control.
Is Claude's memory the same as ChatGPT's memory?
They're similar in shape: both synthesized summaries, both viewable and pauseable by the user. ChatGPT's launched earlier. The audit limits described here apply to Claude specifically; check ChatGPT's current settings for its equivalent.
What does "bi-temporal memory" mean?
Bi-temporal means every fact has two time dimensions: when the fact was recorded in the system, and the real-world time the fact is true. "Worked at Acme 2020–2023" stays in the record after you leave Acme, marked as no longer current. This preserves history rather than overwriting it.
Can my DPO audit Claude's memory on my behalf?
No. Claude's memory is viewable only by the individual user, not by an organization's data protection officer. If organizational audit is a requirement, you need a memory system designed for organizational review, typically a self-hosted one.