Court Forces OpenAI to Preserve Deleted Chats in NYT Copyright Fight

Court Forces OpenAI to Preserve Deleted Chats in NYT Copyright Fight

Published Nov 11, 2025

An ongoing NYT v. OpenAI MDL centers on a May 13, 2025 magistrate order requiring OpenAI to preserve all output logs—including user‐deleted chats—across consumer tiers and many API users. OpenAI opposed, citing privacy, GDPR conflicts, and contractual commitments. On Oct. 22, OpenAI said it is no longer under a blanket obligation to retain new consumer chat or API content indefinitely; standard deletion policies (30 days) resume for new content, but the company must still preserve historic April–September 2025 data and logs tied to plaintiff‐flagged accounts. The order reshapes user privacy expectations, corporate compliance, and publishers’ litigation strategies seeking evidence of training‐related outputs. No significant new filings have appeared in the past two weeks.

OpenAI Data Retention Rules, Court Orders, and User Impact Summary

  • Court preservation order issued on 2025-05-13 requiring OpenAI to preserve all output log data, including deleted chats.
  • Indefinite retention lifted on 2025-10-22; standard deletion resumed: 30-day retention for new deleted chats and API data.
  • Ongoing obligations: retain historic user data from Apr–Sep 2025 (6 months) and logs tied to plaintiff-flagged accounts.
  • Coverage: applies to 4 ChatGPT tiers (Free, Pro, Plus, Team) and non-ZDR API users; excludes 3 groups (Enterprise, Edu, ZDR).
  • No significant new developments in the past 14 days.

Navigating GDPR Risks, Copyright Liabilities, and Legal Uncertainties in AI Log Retention

  • Bold: GDPR/privacy conflict and elevated breach exposure from retained logs (Apr–Sep 2025). Reason: Historic chat/API data preserved against prior deletion expectations risks non-compliance with storage-limitation rules and concentrates sensitive data attractive to attackers. (Probability: Medium–High | Severity: High). Opportunity: Lead with zero-data-retention defaults, EU data residency, encryption/HSM and granular retention controls; beneficiaries include privacy-tech vendors, cloud providers, and enterprise customers seeking compliant AI.
  • Bold: Amplified copyright liability if logs evidence output–source correlation. Reason: Preserved logs could strengthen claims that model outputs reproduce protected content, raising damages, compelled filtering, or retraining risks in MDL. (Probability: Medium | Severity: Very High). Opportunity: Convert to licensing partnerships, provenance/watermarking, and rights registries; publishers monetize content, and AI providers differentiate via transparent sourcing and safer training pipelines.
  • Bold: Known unknowns: scope of discovery and remedial orders. What’s uncertain: Whether courts will compel broader dataset disclosures, model transparency, ongoing retention regimes, or injunctive product changes; how EU/US regulators react to court-driven overrides of data-minimization; whether other plaintiffs piggyback on preserved data. (Probability: Uncertain | Severity: High if expanded). Opportunity: Shape industry standards and safe-harbor frameworks, pre-negotiate collective licenses, and invest in auditability; early movers in governance tooling, consent management, and transparency reporting stand to gain.

Key Legal Milestones and Privacy Developments in Late 2025 to Early 2026

PeriodMilestoneImpact
Nov–Dec 2025MDL case-management/scheduling order update by Judge SteinSets discovery and briefing timelines; clarifies near-term cadence
Nov–Dec 2025Court approval of search/discovery protocol for preserved ChatGPT logs (deleted chats, Apr–Sep 2025, flagged accounts)Defines scope and privacy safeguards; unlocks NYT access; drives discovery volume
Nov–Dec 2025Protective order/GDPR-compliant handling finalized (anonymization, transfer rules)Reduces EU privacy/regulatory risk; may limit usable data in U.S. court
Dec 2025–Jan 2026Initial production of historic logs (Apr–Sep 2025) and flagged-account materialsProvides substantive evidence; informs settlement posture and motion strategy
Early 2026Rulings modifying or reaffirming narrowed retention obligations post-2025-10-22Could expand or further limit retention; impacts user privacy and OpenAI’s compliance burden

How Preservation Orders Are Accelerating Litigation-Ready Privacy and Data Minimization Solutions

Some see the May 13 preservation order as a necessary disinfectant and others as a state-sanctioned privacy breach. To publishers, locking down logs is simple accountability: without them, fair-use arguments become a smokescreen for untraceable appropriation. To OpenAI, the mandate is a privacy nightmare that bulldozes deletion promises and collides with global law. Users hear “deleted” and expect oblivion, not cold storage. Regulators fear a precedent where discovery trumps minimization by default; judges reply that discovery is not a suggestion. Even after OpenAI’s October 22 update narrowed retention to historic April–September 2025 data and flagged accounts, critics call the delete button a placebo and privacy maximalists label carve‐outs capitulation. Supporters counter that evidentiary truth matters more than UX optics: you can’t audit what you refuse to keep.

Yet the more surprising lesson isn’t doctrinal—it’s architectural. The case is forcing a market for “litigation‐ready privacy”: tiered data regimes, explicit carve‐outs, and verifiable deletion that can satisfy courts without hoarding content. Expect a pivot from blanket retention toward cryptographic attestations, forward‐secure logs that prove non‐possession, and wider default use of zero‐data‐retention contracts, on-device or ephemeral inference, and narrow, consented evidence escrow. Publishers may gain cleaner correlational tests while users gain clearer, enforceable limits; both sides get fewer fishing expeditions. The paradox is stark: a preservation order meant to expose more data may ultimately catalyze systems that retain less—replacing “trust us” with “prove it,” and making the next discovery fight about proofs, not troves.