What should my AI company do if a regulator or attorney general contacts us?
What regulators are asking AI companies about, the difference between letters, 6(b) orders, and civil investigative demands, the first steps to take, and how to have the answers ready before anyone asks.
Short answer
Take it seriously, note the deadline, preserve your records, and talk to a lawyer before anyone responds. Most inquiries can be narrowed and resolved, and a careful, accurate first response shapes everything after it. For AI companies, regulators are focused on a few recurring themes: children's safety, claims about what the AI can do, privacy and data use, and harmful outputs. A company that has already checked its product against those themes can answer quickly and with confidence.
What regulators are asking about
- Children and teens. In September 2025, the FTC ordered seven companies running AI companion chatbots to explain how they test for and limit harms to children and teens. In August 2025, 44 state attorneys general wrote to AI companies warning that they would be held accountable for harm to children, and followed up in December 2025 about harmful chatbot outputs.
- Accuracy and capability claims. In September 2024, the Texas attorney general settled with a health care AI company over allegedly inaccurate claims about its product's accuracy, imposing requirements on its future marketing. See What can I claim about my AI product in marketing?
- Privacy and data use. Training on user data, changing privacy terms, and sharing data with AI providers draw questions from the FTC and state privacy regulators. See Can I use my users' data for something new?
- New AI laws. As state AI laws take effect, attorneys general who enforce them will ask whether companies are meeting them.
What you might receive
- An informal letter or call. A request for information or a meeting, often after complaints or press coverage. It may not be legally binding, but it deserves the same care, since what you say can be used later.
- A 6(b) order from the FTC. A legally binding order to answer questions for an FTC study of an industry. It isn't an enforcement action, but the deadlines and the duty to answer are real.
- A civil investigative demand (CID). A legally binding demand for documents, written answers, or testimony in an investigation. For an FTC CID, a petition to narrow or set it aside generally has to be filed within 20 days of service or before the return date, whichever is sooner, so early contact with staff to negotiate scope matters. State attorneys general use similar demands under their own laws.
- A complaint or lawsuit. If it starts here, litigation deadlines apply.
The first steps
- Note the deadline and who sent it, and don't let it pass while you decide what to do.
- Preserve records. Issue a hold so relevant data isn't deleted, including logs, prompts, model versions, and messages, and pause automatic deletion where it would reach them.
- Talk to a lawyer before responding. Counsel can contact the agency, ask questions about scope, and often narrow the request and extend the deadline.
- Keep the investigation privileged. Have counsel direct the internal review, so the analysis of what happened stays confidential.
- Be accurate. Don't guess, overstate, or speculate in a response. Correct mistakes promptly if you find them.
- Keep statements consistent. Public statements, customer communications, and your response to the regulator should say the same thing.
- Check your insurance. Some policies require prompt notice of a regulatory inquiry.
Getting ready before anyone asks
Regulators tend to ask the same questions: what the product does, what you've claimed about it, what data it uses and where that data goes, how you protect children, how you test for harmful outputs, and how you handle complaints. Keeping current answers, with the testing and records behind them, means a response takes days instead of weeks.
Checklist an agent can run against the codebase
- List where the product's capabilities and accuracy are described: marketing pages, app store listings, and in-product text.
- Find age checks, teen settings, and safeguards for minors.
- Find testing and evaluation code for harmful or inaccurate outputs, and when it last ran.
- List every place user data is stored or sent, for comparison with the privacy policy.
- Check retention and automatic deletion for logs, prompts, and outputs, and whether they can be paused for a legal hold.
- Check that model versions and prompt changes are recorded with dates.
- Find where user complaints and safety reports are received and tracked.
Sources
- FTC Act, 15 U.S.C. 57b-1 (civil investigative demands)
- FTC Act, 15 U.S.C. 46 (FTC powers, including 6(b) orders)
If this applies to you
If you've already received a letter, order, or demand, contact counsel before responding, since deadlines are short. To be ready before anyone asks, an AI feature review checks the areas regulators focus on, including product claims, data flows, privacy documents, and safeguards, and leaves you with documents that match the product. For one question, such as whether a planned marketing claim is supported, a pre-build feature check covers it before launch.