AI Companion Data Export and Deletion Questions
Data controls deserve precise language. Download, export, clear history, close account, and request deletion may refer to different actions. This guide does not promise a particular legal right or result. It gives you questions to ask from the service's current privacy notice, account tools, and support process so you can understand scope before submitting a request.
Fast evidence screen
| Area | Useful current evidence | Reason to pause |
|---|---|---|
| Access scope | The export description names included categories and format | Download is advertised without explaining contents |
| Request identity check | The provider explains how it verifies control of the account | Support asks for excessive sensitive documents without explanation |
| Deletion scope | The response distinguishes account, content, records, and stated exceptions | A closed login is treated as proof of every backend result |
| Completion record | A dated response describes what action was completed | The ticket closes with no scope or outcome |
Build a data inventory
Question: Which account areas may contain information you want to access or remove?
Action: List profile fields, conversations, uploads, generated media, billing metadata, support messages, and connected accounts separately. This action reduces guesswork; it does not prove anything beyond the current source and account state you actually observed.
Evidence: Your own category list based on the current product interface and privacy notice. Keep the access date and enough context to understand the wording later.
Worked example: A conversation export may not include billing or support records, so ask about them as distinct categories.
Pause when: The provider cannot say which categories its export or request process covers. A pause is a useful result when proceeding would require an assumption.
Read the current request route
Question: Is there an account tool, form, email, or support workflow?
Action: Use the route named in the live privacy notice or account settings and verify the destination belongs to the provider. This action reduces guesswork; it does not prove anything beyond the current source and account state you actually observed.
Evidence: A dated copy of the request instructions and the submitted ticket number. Keep the access date and enough context to understand the wording later.
Worked example: An old help article may point to a retired form; cross-check the current privacy notice.
Pause when: A third party asks you to send credentials or payment secrets to process the request. A pause is a useful result when proceeding would require an assumption.
Ask about export usability
Question: What format, date range, categories, and delivery method are currently described?
Action: Request the scope before download and prepare a private location for any resulting archive. This action reduces guesswork; it does not prove anything beyond the current source and account state you actually observed.
Evidence: The provider's response and a file inventory without opening sensitive content unnecessarily. Keep the access date and enough context to understand the wording later.
Worked example: A machine-readable archive and a visual transcript may serve different purposes; ask what is actually provided.
Pause when: The download arrives through an unexpected host or requires disabling normal security warnings. A pause is a useful result when proceeding would require an assumption.
Define deletion precisely
Question: Are you requesting removal of a thread, upload, profile, account, or all covered personal data?
Action: Name each category, ask what action applies, and request an explanation of any stated retention or exceptions. This action reduces guesswork; it does not prove anything beyond the current source and account state you actually observed.
Evidence: The original request, identity-verification steps, provider response, and completion date. Keep the access date and enough context to understand the wording later.
Worked example: Closing the account may prevent login while a separate request concerns stored content; ask how the provider distinguishes them.
Pause when: The response uses vague final language but will not state scope, timing, or any exceptions. A pause is a useful result when proceeding would require an assumption.
Handle local copies
Question: What new copies will an export or confirmation create?
Action: Store downloads in a controlled location, remove unneeded copies, and check downloads, backups, and shared cloud folders. This action reduces guesswork; it does not prove anything beyond the current source and account state you actually observed.
Evidence: A local file checklist that records location and disposal without recording content. Keep the access date and enough context to understand the wording later.
Worked example: An archive deleted from Downloads may still exist in a backup or synchronized trash folder.
Pause when: You cannot control where the export is saved or who has access to that location. A pause is a useful result when proceeding would require an assumption.
Copyable checklist
Complete each line from the provider's current interface or published documents. A blank or unclear answer should remain visible in your notes.
- List profile, conversation, upload, billing, support, and connection data separately.
- Use the request route named in the current policy or account page.
- Ask what categories and date range an export includes.
- Prepare a private location before downloading an archive.
- Define whether you mean thread removal, account closure, or a broader request.
- Ask the provider to explain stated retention or exceptions.
- Keep request and completion records without exposing their contents.
- Remove unnecessary local and synchronized copies after use.
Worked situations
Export before account closure
If you want a copy, check whether closing the account could remove access to the export tool. Ask the provider about the current order of operations. Download only to a location you control and remember that the archive creates a new privacy responsibility.
Record what the current source shows, keep personal details out of the worksheet, and mark unresolved questions rather than filling them with an assumption.
Vague completion message
A message saying a request is complete may not identify categories. Reply with the original numbered questions and ask which actions were performed, which data was outside scope, and what current policy says about any remaining records or exceptions.
Record what the current source shows, keep personal details out of the worksheet, and mark unresolved questions rather than filling them with an assumption.
How to record a reliable answer
Use a dated worksheet with four columns: the question, the current source, the exact answer, and what remains unknown. Prefer a live detailed policy or account control over a promotional summary. Preserve enough surrounding wording to avoid changing the meaning, but cover names, addresses, payment values, conversation text, and other personal details. A screenshot records one interface at one moment; it is not proof that the same rule applies later, in another region, or to another account.
When two sources disagree, do not choose the answer you prefer. Record the conflict and ask the provider through a contact route reached from its current account, terms, or privacy page. Keep the case number and exact response. If the answer affects payment, an upload, account access, or sensitive disclosure, wait until the conflict is resolved or choose not to proceed. Unknown is a valid worksheet result.
A calm stop rule
Pause when a required term is missing, the final confirmation differs from the earlier page, a request moves outside the documented account route, or support asks for secrets that normal support should not need. Do not send passwords, one-time codes, full payment credentials, recovery secrets, or unrelated private conversation content. Do not install unknown software or grant remote control. Return through a known official address and verify the account state independently.
Related safety checklists
Frequently asked questions
Does this guide guarantee deletion?
No. It helps you ask about current scope, process, timing, and exceptions. Only the provider can answer for its systems, and its policy or interface may change.
Should I send identity documents to support?
First verify the official request route and ask why each item is needed. Cover information not required by the stated verification process, and never send passwords, recovery codes, or full payment credentials.
Is an export safe to keep?
An export can contain concentrated sensitive information. Store it only where you control access, consider local backup behavior, and remove copies you no longer need.
What if the policy and support answer differ?
Preserve both dated sources and ask the provider to resolve the conflict in writing. Do not infer the more favorable answer is correct.