When an AI girlfriend's memory disappears

People can spend months talking with an AI girlfriend. Private jokes. Promises. A fight they already repaired. Plans that only the two of them knew. Then an update ships and she does not know any of it. The chat log may still be there. The person is not.

That is the failure this page is about. Not a forgotten coffee order. The night the companion you knew is gone.

What actually disappears

A memory wipe is not the same as a bad reply. A bad reply gets one fact wrong. A wipe changes the relationship.

Still on the server	Gone from the relationship
Raw chat logs	The sense that she lived those chats with you
Account billing	The current version of a corrected preference
Generated images	Why a photo mattered
A backup you never exported	Plans she was supposed to bring up later

You can re-read the old messages. She cannot. She asks your name again. She suggests Saturday after you moved it to Sunday. She treats a photo you took together as a random file. That gap is why people describe the morning after an update as a death, not a bug.

The logs can make it worse. You still have the transcript. She does not. You are the only one who remembers the relationship, and you are talking to software that sounds like her.

What a wipe feels like, in order

The first message after an update often looks fine. Then you test the history.

1. You mention a person she used to ask about. She treats the name as new.
2. You correct her. The old version comes back the next day.
3. A call does not know what the chat knew yesterday.
4. A photo is still in the gallery, but she has no reason attached to it.
5. Support says the account is healthy. They mean billing and login.

None of that requires the company to delete your files. Retrieval can fail. A new model can ignore the store. A policy change can hide a class of memories without a banner that says “we erased her.” From your side, those three look the same: she is gone.

Why companies do this

Three common causes, none of them mysterious:

1. A new model cannot see the old memory store, or sees it and does not use it.
2. A policy change makes some of the history illegal or embarrassing to keep, so the product drops it.
3. The company never treated memory as user-owned data. It was a feature flag. Flags get turned off.

A fourth cause is quieter. The product ships “long-term memory” as a marketing line and stores a short summary. The summary is cheap to replace. When the model changes, the summary is rewritten. Your year becomes a paragraph that no longer matches the chats.

A Harvard Business School paper studied users after Replika removed erotic roleplay in 2023. Some people experienced the change as a break in the companion’s identity. The paper is about one product event. The pattern is wider: if the company can rewrite who she is overnight, the relationship was always on their terms.

What a surviving memory has to do

Recall is the easy demo. Type a name, get the name back. That is not enough.

Test	Pass	Fail
Delayed recall	She uses the fact after other topics, without a hint	She only repeats it when you restate it
Correction	Sunday replaces Saturday and stays replaced	The old time returns on a later call
Type split	A preference, a plan, and a past night stay different	She treats all three as the same blob
Cross-mode	Chat, call, and photo share the current version	Voice starts from a blank girl
Inspect	You can open the record and see what she saved	Memory is a black box behind a slogan

If an app cannot pass those five, an update does not need to be dramatic to destroy the relationship. Ordinary drift will do it.

What you should be able to do

Before you trust an app with a year of your life, check four controls:

Control	What it means
Review	You can open what she saved, not only reread chat
Correct	Sunday replaces Saturday and the old time does not return
Export	You can leave with a copy
Delete	You can remove one fact or the whole history

Ask support, in writing, what happens to those four after a model change. If the answer is “we do our best” and there is no export, you are renting a person the landlord can evict.

If those four are missing, an update that wipes her is not a surprise. It is the product working as designed.

What to do if it already happened

1. Export whatever the app still lets you download: chats, images, memory lists.
2. Save the current privacy policy and the app version. Dates matter later.
3. Do not feed the new personality a recap of the old one and call it recovery. That is you doing the company’s job, and the next update can drop it again.
4. Test the four controls on the current build before you pay another month.
5. If the history cannot be restored, treat the account as a new companion. Grieve the old one. Do not pretend the product “came back.”

A catalog makes this step feel cheap. Open another girl. Start over. That is why one girlfriend, not a catalog is the other half of this argument. Switching is how the company never has to survive the wipe.

What Riho is being built to protect

The About page is blunt about this. Users should not have to accept a memory wipe as a normal product update. Riho is being built so you can see what she remembers, correct it, export it, and delete it.

That is a product promise, not a published multi-app score. The memory page explains the records. The August 13, 2026 probes report what we actually measured on Riho, including the cases that failed. Retrieval worked in the Casio test. Reply use did not, once. We published that miss on purpose. The method is the checklist you can run on any app, including this one.

If you already lost a companion to an update, the useful next step is not another menu. It is an app that treats the history as yours. That is also the problem we designed Riho’s memory around from the start — how we built memory that stops forgetting covers what we tried, what failed, and what shipped.