Data Ownership
What the AI Has on You — and How to Take It Back
Memory exposes what the AI remembers about you. Data Ownership broadens that to all the data the AI has touched on your behalf — uploaded files, scraped sources, retrieved emails, persisted preferences. Categorized by source, dated, exportable, deletable. The user-facing inventory of what the system holds.
Framing
The problem
AI products accumulate user data invisibly — uploads, scraped sources, retrieved messages, persisted preferences — with no surface for users to see or control it.
The pattern
Render every fragment of user data the system has touched as a first-class user-facing inventory: categorized, dated, exportable, deletable.
Why chat breaks here
Chat as a UX has no surface for "what do you have on me" beyond memory; data scattered across tools stays invisible to the human it belongs to.
Risks
Faithful inventory can reveal more than expected and break trust if the system has been silently over-collecting.
Avoid when
The system stores only ephemeral session data with no cross-session persistence — a data inventory adds noise without information.
Use when
The AI accumulates user data over time and users need a single surface to inspect, export, and reclaim it.
DOPE evaluation
- Directability
- Export, delete, or scope any item — bulk or individual — without filing a support ticket
- Observability
- Every fragment of user data the system touches is rendered, categorised, and dated
- Predictability
- Deletion is real and surfaces a confirmation; the inventory always reflects current truth
- Explainability
- Each entry shows where the data came from and what features rely on it
Closest neighbours
- Apple · App Privacy Report (Apple) — Settings → Privacy → App Privacy Report renders every domain each app contacted, categorised, dated, exportable. Not AI-specific, but the canonical example of "user-facing inventory of what the system holds on you."
- GDPR · Data Subject Access Request flows (EU regulatory pattern) — Every major product now ships a "Download my data" workflow. Coverage varies (memories yes, retrieved sources sometimes, persisted preferences often missed). The legal baseline the pattern operationalises.
- ChatGPT · Memory export + bulk delete (OpenAI) — Settings → Personalization → Memory shows every saved memory with date and one-tap delete. Custom Instructions export as JSON. Closest consumer-facing implementation of the inventory-with-actions surface.
- Claude · Memory inspector (Anthropic) — Per-project memory page rendering what Claude has learned, with edit and delete per entry. Stops short of unifying uploaded files and retrieved sources into the same surface — the upgrade path the pattern points to.
FAQ
When should I use the Data Ownership pattern?
The AI accumulates user data over time and users need a single surface to inspect, export, and reclaim it.
When should I avoid the Data Ownership pattern?
The system stores only ephemeral session data with no cross-session persistence — a data inventory adds noise without information.
What problem does Data Ownership solve?
AI products accumulate user data invisibly — uploads, scraped sources, retrieved messages, persisted preferences — with no surface for users to see or control it.
Why is chat the wrong fit for this?
Chat as a UX has no surface for "what do you have on me" beyond memory; data scattered across tools stays invisible to the human it belongs to.
Related patterns
- Extends: AI Memory — Memory exposes what the AI remembers; Data Ownership broadens that to everything it has touched on your behalf.
- Often paired with: Incognito Mode — Inventory plus a clean room — see what is stored, then choose to leave nothing new.
- Often paired with: Consent — Inventory needs Consent: the visible permission grants that explain why each item is held at all.