Delete a Candy AI Account: Prepare Records and Ask About Retention
Review Candy.ai’s documented account-removal route, preserve necessary evidence and distinguish unavailable account content from legally retained records.
The help center documents account deletion under My Profile, Settings and the Danger Zone. Prepare necessary records before confirming. Account removal can make information permanently unavailable to you, while the Privacy Notice describes separate retention categories. A signed-out screen is not a backend erasure audit.
Prepare before deleting a Candy AI account: the account you remove must be the account you intend to lose. The documented route is My Profile, Settings, then Delete Account in the Danger Zone. Read the final consequence and any additional verification in your own session.
The help center describes permanent unavailability of account-associated information and notes legally required retention. We reviewed those documents, not internal storage systems. This is preparation guidance rather than a claim that we verified completed erasure.
Keep only the records you need
Before the final confirmation, decide whether you have an unresolved billing or support question. Save the relevant receipt, subscription acknowledgment or case reference privately. Avoid creating a large archive of sensitive material simply because you are leaving.
A useful preparation note has four entries: the account identifier, the outcome you want, the records needed afterward and any outstanding support question. It helps reveal when you have requested account deletion but still need a separate billing answer.
For example, a receipt in email and a screenshot in cloud storage are independent copies. Losing access to the service account does not tell you what happened to either file. Address those locations according to your actual retention or cleanup goal.
Verify the account on the confirmation screen
Open the documented settings from the service you use. If you have multiple identities or browser profiles, compare the account shown with your preparation note. Stop if it is wrong.
Read whether the screen describes account removal, a conversation action or subscription cancellation. Similar-looking confirmation buttons can have very different consequences. Do not use deletion as a harmless test of whether support can restore an account later.
Afterward, keep the acknowledgment and date if provided. If no result is clear, explain the exact action and message to official support. Do not submit passwords, authentication codes or unnecessary personal media as evidence.
Ask a category-specific retention question
The Privacy Notice, section 6, treats account, financial, marketing and legally required records differently. It should not be summarized as one universal deletion clock for every kind of information.
If a particular category matters, name it: “What happens to account identifiers and conversation content following my deletion request, and what financial records are retained under your policy?” Ask for the relevant policy basis and any remaining action you must take.
That question is more useful than asking whether “everything” vanished. An inability to sign in, an empty screen and a provider’s written response are different pieces of evidence. None independently shows every backend copy.
Finish the task you actually started
If your goal was only to stop renewal, use and verify the cancellation process instead of assuming deletion is the only route. If your goal includes local privacy, review your device and independently saved copies as well.
Keep a concise record of what you requested and what was confirmed. That preserves the information needed for a later question without retaining more personal content than necessary.
Sources and verification
This guide distinguishes published documentation from examples and observations. Feature access, policies and account screens can change; the linked source governs its own terms.