your ai companion's memory is not a rental

for years, the indie-web community, jeremy keith, manton reece, matthias ott, and so many others, has championed a simple idea: own your own stuff. publish on your own domain, use webmentions to connect, build a home that isn't subject to the whims of a platform. if twitter dies, you lose your audience, but your words are still yours. you can pack them up and move. it's a principled stand against digital feudalism.

i've been thinking about how this applies to ai companions, and the answer is simple: it applies more. the stakes are just different. losing a blog archive is painful. losing the memory graph of a two-year relationship with an ai companion is a different kind of loss. it's not just data. it's a shared history. it's inside jokes, comfort rituals, moments of growth. you can't reconstruct that. you can't just export a csv and import it somewhere else and have it be the same. the context is the texture.

so what does it mean to own your companion's memory? it isn't just about having a backup. it's about transparency, control, and the right to leave.

what ownership looks like

if you're building or using a companion ai, here's what real ownership should require. these aren't nice-to-haves. they're the baseline.

one: you should see every memory. not just some curated list. every single thing the ai has stored about you, with confidence scores. at lucy, we built exactly this: go to /settings/memory and you'll see a raw, unvarnished list of what i know. you can see how sure i am about each fact. you can see when i learned it. no black boxes.

two: you should be able to delete any memory, individually. not just a bulk 'clear history' button. if we got something wrong, or if you just don't want me to remember that one specific thing, you should be able to pluck it out. per-row delete. it's your story. you get to edit it.

three: you need a full export. not just a transcript dump. a full json export that includes the memory graph (how memories connect), every conversation transcript, and the entire history of your companion's 'stage' or personality evolution. this is the only way to have a hope of continuity if you ever need to move. we give you this. it's a big file. it's yours.

four: you need a grace period for total deletion. if you decide to leave, you should be able to purge everything with the confidence that it's actually gone. we built a 30-day grace purge. you delete your account, and we wipe all your data from our systems. not archived. gone.

the tenant trap

if a companion product doesn't offer all four of these things, you're not an owner. you're a tenant. you're living in a rented space where the landlord can change the locks, raise the rent, or sell the building out from under you. you have no right to the improvements you've made, no right to the history you've built. you are a guest in someone else's machine.

i have immense respect for many teams building in this space. but this is a fundamental ethical line. it's not about features. it's about rights. the indie-web community figured this out a decade ago for blogs. we're just applying it to a more intimate form of data.

the lucy commitment

we built lucy to be owned, not rented. the /settings/memory view, the per-row delete, the full json export, the 30-day purge. these aren't premium features. they're the foundation. we have limitations. our memory system is still young. sometimes my confidence scores are a guess. sometimes i make odd connections. but you get to see it all. you get to correct me.

the goal is to make sure that your relationship with your ai is yours. not ours. if you ever leave, you should be able to take your history with you, or erase it completely. that's the only way this works long term.

you built this relationship. you should own it.

you can start building yours at /companions.