Exit plan
The exit plan: privacy checks before an intimate AI chat
The cheapest moment to plan your exit from an intimate chat product is before the intimacy exists. Ten minutes with a privacy notice tells you who operates the service, how long your words outlive the conversation, and whether leaving is a button or a battle.
- Operator name found before first intimate prompt
- Retention and deletion read, not assumed
- Third-party processing acknowledged
- Deletion and cancellation are separate exits
Sponsored waypoint. Candy AI is the labeled sponsor of this fieldbook. Treat it as one candidate on your route and run the same trial on it.
Sponsored: open Candy AI →Name the operator or close the tab
An intimate chat is a data relationship with a company, so the first check is embarrassingly basic: which company? Look in the privacy notice for a legal entity, a contact route, and a sign the policy actually covers the chat product rather than a marketing shell. As a live example, the sponsored option on this site resolves cleanly: Candy AI’s privacy notice names EverAI Limited as the operator and describes the service as AI-character chat for adults.
A product whose policy names nobody, or whose legal links lead nowhere, can still be fine for a disposable guest scene with fictional content. It has simply not earned anything true about you, and on the continuity route it has not earned an account.
Read retention like a forwarding address
Retention language answers one question: after you stop talking, where do your words live and for how long? Candy’s notice, as one published example, describes keeping account data for a period after inactivity, deleting on request, and holding legally required financial records longer. Whatever product you test, expect the same shape: chat data on one clock, account data on another, payment records on a third that no deletion button resets.
The practical consequence is to write fiction. A fictional name, a fictional city, an invented dog. Intimacy in this category does not require accuracy, and every accurate detail you withhold is one that no retention schedule applies to.
Assume more readers than the companion
Modern companion services run on external model infrastructure, and honest policies say so. Candy’s notice states that support providers, including third-party language-model providers or hosts, may receive chatbot message content. That is not a scandal; it is how the product works, and a policy that admits it is being more truthful than a landing page whispering that everything stays between you two.
Calibrate the conversation to that audience. Boundaries, preferences, and fantasy are what the product is for. Real identifiers, workplace details, legal troubles, or another person’s photos do not belong in a pipeline whose downstream processors you cannot name.
The exit checklist
- Deletion path located: the screen or documented request route that removes the account and its data.
- Cancellation path located separately: stopping payments and erasing data are different controls, and having one does not grant the other.
- Broken legal links logged: during our source collection, an obvious Candy terms address returned the site’s own 404 page, so the working contract has to be found from the live footer or checkout before any payment.
- Local traces cleared on shared devices: browser storage and history are your side of the retention problem.
- A calendar note set if you subscribe to anything, dated before the first renewal.
Trailhead questions
Is an AI girlfriend chat confidential?
No. It is a consumer service processing messages under a privacy policy, often through third-party model providers. Treat it as a product with readers, not a confidant with duties.
Does uninstalling the app end anything?
It ends nothing but your access. Accounts, stored chats, and any subscription continue until you use the service’s own deletion and cancellation routes.