Konshus.ai

A practical guide · ~8 min read

How to Delete Specific Things ChatGPT, Claude, and Gemini Know About You

Most "how to delete ChatGPT memory" guides tell you to wipe everything and start fresh. That's the bazooka option. Most of the time you don't want a bazooka — you want a scalpel for the one weird thing the assistant keeps bringing up. Here's how to do it per provider, and what the per-claim alternative looks like.

ChatGPT (OpenAI)

  1. Open ChatGPT in a browser → click your name → Settings.
  2. Go to Personalization → Memory → Manage.
  3. You'll see a list of memory entries. Click the trash icon next to any one to delete it individually.
  4. To wipe everything: Clear ChatGPT's memory button at the top.
  5. For a full data deletion request (server-side, GDPR/CCPA): privacy.openai.com → request data deletion.

What this doesn't do: it doesn't stop the model from re-inferring the same fact next time you start a chat that touches the topic. The entry is gone; the pattern isn't.

Claude (Anthropic)

  1. Claude doesn't have a long-term Memory store like ChatGPT does — most "what Claude knows about you" lives in Custom Instructions and Projects.
  2. Open Settings → Profile to edit global Custom Instructions.
  3. Open each Project and edit the project knowledge / instructions to remove the specific fact.
  4. For server-side deletion: privacy.anthropic.com → submit a data deletion request.

Claude's model is less leaky between sessions, which means surgical deletion is more tractable — but only if you've kept your context in Projects rather than relying on the model's working memory across chats.

Gemini (Google)

  1. Open myactivity.google.comGemini Apps Activity.
  2. You can delete individual past conversations or set Auto-delete (3, 18, or 36 months).
  3. Gemini's personalization (where rolled out) is surfaced in Settings → Personalization.
  4. For broader account-level deletion: takeout.google.com to export, then delete via your Google Account → Data & privacy.

Gemini's memory layer is the least transparent of the three, and changes by region. If a specific weird claim keeps coming up, the most reliable lever is deleting the conversation that taught it.

Short answer

Each major provider lets you delete individual memory entries or past conversations, but none of them shows you the link between a bad reply and the entry that caused it. Per-claim editing — every fact pinned to its source so you can surgically delete one without losing the rest — is the Brain Surgery patent pending claim (/patent).

Never lose your AI again

Konshus is one way to solve this — a persistent memory vault and portable persona that follows you across ChatGPT, Claude, Gemini, and whatever ships next.

Meet Konshus

When to nuke instead

Surgical delete is the right default. But there are cases where wiping makes sense:

  • Major life change. You've moved countries, changed careers, ended a long relationship. Half your stored memory is now stale; rebuilding from a blank slate is cleaner than editing one at a time.
  • A breach or shared account. Someone else used your account and you don't trust what's in there. Wipe and restart.
  • You're leaving a provider. Export, then submit a server-side deletion request. The in-product Memory panel doesn't reach the backups; the privacy portal does.

For everything else, scalpel beats bazooka. (We argue the same point about contradictions specifically in why your AI contradicts itself.)

The per-claim alternative

A memory layer built on atoms with sources makes deletion almost boring. The assistant says something weird; you click the reply, see which atoms it used and which source they came from, and remove or supersede the offending atom. The audit log shows the delete. Next reply, the claim is gone. No guessing, no nuking, no months of re-onboarding.

That's the bar. We think it should be the default. Until it is across providers, surgical cleanup via the steps above is the realistic best practice.

Frequently Asked Questions

Delete one thing, keep the rest

Konshus pins every stored fact to its source so you can surgically delete a single claim — with a real audit trail. Brain Surgery, patent pending.

Meet Konshus