Map every place an AI companion can remember before you share
An AI companion memory feature can make conversations continuous, but it can also spread one detail across several stores and reuse paths. The practical response is to map every surface before sharing, keep only the smallest useful detail, secure the account, and test deletion at both the visible memory and its original sources. Controls differ by product and can change, so verify the current setting instead of assuming that deleting one chat, switching memory off, or disconnecting one app removes everything.
Start with a memory-surface map
Memory is not one box. Before sharing a personal detail, list five possible surfaces: an explicit saved-memory panel, ordinary chat history, uploaded files, profile or custom instructions, and connected apps. Add a sixth line for copies outside the service, such as notification previews, exports or screenshots. A companion may use one surface to personalize another, so deleting the visible conversation may not remove a separate summary or source. OpenAI’s current Memory FAQ explicitly distinguishes memory from chat history; Google separately describes Activity and connected services. Use each product’s current settings as the source of truth, not the word “delete” on one screen.
Separate collection from later reuse
For each surface, write what enters it, whether saving is automatic or requested, where the item is shown, and which future actions can call it back. A nickname used only in one chat has a different exposure path from a preference promoted into cross-chat memory. A connected calendar, photo library or mailbox creates another route: the assistant may retrieve a detail again even after you edit its summary. This is why the useful question is not only “does the app remember?” but “what source can supply the detail, for which purpose, and under which account setting?” NIST’s generative-AI profile highlights transparency, participation and purpose specification as privacy concerns.
Watch for inference, drift and combination
A memory can be risky even when every saved fragment looks harmless. Several ordinary details—regular location, work schedule, preferred shop and upcoming trip—can combine into a much more specific picture. Summaries may also become stale or merge two periods incorrectly, causing the companion to repeat an outdated preference in a later conversation. Review the memory panel and ask the product what it uses, but do not assume the summary lists every contributing source. Correct inaccurate items promptly. For details that are useful only once, choose a temporary or memory-free mode when the product actually offers one, and verify what that mode excludes before relying on it.
Protect the account and the nearby screen
The most sophisticated deletion control cannot help if another person can open the account. Use a unique password, available multi-factor authentication, a device screen lock, and a recovery email or phone you still control. Review active sessions and connected devices after borrowing, repair or resale. On a shared phone, tablet or computer, sign out and avoid browser profiles that synchronize history to someone else. Reduce notification previews if they reveal names, places or remembered prompts on the lock screen. Do not paste a full memory list into a public support thread; provide only the minimum fields the verified support channel needs.
Run a two-pass deletion test
First remove the remembered item through the documented memory control, then start a new conversation and check whether it is still referenced. Second, trace the item back to its sources: old and archived chats, files, profile instructions, connected apps, shared links and exports. Delete or disconnect only the sources you intend to remove, then check again after the product’s stated processing period. OpenAI notes that full removal may require deleting every place where the information appears. Google also warns that deleting activity in one service may not delete data in another. Record the date, control used and result instead of assuming that switching memory off erased existing data.
Choose the smallest useful memory boundary
Keep only details that create a clear everyday benefit and are easy to revise: a preferred writing tone, a recurring fictional character or a broad hobby may need less precision than an address, identifier or private document. Avoid adding another person’s information without their permission. Revisit the map after enabling a new integration, importing old chats, changing plans or accepting revised terms. If controls are unclear, use the assistant without persistent memory until you can verify them. The goal is not to fear personalization; it is to make continuity deliberate, visible and reversible. A short quarterly review of sources, sessions and deletion paths is more useful than trusting an old setup forever.
Common questions
Does deleting a chat always delete its memory?
No. Some products store memory separately, so check and remove both the remembered item and its source conversation where required.
Is turning memory off the same as erasing it?
Not necessarily. A switch may stop future use or creation without deleting existing items; verify the current product wording.
Can connected apps recreate a deleted detail?
They may supply the detail again if the connection and source data remain available, so include integrations in the deletion map.