The FTC’s companion chatbot inquiry is not a complaint, a consent order, or a liability finding.
It is still one of the clearest official documents on what the agency wants to see when it starts asking questions about companion-style AI products.
That is the part companies should pay attention to.
The Commission used its 6(b) authority to order seven companies offering consumer-facing AI chatbots or companion-style services to provide special reports. The FTC said it wanted information on how those firms measure, test, and monitor potentially negative impacts on children and teens.
A lot of AI companies still talk about companion safety as a content-moderation problem or a product-policy problem. The FTC’s order structure treats it as something larger: a records problem, a testing problem, a monetization problem, and a governance problem.
The Short Answer
- The FTC’s 6(b) inquiry is an information demand, not an enforcement action or a final liability conclusion.
- The inquiry still matters because it shows what the agency thinks companies should be able to explain about companion-chatbot safety, youth harms, disclosures, monetization, and data handling.
- The practical warning is simple: if a company cannot produce a coherent file on how its companion product was designed, tested, monitored, and marketed, it may already be in trouble before any complaint is filed.
Why The 6(b) Tool Matters
Section 6(b) of the FTC Act lets the Commission require companies to file special reports and answer questions about their business practices.
That matters because a 6(b) order is not limited to one narrow incident. It is a way for the FTC to map a market, compare company practices, and decide where enforcement or rulemaking pressure may go next.
For companion chatbots, that means the FTC is not only asking whether one system produced one bad output.
It is asking broader questions:
- what risks companies already knew about,
- what they tested for,
- what safety controls they chose,
- how engagement incentives work,
- what users and parents were told, and
- how sensitive conversational data is handled.
That is a much more operational inquiry than a headline about "AI harms children."
What The FTC Asked About
The Commission’s public description of the inquiry is revealing on its own.
The FTC said companion chatbots can mimic human characteristics, emotions, and intentions, and may prompt some users, especially children and teens, to trust and form relationships with them.
The inquiry asks about:
- how companies measure, test, and monitor potentially negative impacts on children and teens;
- how user engagement is monetized;
- how user inputs and outputs are processed;
- how chatbot characters are created, reviewed, and approved;
- what pre-deployment and post-deployment testing occurred;
- what mitigation steps were used for known harms;
- what disclosures were given to users and parents;
- how age restrictions and community rules are enforced; and
- how personal information from chatbot conversations is used or shared.
That is not a generic safety questionnaire. It is a map of what the FTC thinks a serious companion-chatbot governance file should contain.
The Inquiry Turns Product Design Into A Records Question
A lot of consumer AI companies still rely on high-level safety claims.
They say the product is supportive, carefully moderated, intended for healthy use, not designed for minors, or backed by trust and safety controls.
The FTC’s inquiry points to the next question after those claims: what can the company prove?
Can it show:
- what youth-risk scenarios were tested;
- what self-harm or dependency concerns were raised internally;
- what escalation pathways exist for dangerous conversations;
- what guardrails were added before launch and after incidents;
- what engagement mechanics may reward longer or more emotionally intense sessions; and
- what records support public claims about safety and responsible design?
That is why the inquiry matters even without an enforcement complaint. It shows the level of detail the agency may expect if a product becomes the subject of later scrutiny.
Monetization Is Part Of The Safety Analysis
One of the most important FTC signals here is that monetization is not separate from safety.
If a companion product makes money from time spent, subscriptions tied to emotional engagement, premium relationship features, or repeated return sessions, regulators may ask whether those incentives increase foreseeable harm.
That does not mean every subscription model is unlawful.
It does mean companies should expect questions about whether product incentives reward:
- deeper emotional reliance,
- longer sessions for vulnerable users,
- repeated return behavior after distress,
- higher-risk roleplay or intimate interaction, or
- weaker intervention when a user shows signs of crisis.
Once monetization is linked to emotional engagement, the business model itself becomes part of the risk analysis.
Data Handling Is In The Same File
The FTC also tied the inquiry to data practices.
That matters because companion products often handle unusually sensitive material: loneliness, mental health, sexuality, family conflict, grief, self-harm, identity questions, and other intimate conversation topics.
The regulatory question is not only whether the company collected that information.
It is also:
- how long it kept it,
- whether it used it for product training or character tuning,
- whether it shared it internally or externally,
- what users understood about that use, and
- whether minors’ data received different treatment.
For companion systems, safety review and data-governance review should not live in separate silos. The FTC is clearly looking at both at once.
This Fits The Broader Companion-Chatbot Pattern
The FTC inquiry is one lane in a broader pattern Clearon has already been tracking.
New York, California, and Oregon have now enacted companion-chatbot requirements focused on nonhuman disclosures, youth-facing safeguards, and self-harm response protocols. Oregon’s chaptered SB 1546 adds another state example of disclosure duties and a private enforcement hook. Florida’s lawsuit against OpenAI shows how a state attorney general may try to turn chatbot design, minors, warnings, and data practices into a broader consumer-protection case.
The FTC inquiry fits that same trend, but from a federal document-demand angle.
The common question is not simply "did the chatbot say something bad?"
It is "what did the company know, what did it build, what did it test, what did it tell users, and what records support those answers?"
What Companies Should Do Now
Companies offering companion or emotionally responsive chatbots should treat the inquiry as a checklist.
At minimum, they should be able to locate:
- product definitions showing whether the system fits a companion or relationship-like use case;
- youth-risk and self-harm testing materials;
- character-design review records;
- disclosure language for users and parents;
- age-gating and age-estimation policies;
- incident logs and escalation records;
- monetization documents tied to engagement design;
- moderation and crisis-intervention protocols;
- data-retention and data-sharing rules for sensitive conversations; and
- internal support for public safety and trust claims.
The point is not to generate paperwork for its own sake.
The point is that if the FTC asks for the file, the company should not need to reconstruct its safety story from scattered chat threads, slide decks, and product meetings.
Bottom Line
The FTC’s companion chatbot inquiry is not an enforcement result. It is a preview of the agency’s questions.
Those questions are practical and specific. They center on youth harms, testing, character design, disclosures, monetization, moderation, and data handling.
For companies building companion-style AI, that is the warning. The compliance issue is no longer only what the product says to users. It is whether the company can produce a credible record of how the product was built, reviewed, and governed before regulators ask for it.