Read it.
The memory list is a screen in the app, not a promise in a changelog. Entries are extracted automatically as you chat and land where you can see them — what got remembered, line by line.
Companion · long-term memory
"Remembers" has two layers: what got remembered, and where that memory lives. Most companion apps show you neither. A Foreverse companion keeps long-term memory as files on your phone — open the list, read every entry, fix the wrong ones, delete what shouldn't stay. Anniversaries, journals, and the relationship archive work the same way.
Memory sovereignty
Four operations, all in your hands: read every entry the companion holds, edit entries that are wrong, delete entries that shouldn't exist, and export the whole companion when you change phones. The app supports all four; here is each one up close.
The memory list is a screen in the app, not a promise in a changelog. Entries are extracted automatically as you chat and land where you can see them — what got remembered, line by line.
Extraction gets things wrong sometimes; people misspeak too. Wrong entries edit in place, and entries that shouldn't exist delete for good. Deleting the companion deletes the memory with it.
Companion data exports as one portable package: persona, memory, journals, anniversaries, the relationship archive. Import it on the new phone and the relationship continues. No account holds it hostage.
Why others forget
Two reasons, and neither is malice: memory kept server-side where you can't inspect or correct it, and context windows that only fit a slice of history per reply. Both have engineering answers — but only if the app lets you watch the system work.
Most platforms store companion memory server-side, unopenable. You can't see what got saved, so you can't fix what got saved wrong. You find out three weeks later, when it calls your sister by your cat's name.
A model reads a finite slice of history per reply. Whatever fell off the edge might as well never have happened, unless a memory system catches it — and most apps won't show you whether theirs did.
Structured entries extracted from chat, stored as files, always visible. On very long relationships, older conversation gets condensed into summaries so the model can still reach far back; the structured entries stay untouched. Engineering, not magic — and you can check the work.
FAQ
Remembering is also what makes a first message possible — a companion opens the conversation because Thursday is the interview you mentioned, not because a timer fired. That behavior has its own page: an AI that texts you first.
In files on your phone, not on our servers. The app has a memory screen that lists every entry, and each one can be read, edited, or deleted there. Anniversaries, journals, and the relationship archive live on the device the same way. Deleting the companion deletes all of it.
Sometimes, yes. Automatic extraction mishears and over-generalizes the way models do, which is exactly why the list is editable: fix the entry in place or delete it, and the correction holds from the next conversation on. We would rather hand you the edit button than pretend extraction never misses.
Yes. Companion data exports as one portable package — persona, memory, journals, anniversaries, the archive — and imports on the new device. The relationship picks up where it left off. None of it is tied to one phone or held behind a platform account.
Mostly in where the data sits and what you pay for. Subscription companions keep memory on their servers; stop paying and that history is out of reach. Here the app is free, companion data lives on your device, and AI calls run on your own provider keys (62 providers) or an official metered channel. You pay for usage, never for access to your own history.
Now on Google Play · iOS beta
Install on Android, create a companion, and watch the memory list fill as you talk. iOS is in beta — leave an email and we send one short note when the next wave opens. Or write to [email protected] about the companion you have in mind.