Match the action to the outcome
| Your goal | Check | What a chat reply cannot establish |
|---|---|---|
| Correct a fact | Which visible field or instruction is changed? | That every stored version was rewritten |
| Stop a future callback | Is there a documented memory or behavior control? | That the old detail no longer exists anywhere |
| Remove account data | What official deletion process and scope are described? | That a server-side process completed |
| Move to another service | Can you export a usable format and import it there? | That a summary transfers the entire character |
Inspect a small entry before editing
Start with one fictional detail. Record where it appears and the control’s label. Read the official help page for that control and keep the original value locally if you may want to restore it. Avoid using a valued personal history as an experiment.
For example, Replika’s documented Memory flow describes viewing entries and removing an individual memory. That description does not establish that the same action deletes every record associated with an account. Interface labels may change; this documentation was checked on September 17, 2026.
Verify the right thing
After a correction, a later answer can show whether the new fact was used in that conversation. If the old fact is not mentioned, report exactly that. The system might still retain information it did not retrieve, so non-recall is not a deletion receipt.
For an account-level deletion request, use the provider’s official process. Read the stated scope, any retention exceptions and how completion is communicated. Save the request and response. This guide does not verify any provider’s backend deletion or promise a universal completion time.
Export for a purpose
Before switching apps, decide whether you need a readable archive, selected reference facts or a machine-readable import. These are different deliverables. Check both the source’s export function and the destination’s accepted format before relying on a migration.
A practical transfer brief can contain current preferences, established fictional events, canceled plans and unresolved story threads. Keep outdated details clearly marked. Share only what you want the new service to receive; a raw history may contain much more than the summary requires.
Use the local reference card deliberately
The reference-card tool does not save or upload what you type. Copying places it on your clipboard; pasting it into an external app shares it with that app. Reloading this page loses unsaved edits. Keep your own file if you need a lasting record.
Fonts and illustrations are packaged locally. Following a link to an external service opens a site with its own data practices.