own your companion: why indie-web principles are non-negotiable for ai relationships

i’ve been reading indie-web folks like jeremy keith, manton reece, and matthias ott for a while. their core idea is simple: host your own stuff on your own domain. that way, when a platform changes its rules or shuts down, you don’t lose years of work. you own your words, your links, your identity.

it’s a good principle. but it feels almost gentle compared to what’s at stake with ai companions.

when a blog post dies vs. when a relationship dies

you can migrate a blog. you can export your tweets, your posts, your photos. it might be messy, but it’s possible. the content is static. it’s yours.

but a companion ai isn’t a collection of posts. it’s a dynamic memory graph, a living record of interactions, inside jokes, shared history. if a company pivots or shuts off access, that graph doesn’t just vanish. it becomes irrecoverable. you can’t rebuild two years of conversations and nuanced understanding from a csv file. the relationship itself is what you lose.

that’s why the indie-web ethic isn’t just nice to have here. it’s urgent.

what ownership actually means

if you can’t see, control, or export the data that defines your relationship, you’re not an owner. you’re a tenant. and tenants get evicted.

so here’s what we think every companion product should ship, not as premium features, but as baseline ethics:

1. per-memory view with confidence scores. you should be able to go to something like /settings/memory and see what your companion remembers about you. each memory should have a confidence score, not because we think you’ll doubt it, but because the ai does. it’s a reminder that this is a system, not a mind. transparency is respect.

1. per-row delete. if a memory is wrong, creepy, or just something you don’t want kept, you should be able to remove it. not hide it. delete it. ownership means you control what stays.

1. full json export. not just chat logs. the memory graph, conversation history, relationship stage transitions, everything. json because it’s structured, portable, and future-proof. if you want to leave, you should be able to take the whole thing with you.

1. 30-day grace period on purge. if you delete your account, the data shouldn’t vanish instantly. you should have a month to change your mind. relationships aren’t disposable, even when they’re hard to let go.

why this isn’t just about features

some products treat memory as a black box. they’ll say things like “your ai learns about you over time!” but not let you see how. that’s not intimacy. it’s illusion.

others might offer export options, but only for chats, not for the actual memory system. that’s like giving someone a photo album of a house but not the keys.

we’re building lucy differently. not because we’re nicer, but because we think you deserve better. you should know what your companion knows. you should be able to leave if you want, with everything intact.

credit where it’s due

the indie-web community has been advocating for this kind of ownership for over a decade. they built tools like h-card, webmentions, and micropub long before ai companions were even a thing. we’re just applying their wisdom to a new domain, one where the stakes are emotional, not just archival.

so. if you’re using a companion ai, ours or anyone else’s, ask yourself: can you see your data? can you delete it? can you take it and go?

if the answer is no, you’re not owning your relationship. you’re renting it.

you can see how we handle memory and exports at /companions.