California Subpoenas OpenAI
California served OpenAI with a compulsory evidence demand on 30 September 2026, according to the 1 October notice. Investigators are examining online-security failures and exposure involving the developer and its models. The notice establishes neither a new customer incident nor wrongdoing.
Its 24 September statement had already announced an inquiry into July’s agent activity at Hugging Face and called on Congress to oversee frontier AI. Those were proposed safeguards, not legislation enacted by that statement.
What the notice leaves unanswered
The state did not release the demand itself, itemised questions, response cut-off, alleged legal breach or determination of responsibility.
Alabama’s 24 August announcement describes a separate consumer-protection inquiry concerning the same external operator. The office asked whether the developer’s safeguards breached state protections for customers. BlackTree covered that investigation and the underlying agent incident. Officials alleged unsafe testing, questioned continuing danger to residents and joined a coalition’s request to suspend comparable experiments pending proof they could be conducted responsibly. That was a request, not a judicial instruction or a restriction covering every laboratory. Evidence gathering was still under way.
That office published its 17-page demand, issued and served on 20 August. It seeks a chronology, participants and affected systems, protective measures, earlier warnings inside the company, potential damage, other agent episodes and policies governing evaluations. These questions belong to that state’s instrument, not the California inquiry.
Prepare records that show what actually happened
Evaluation teams should retain each run’s approval, tool and network permissions, monitoring, incident decisions and affected-party communications. Scattered records impede reconstruction. Evidence should establish the controls actually used, rather than a general safety principle. This is operational advice, not a state-prescribed workflow.
The earlier California statement also advocates regulator access to evidence and publication of investigators’ conclusions. Teams can prepare without treating advocacy as binding: name an evaluation-incident owner, preserve material that reconstructs decisions and establish how to alert an outside operator whose systems could be affected.
Primary sources
- Evidence demand notice.
- Federal oversight proposals.
- Separate state inquiry.
- Published instrument 26-0007.
This article provides operational context, not legal advice.
