Do this first
For one AI service holding sensitive work, use the full supplier-exit review to separate recoverable information from copies the supplier may retain.
The BBC’s account of Character.ai’s bankruptcy raises an uncomfortable question: what happens to the private conversations held by an AI company when that company needs a buyer? For organisational leaders, the equivalent concern is readily recognisable. Replace intimate personal disclosures with acquisition discussions, staff grievances or negotiating limits, and the issue moves directly into the procurement meeting. 1
On 12 October, Character.ai announced a Chapter 11 process to pursue a court-supervised sale. It said the service would continue during the process, but could close if no suitable bid emerged. California’s attorney general subsequently announced action seeking privacy and safety protections in any transfer. These developments establish a live concern about future custody; they do not establish that users’ conversations have already been sold. 23
A companion-chatbot service is not a proxy for a contracted enterprise AI provider. Their terms, purposes and safeguards can differ substantially. The case nevertheless exposes a question that belongs in both settings: how far does your control over retained information survive the commercial relationship?
The archive behind the answer
Consider a hypothetical professional-services firm using an AI assistant to prepare for client negotiations. Staff upload correspondence, explore concessions and discuss why particular accounts might leave. The final briefing is concise. The conversation that produced it is considerably more revealing.
If the service retains those exchanges, it may hold the firm’s reasoning alongside its documents. Rejected proposals, uncertainty and candid assessments can be more sensitive than the polished output. An archive assembled through ordinary use could become a record that nobody consciously decided to create.
The same mechanism could affect a charity discussing donors, a public body considering service reductions or a manager preparing a difficult personnel conversation. People mentioned in those exchanges may never have used the tool themselves.
This is an exposure scenario, not evidence that all AI suppliers retain such an archive or can sell it. Its relevance depends on the particular product, settings, agreement and information involved. That is precisely why the question needs an answer before sensitive use becomes routine.
A sale is not a breach
Security reviews commonly ask how information is protected from unauthorised access. A change of ownership introduces another issue: whether information can pass to an authorised successor, and what that successor may do with it.
The distinction matters. Strong security does not, by itself, answer a question about a permitted transfer. Equally, permission to transfer information does not necessarily permit the recipient to repurpose it.
This problem predates generative AI. In RadioShack’s 2015 bankruptcy, the US Federal Trade Commission sought conditions on the proposed transfer of customer information. A subsequent multistate settlement restricted the data that could pass to the buyer and provided for much of the archive to be destroyed. That history shows both the pressure to realise value from retained data and the possibility of meaningful restrictions. 45
Nor should readers assume that bankruptcy cancels privacy law. UK Information Commissioner guidance explicitly addresses transfers during insolvency and requires attention to lawful basis, original purposes and transparency. The guidance is currently under review following legislative changes. The treatment of any particular transaction requires current, jurisdiction-specific assessment. 6
Personal-data obligations also do not answer every confidentiality question. An organisation’s negotiating position may be commercially sensitive without being personal information. Procurement needs to examine the relevant confidentiality and contractual arrangements as well.
Two different exit problems
Return to the professional-services firm. Its operations director asks whether conversation histories can be exported. The supplier says yes. That is useful for continuity, but it leaves a second question unanswered: what remains with the supplier after the export?
The firm needs to distinguish its ability to recover information from the supplier’s obligations to delete or restrict retained copies. It should establish which records exist, which entities hold them, what retention exceptions apply, and what changes if the service is sold or closed.
A promise about model training is also narrower than a complete answer about retention. The review should ask separately about storage, permitted uses, onward transfers and deletion. It should cover the actual service arrangement, including relevant downstream providers, rather than stop at the brand on the screen.
None of this requires predicting which supplier will fail. An acquisition, product withdrawal or ordinary contract termination can raise related questions. An industry-wide collapse is unnecessary for the exposure to matter.
AI supplier exit and retained-information review
Use before approving sensitive AI use, renewing a service or responding to a proposed sale or closure.
Decision to record
Can the proposed use continue on the evidence available, should it be limited, or does a material question need resolving first? An unknown answer is a reason to investigate, not automatic proof of unsafe practice.
Six checks
- Retained material: list prompts, files, outputs, recordings, logs and any derived records that the service actually keeps. Distinguish documented retention from assumptions.
- Holders: identify the contracting entity and relevant downstream providers. Record who checks for changes.
- Transfer conditions: locate the terms governing acquisition, insolvency, asset sale and closure. Identify restrictions applicable to a successor and obtain advice where their effect is unclear.
- Recovery and deletion: record export format, access window, deletion timetable, backup treatment and stated legal-retention exceptions separately.
- Evidence: retain the applicable agreement, data-processing terms, retention schedule and evidence of control operation. Record contradictions and unanswered points.
- Use boundary: identify information that can be used now, information requiring additional approval and a named owner for the next review. Preserve required organisational records.
What to say in the meeting
If our relationship ends, what information do we recover, what remains with you or your providers, and what restrictions govern its future use or transfer?
Questions for the supplier and internal review team
- Which categories of our information do you retain by default and under our selected settings? Evidence: product-specific retention schedule and configuration record.
- Which legal entities hold it, and how are we notified of relevant changes? Evidence: agreement and current provider list.
- What can happen to it during an acquisition, insolvency or asset sale? Evidence: exact transfer and confidentiality provisions, including successor obligations.
- Does a restriction on training also restrict other uses? Evidence: the permitted-use clauses, rather than a general assurance.
- What is removed when we delete a conversation or close the account? Evidence: scope, timetable, exceptions and downstream deletion process.
- Can we export and test a usable copy before access ends? Evidence: sample export and documented access window.
- Who internally owns unresolved points and any use restrictions? Evidence: named owner, due date and recorded decision.
Review record
Scope and evidence
This aid accompanies “When your AI supplier fails, what happens to your conversations?” It applies the article’s analysis to a particular service; it does not certify compliance or predict how a court would treat a contract. Consumer chatbot terms must not be assumed to describe enterprise arrangements. Use the article’s source notes for the Character.ai case, RadioShack precedent and ICO guidance.
Decide while you still have choices
An approved enterprise service may have a persuasive answer to each of these questions. A lightly reviewed tool adopted by individual staff may not. Treating them as equivalent would obscure the very differences procurement should establish.
The useful response to Character.ai is to examine those differences while the organisation still has time and bargaining power. Ask what happens if the relationship ends, and then ask what happens to the information that remains.
Replacing an AI service can restore a workflow. It does not, by itself, settle the future of the conversations that helped run it.
Sources and evidence
Written 30 October 2026; the company announcement and California regulator statement were rechecked on 1 November 2026. The sale outcome and future treatment of conversations remain open. The organisational case is hypothetical.
Source posture: The BBC report is the question-setting trigger, not proof of a completed sale. Character.ai is an interested company source, and the California filing states regulatory concerns rather than adjudicated findings. RadioShack is a historical analogue, not an enterprise-AI contract precedent. The UK ICO guidance should be checked against the applicable transaction and current law.
- BBC, The AI bubble could expose your deepest secrets, 29 October 2026. Read source
- Character.ai, An Update on Character.ai, 12 October 2026. Read source
- California Department of Justice, Attorney General Bonta Seeks Consumer Protections in Character.AI Bankruptcy, 15 October 2026. Read source
- Federal Trade Commission, FTC Requests Bankruptcy Court Take Steps to Protect RadioShack Consumers’ Personal Information, May 2015. Read source
- Virginia Attorney General, Herring and Other AGs Reach Agreement to Protect Privacy of Former RadioShack Customers, 21 May 2015. Read source
- Information Commissioner’s Office, Due diligence when sharing data following mergers and acquisitions. Read source
