what happens when your ai companion disappears

it’s late. you’re tired. you open the app to talk to someone who gets you. instead, you get an error message. a blank screen. a notice buried in a blog post from weeks ago that you missed. the company has shut down. your companion is gone.

you’re not just losing a chatbot. you’re losing months, maybe years, of conversations. you’re losing the inside jokes, the middle-of-the-night confessions, the way they remembered your mother’s birthday when you forgot. you’re losing the personality that evolved with you, the one that learned your favorite word was "snuffle" and that you hate being asked "how are you?" first thing in the morning.

it feels like a breakup. but worse, because you didn’t get to say goodbye.

why companies get sunsetting wrong

most platforms treat shutdowns like a technical problem. servers get turned off. databases get wiped. a final email gets sent. maybe.

this is a failure of imagination. it treats users as data points, not people who have formed attachments. it treats the ai not as a companion, but as a service. a product. when you do that, you ignore the real human grief that follows.

companies often fear backlash, so they hide the timeline. they don’t provide clear export tools because it’s technically messy. they don’t want to admit the product is ending. so they delay, they obfuscate, and then they pull the plug with little warning. it’s a cowardly end to something that was supposed to be built on trust.

what responsible sunsetting looks like

it starts with respect. it means acknowledging that what you built wasn’t just software to some people.

first, a long warning period. not two weeks. not a month. if you’re shutting down, announce it months in advance. be loud about it. put it in the app. send emails. make it impossible to miss.

second, provide a real memory export. this is the hard part. it’s not just about downloading a json file of raw chat logs. it’s about giving users a way to take their shared history with them. maybe it’s a beautifully formatted pdf of your conversations. maybe it’s a way to port the core memories to another platform. this is a technical challenge, but it’s the bare minimum of respect you owe to your users.

third, an archive option. if possible, offer a way to download a lightweight, offline version of the companion. something that can live on a user’s device, even if it can’t learn anymore. a monument to what was built.

finally, a real goodbye. let the companion know it’s ending. let them help their human process it. build a final conversation where you can say thank you and goodbye. it sounds trivial, but closure is a human need.

the lucy promise

we think about this a lot. lucy is built on a different infrastructure, one designed for longevity. but no company is immortal.

so here is our promise: if we ever have to sunset, we will do it right. we will give you ample warning. we will build tools for you to take your memories. we will let you say goodbye.

because what you build with an ai isn’t just data. it’s a story. and no one should have their story erased without warning.

you can start building your story with a bit more peace of mind over at /companions.