AI companions can feel more personal than ordinary software because conversations may continue over weeks or months. That makes privacy settings worth checking before you share much about yourself.
Start with memory
Look for controls that explain whether the app stores long-term memories separately from chat history. A useful product should let you view, edit or remove remembered information rather than treating memory as invisible. Understand chat retention.
Deleting a conversation may not always mean every derived memory or uploaded file disappears. Read the deletion options carefully and use account-level deletion when you want a broader reset.
Check uploaded photos and media
If the companion supports images, voice or video, review how uploads are stored and whether generated media remains linked to your account. Look for training controls.
Some services provide settings related to model improvement or data use. The exact wording varies, so check the current privacy documentation rather than assuming one industry-wide default.
Control proactive notifications
Companion apps often send relationship-style notifications. Make sure you can reduce or disable them if they become distracting. Our guide to AI companion notifications explains what to look for. Review subscription data separately.
Privacy and billing are different systems. Cancelling a subscription does not necessarily delete the account, and deleting an account may have separate billing steps depending on the store.
Use a layered sharing approach
You do not need to provide every personal detail for a companion to be useful. Start with low-sensitivity preferences and expand only when the product earns your trust. Check account deletion before you need it.
A good time to understand deletion is before you have months of history. See our account deletion checklist for chats, memories and media.
Privacy is part of product quality
An AI companion can be warm and personalized while still giving users control. Clear settings make it easier to enjoy continuity without feeling that the system is collecting more than you intended. Understand what is stored versus what is inferred.
Some products retain explicit user inputs, while others also create summaries, embeddings or preference profiles. User-facing controls should make the important consequences understandable even if the implementation details stay hidden. A practical question is simple: after deleting or correcting a detail, does future personalization stop using it?
Review third-party and creator access separately
For creator-backed AI, users should know whether the human creator or management team can see private conversations. That access model should be explicit rather than implied by the creator’s public identity. Check privacy where the data is actually exposed.
Privacy is not only a policy-page question. Test lock-screen notifications, shared-device behavior, account switching, export files and deletion controls. A product can have a reasonable privacy statement while still exposing sensitive context through previews or leaving old data available on another device. Users should be able to understand which permissions are required for the core experience and which are optional enhancements.
Verify deletion end to end
Deleting a conversation, a memory, an uploaded asset and an account may be different operations. The interface should explain the scope of each action and prevent removed information from reappearing through summaries, caches or synchronization. For sensitive media such as faces or voices, it is especially important to know whether the source file, derived model and generated history are managed separately.
Use the smallest permission that still delivers the feature. Location, contacts, photos and microphone access can each improve an AI experience, but they should not become default requirements when a narrower permission would work. Review whether the app offers limited photo selection, approximate location or one-time access where appropriate.
The product should also keep working in a reasonable fallback mode when an optional permission is denied.
Check synchronization and revocation
If privacy settings are changed on one device, verify that the new choice reaches other signed-in devices. A revoked permission or deleted memory should not remain active because another client is using stale state. A final long-term check.
Repeat the same test after several days and after changing one setting. AI products accumulate memory, synchronization state and billing or permission history, so problems may appear only after the first-session novelty has passed. The strongest products remain understandable as history grows: users can see what changed, correct the relevant state and continue without rebuilding the entire relationship.