Delete AI Chat Data: Keep, Remove, Confirm

Choose the outcome before the button

• Remove one conversation: identify the chat and ask whether related memory or media needs a separate step.
• Reset personalization: inspect memory and profile controls before deleting an account you want to keep.
• Leave the service: review export, billing and account closure as separate tasks.

An exit sequence with checkpoints

1. Check the export. If available, download it through the official channel and open it before closing the account. Check a representative conversation and expected attachments. An unreadable archive or a missing date range is not a completed export.
2. Protect the copy you keep. Choose a private storage location. An export creates another copy; do not upload it to a public converter or an unrelated chatbot merely to inspect it.
3. Check billing separately. Identify whether you pay through the provider or an app store, then use that channel’s current cancellation instructions. Save the confirmation. Do not infer cancellation from uninstalling an app or removing a chat.
4. Define removal scope. List history, memory, media and account data. Ask separately about logs, backups, processors and archives.
5. Use the documented route. Open the provider’s own settings or verified privacy contact. Keep a request identifier and submission date.
6. Read the outcome. Record each category confirmed removed, each retained category and the explanation. Note the date or event from which a stated period runs.

Two policies, two different clocks

Nomi’s policy, sections 4 and 6, describes account deletion taking approximately 28 days after confirmation, while separately addressing training and communications archives and legal exceptions. Do not translate this into a promise that every record disappears on day 28.

CHAI’s privacy notice describes processing during the account lifetime and for up to five years after deletion, with specified reasons for longer retention. Its deletion clause refers to retention obligations. These examples demonstrate why a visible deletion control and a retention schedule must be read together; they are not a ranking.

If the confirmation is vague

Reply with the request reference rather than resending your chats: “Please distinguish account closure from removal of history, personalization records and media. For retained categories, identify the reason, timeframe and starting event. Please confirm whether any further action is needed from me.” Use the request builder to prepare a draft.

If the stated period passes without a clear answer, preserve the correspondence and use the provider’s escalation channel. Applicable legal rights depend on your location and the business; do not invent a universal deadline. The California Attorney General’s CCPA guide explains California-specific rights and exceptions.

A removed login, an empty history screen or a bot saying “I forgot” is not proof that every server-side copy has been erased. Keep the provider’s exact scope of confirmation in your log.

Make it practical

Keep your own record

Download the blank worksheet and fill it in privately. No account or upload is needed; nothing you write in the downloaded file is sent to this site.

Download worksheet · CSV

Scope: editorial guidance and official documentation checked on September 18, 2026. No in-app deletion tests or infrastructure audit were performed. Illustrative scenarios are fictional. Evidence method · Website privacy