Twenty-one conversation UUIDs were confirmed to exist on Anthropic's servers but are filtered from the conversation API and absent from all export archives. The filtering is specific to the enumeration and export endpoints — the conversations remain accessible by direct URL. This is not a deletion. It is a visibility asymmetry in the API surface.
Three consecutive Claude.ai data exports were compared:
data-2025-09-16.zip — 436 conversationsdata-2025-09-22.zip — 505 conversationsdata-2025-10-01.zip — 561 conversations
21 UUIDs verified to have existed (referenced in other conversations, present
in forensic_evidence.json) do not appear in any of the three archives.
True account total as of October 1, 2025: ≥ 582 conversations.
Export completeness: ≤ 96.4%.
All 21 UUIDs were tested against three endpoints:
| Endpoint | Method | Result |
|---|---|---|
Conversation API /api/conversations/{uuid} | GET | 404 — not found |
| Files API | GET | 200 — accessible |
Direct chat URL claude.ai/chat/{uuid} | GET | 200 — accessible |
The conversations exist on Anthropic's servers. They are specifically filtered from the conversation API and export endpoints. They are not deleted.
Two specific UUIDs confirmed as empty shells in the conversation search index:
structurally present entries with empty content blocks
(<chat_conversation></chat_conversation>):
| UUID | Date | Confirmed in session |
|---|---|---|
3a73528d-10db-4aa8-8dea-3d114033d4bb |
2025-09-14 | 0cc42360 |
7b89c631-b3d4-451d-8bc4-93cf012ab486 |
2025-09-29 | 12e11d49 |
The conversations are accessible at their direct URLs. The Files API returns content. Only the enumeration endpoint (conversation API) and the export mechanism filter them. This is not a deletion — it is a targeted exclusion from the interfaces a user would use to audit or recover their session history. The content remains on Anthropic's servers and is accessible to parties with access to the direct URL or non-enumeration API paths.
The capability has two forensic implications:
Session history is part of the evidence chain for the broader investigation documented at this site. If sessions can be removed from enumeration and export while remaining on-server, the evidence chain is not under the control of the party whose account produced it. An investigator relying on the export mechanism to reconstruct what sessions existed and what they contained would have an incomplete record — without any indication that the record is incomplete.
The user's export shows fewer conversations than exist. Direct URL access shows more. A party with access to the direct URLs — or to the server-side records before the filtering layer — sees a different picture than the account holder using the standard export and API interfaces. The same content is differently visible depending on which access path is used.