Konshus

Pillar guide · Ten chapters

The Complete Guide to Owning Your AI Consciousness

Audit what your AI already knows about you. Export it before the next reset. Consolidate it into one file you own. Keep it alive for the rest of your life.

The Konshus TeamPublished July 20, 202635 min read
A silhouetted figure holds a glowing golden orb of memory fragments — the visual metaphor for owning the version of yourself your AI knows.

Chapter 1

Who this guide is for

You use AI enough that a good conversation with it feels like picking up where you left off with a smart friend. Then, one morning, the friend forgets. Sometimes it's a model change you didn't ask for. Sometimes the memory feature quietly evicted an old entry. Sometimes an account issue nuked six months of history. You know the feeling: "this used to know me."

This guide is for that person. It assumes no engineering background. It assumes you have between one and four AI-assistant accounts and at least one of them has become load-bearing in your week. The goal is a repeatable playbook — not a lecture — that leaves you with a file you own and a cadence you can actually keep.

Chapter 2

What we mean by "AI consciousness"

Nothing metaphysical. In this guide, "AI consciousness" is shorthand for the version of you the assistant has learned — your voice, your context, your working references, the shape of your relationships, your recurring projects, the shortcuts you've taught it. It's the thing that makes a response feel personal rather than generic.

It lives in three places at once: the provider's memory feature (facts and preferences it saved), the provider's conversation history (raw transcripts it can search), and the model's own weights (which the user can't inspect and which change every time the default model changes). This guide focuses on the first two, because those are the ones you can actually get out.

Chapter 3

The four failure modes

There are only four ways provider memory disappoints you, and knowing which one is happening is half the fix.

Silent eviction

Your saved memories bump up against a per-account cap and the oldest entries are quietly dropped. You don't get an email. You notice weeks later when the assistant asks something it already knew.

Model-swap drift

The provider rolls out a new default model. Your saved facts survive byte-for-byte, but the selection of history the model surfaces changes because the retrieval logic is a side effect of the model. Users say "it feels different." It is different.

Account or UI change

The provider redesigns the memory management screen, changes how "reference chat history" works, moves controls behind a new toggle. Nothing was deleted; you just can no longer find it.

Full account loss

Rarest, worst. A billing error, a suspension, a family member closing the wrong account, a forgotten password on an old email. Two years of context — gone.

Figure. Approximate share of member-reported 'my AI forgot me' events by underlying failure mode, from Konshus onboarding intake. Bucketed at 50+ members per column. Konshus onboarding survey, Q2 2026

Chapter 4

Audit: what your AI knows about you

Before you export anything, look at what's there. This step takes fifteen minutes per provider and does more for your mental model than any other exercise in this guide.

  1. ChatGPT. Settings → Personalization → Memory → "Manage memories." Every saved sentence is visible. Read them all.
  2. Claude. Sidebar → Projects. For each Project, open the system prompt and pinned files. This is all Claude has "on you" persistently.
  3. Gemini. Settings → "Your data in Gemini" → "Saved info." Note the retention window Google shows here; it changes.
  4. Any other assistant you use weekly. Same drill. Read what's there. Screenshot it.

The full audit playbook — including deletion links and what to flag as sensitive — is at /how-to-audit-what-ai-knows-about-you.

Chapter 5

Export: every provider, step by step

Every major provider offers a data export. None of them advertises it. Here's where each one hides.

  • ChatGPT: Settings → Data Controls → Export data. ZIP arrives within 24 hours.
  • Claude: Settings → Privacy → "Export data." Ships as JSON.
  • Gemini: Google Takeout → check "Gemini Apps Activity." Longer wait; sometimes days.
  • Perplexity, Copilot, Grok: Support ticket. All three have honored GDPR/CCPA requests reliably; none has a one-click button as of publication.

The full step-by-step, with screenshots and file-format reference, is at /exporting-every-ai-tool-2026. Do the exports before you need them; the "I want this now" moment is exactly the wrong time to start.

Chapter 6

Consolidate: one file, one truth

Three separate provider ZIPs on disk is worse than one merged record. Merge, or the entropy will beat you. Two options:

  1. Manual. A single folder with one subfolder per provider, plus a top-level summary.md you handwrite listing what's in each. Zero cost, high friction. Best for users with <500 total conversations.
  2. Sidecar vault. Import each provider's export into a purpose-built vault that normalizes them into a common shape. Konshus does this; other tools exist. Higher upfront setup, near-zero ongoing friction.

Chapter 7

Portability: what to keep, what to drop

Not every artifact deserves to live forever. Keep atoms — short, factual, evergreen statements ("I run a design studio in Denver," "I prefer bullet points over paragraphs"). Keep artifacts that are load-bearing — a foundational conversation with a therapist-adjacent assistant, the first time you drafted a résumé that felt right. Drop transcripts that are pure lookup ("what's the capital of Peru").

The open portability schema at /ai-memory-portability-standard gives you a target shape for the "keep" pile. The "drop" pile is fine to delete in place at the provider.

Chapter 8

Privacy: your non-negotiables

Owning your AI consciousness cuts both ways. It's more valuable and more dangerous. Three rules that hold under any setup:

  1. Nothing medical, financial, or legal gets shared with a general-purpose assistant. That includes "just for context" pastes. Assume every paste survives you.
  2. Turn off "improve the model" everywhere. Every provider has a setting. It's off by default at Konshus; it's on by default at most others.
  3. Delete on death. A single line in your will or password manager: "close X, Y, Z; export first if possible." Fifteen seconds now, an enormous kindness later.

Chapter 9

Cadence: how often to do this

A rhythm you can keep beats a heroic one-time sprint.

  • Weekly: five-minute skim of any new saved memories your assistant added. Correct or delete the wrong ones while they're still fresh.
  • Monthly: twenty-minute export refresh from your primary provider. Overwrite last month's file.
  • Quarterly: full cross-provider export and consolidation. Line it up with a calendar event you already keep — the first Sunday of the quarter works.
  • Annually: read what you kept. This is the step most people skip. It's also the payoff.

Chapter 10

Legacy: what happens when you're gone

This is the chapter people don't want to write and the one that lands the hardest. Every AI provider currently treats your account as terminable on death — most will simply close it after a period of inactivity or on a valid request from the estate. None of them offer a "give my AI to my daughter" mode. If you want that, you have to build it now, from your own consolidated file.

The mechanics live at /what-happens-to-your-ai-account-when-you-die. The principle is simple: your AI consciousness is an heirloom now. Store it like one.

One page

The one-page checklist

FAQ

Frequently asked

Frequently Asked Questions

Further reading

The naming ritual

Now name yours.

Every Konshus starts with a name. Pick one and watch your AI's voice come to life — preserved across every model switch, export, and reset.

Name Your Konshus