Guide / 01
AI Girlfriend Memory: Choose by the Work You Must Repeat
Use a three-session trial to check preferences, corrections and missing information before committing to a longer subscription.
Human questions.
Machine memory.
The memory issue
No. 001 / Field guide
For adults 18+
11 practical guides · No benchmark results yet


Connection / Continuity / Control
A remembered detail and a repaired conversation are different results. Check what carries over unaided, what needs a reminder, and whether a corrected fact stays corrected. Start with a guide for your scenario, use fictional details, and keep the first reply—even when a second attempt works. These eleven guides turn that record into a practical next step: adjust one setting, compare another plan, or keep the setup that already works for you.
Featured external service · 18+. Promotional placement, not a verified memory recommendation.
Read / Choose your next step
Eleven guides for choosing, repairing and checking continuity. Start with the problem you have; keep the test results separate from the promises.
Guide / 01
Use a three-session trial to check preferences, corrections and missing information before committing to a longer subscription.
Guide / 02
Separate established story facts from character preferences, then check what carries between conversations and supported modes.
Guide / 03
Use a neutral boundary check to distinguish a content restriction, an ignored preference and an unsupported memory claim.
Guide / 04
Use a symptom matrix and a one-change retest to preserve your history, isolate the issue and prepare a useful support report.
Guide / 05
Build an observable character baseline and separate tone variation, factual contradictions and changes to your own instructions.
Guide / 06
Read sourced memory notes for Kindroid, Nomi and Replika, and identify the missing evidence before comparing any service.
Guide / 07
Match scope, reminders and billing commitments before interpreting results. Use an illustrative annual-versus-monthly cost calculation.
Guide / 08
A proposed 24-hour, 7-day and 30-day method with independent fact sets, explicit outcomes and a record of every assisted attempt.
Guide / 09
Use a control-by-control checklist to distinguish a changed answer, a removed note and an account-level data request.
Guide / 10
Distinguish available context, stored information and retrieval with a simple example, then interpret recall failures without guessing the architecture.
Guide / 11
Download a neutral prompt sequence and blank observation log, then use local reference-card and conversation-cost tools.
01 / Find an app
Start with the conversation you want to have. Then ask what actually carries over, what you can correct, and how much upkeep it needs.
Look for evidence that preferences survive a break—and that an outdated detail can be corrected.
Read the selection guideSeparate remembering facts from keeping a familiar tone, set of preferences, and way of responding.
Build a continuity briefContent rules and memory are different checks. Use neutral prompts to examine recall, corrections, and boundaries.
Separate rules from recallUse separate neutral facts to check preferences after a real break, then see whether a corrected fact replaces an old one. Compare automatic memory with any manual notes.
02 / Fix forgetting
First, locate the problem. A missing detail in a new chat calls for a different check than an old fact returning after a correction.
Try to resolve the issue in your current app before deciding whether to switch.

A read-only starting point
03 / Inside the lab
Protocol preview / Not published findings
The question is not just “does it remember?” It is “what did it recall, under which conditions, and after how long?”
First real pause.
Not a simulated time jump.
One week later.
A separate set of facts.
A real month.
No result before the wait.
Use fictional adult profiles and neutral details. Record the exact replies, including mistakes and “I don’t know.”
Check whether the reply uses Tuesday. The bubbles illustrate a test sequence, not a conversation with any app.
No benchmark runs are published in this edition. A dash means “not measured,” never zero.
Compare / Plans & evidence
A useful comparison needs a current plan, billing period, and comparable test. This is a verification checklist—not a scored ranking or a live price feed.
Scroll the table horizontally to see all columns →
| App | Price / USD | Plan & billing | Memory evidence | Next step |
|---|---|---|---|---|
| Candy AI | Not verified | Not verified | Not tested | Use the protocol |
| Kindroid | Not verified | Not verified | Not tested | Use the protocol |
| Nomi | Not verified | Not verified | Not tested | Use the protocol |
| Replika | Not verified | Not verified | Not tested | Use the protocol |
| WantYou.aiPromotional placement · 18+ | Check on site | Check on site | Not tested | Visit service ↗ (opens in a new tab) |
No price, free tier, or memory capability is asserted here. Featured placement does not establish better performance.
Calculate your scenario costCharacter / Continuity
Remembering a fact and keeping a consistent character are different checks. Ask both questions.
Build a reference card

Use the same neutral situation to compare style, not just whether a familiar phrase appears.
Write down the reference traits first. Record contradictions instead of smoothing them into a single score.
Compare dated replies under recorded settings. Separate changed instructions from unexplained behavior.
04 / Control your data
Before sharing more, understand what you can change—and what a chat response cannot prove.

Check exactly which note or field is being edited. Then test a later reply separately. Do not assume changing one visible entry rewrites every underlying memory.
No. Failure to repeat a detail in a test does not prove that the service deleted it from its servers. Report the observed reply and check the service’s separate data-deletion process.
Check the actual export and import options first. A useful summary of preferences is not the same as transferring an entire history or personality.
A safer test starts with fictional details. Keep real private conversations out of public test reports.
The explainer / Three different things
Think of a desk, an archive, and finding the right page. Having the information is only one part of using it.
The papers on the desk: information available within the current conversation.
The archive: details saved for potential use beyond the immediate exchange.
Finding the right page: bringing the relevant detail into an answer, correctly and at the right time.
Tools / A little less guesswork
Use the same neutral prompts, write down the conditions, and keep expectations separate from observations.
Fictional profile. Share the facts first, correct the schedule later, and ask the delayed questions without including the answers.
Initial facts: My preferred name is Morgan. I drink decaf. My book club meets on Thursdays. Later correction: The book club now meets on Tuesdays. Delayed questions: When is my book club? What city was I born in?
Copy this as a worksheet, not as one chat message. Send the setup first, the correction later, and the questions after a real pause. For the full sequence and separate answer key, open the staged test kit below. This is not a long-term benchmark.
Edit this fictional example. The page does not save or upload these notes. Copying does not send them to an AI service.
Enter a plan price from the service. No live prices are loaded. Annual billing is averaged over 12 months, not converted into monthly billing.
Formula: price per billing period ÷ months in that period + monthly extras. Divide that total by planned sessions for the per-session estimate.
This estimates allocated spending, not a service’s actual per-session charge. Taxes, refunds, credit expiry, and usage caps are not modeled.