ChatGPT Kept the Logs. The Palisades Arson Jury Saw Them.

Prosecutors in the Los Angeles Palisades fire trial introduced OpenAI conversation records as evidence, exposing the gap between what the model retains and what users believe disappears.

ChatGPT conversation logs were entered into evidence during the Palisades fire arson trial.
Prosecutors paired the logs with location data and witness testimony to build their case.
The case ended in a mistrial, but the evidentiary use of the logs stands as precedent.
OpenAI retains user conversation data by default; deletion requires deliberate account action.
The episode is a working demonstration of what the system actually does, not what users assume.

A Los Angeles prosecutor put ChatGPT conversation logs on the evidence table in an arson trial tied to the Palisades fire. The trial ended in a mistrial. The logs were still admitted. That part does not go away.

The named product is ChatGPT, the OpenAI cloud service. The relevant specification is retention: by default, OpenAI stores conversation history on its servers. Users can disable that, or request deletion. Most do not. The data sits.

That is not a flaw. It is the design. A cloud inference service with persistent accounts keeps state. The number that matters here is not a clock rate or a die size — it is a retention window long enough for investigators to subpoena records and get something back. They did.

The tradeoff is exactly what it always is with cloud-side storage: the provider holds the record, not the user. Local compute gives you nothing to subpoena. Remote compute gives you continuity, sync across devices, and a log that exists independent of whether the endpoint survives. You pick one. OpenAI picked the second. So does every major cloud service.

What the Palisades case added is a named defendant, a named service, and a working evidentiary chain. Investigators obtained the logs. Prosecutors introduced them. The machine performed as specified. The assumption that a conversational interface is inherently transient — that it works like speech and leaves no trace — is a user belief, not an engineering fact.

The spec was always public. The terms of service say what they say. The gap is between what people read and what they click through. That gap is not ChatGPT's problem. It is theirs.