What changed

CourtListener docket metadata for *Dow Jones & Company, Inc. v. Perplexity AI, Inc.* reflects that a second amended complaint by Dow Jones & Company, Inc. and NYP against Perplexity AI, Inc. was entered on Jan. 28, 2025, along with listed appendices. The supplied source is metadata-only; this note does not rely on the full complaint, a merits record, or any description of the appendix contents beyond their existence in the metadata.

For AI search, summarization, and answer products, the immediate value of this signal is not predicting the outcome. It is a reminder that content-use disputes can quickly turn on whether the company can reconstruct what content was used, how it was surfaced or displayed, what notices or objections were received, and who owned the response.

The operational hinge

The docket metadata does not establish infringement, product architecture, training practices, or liability. It also should not be read as confirming the contents of the listed appendices. Even with that limitation, the docket signal points to a familiar dispute-readiness problem: when publisher-content questions arise, counsel may need to reconstruct content provenance, product behavior, rights-holder notices, and vendor commitments.

That makes this a documentation and governance check for companies operating or buying AI tools that search, retrieve, summarize, cite, or generate answers using third-party content.

Controls to review now

1. Maintain a content-source inventory

Counsel should be able to identify whether publisher content reaches the product directly, through an index, through a vendor, through cached snippets, or through another retrieval path. The inventory should be specific enough to support a later review of what content categories were available to the system and under what terms.

2. Preserve product evidence when notices arrive

When a publisher complaint, objection, or notice is received, preserve the materials needed to reconstruct the relevant product behavior. That may include prompts, retrieval logs, citations, output examples, and the configuration or source-selection records tied to the challenged use.

3. Document exclusion and escalation workflows

If the product has ingestion exclusions, source restrictions, takedown paths, or rights-holder escalation workflows, keep records showing how those processes operate and who approves changes. The goal is not just to have a policy, but to show how it is applied when a specific objection is made.

4. Review customer-facing claims

Product, sales, and procurement teams should review claims about “real-time” answers, citations, source use, or publisher coverage. Marketing and contract language should not overstate what the product does, what rights have been cleared, or how third-party content is handled.

5. Check vendor allocation

For enterprise AI answer products, vendor terms should be reviewed for who bears responsibility for training-data claims, retrieval-source claims, output claims, rights-holder notices, and preservation of relevant logs or evidence.

Questions for counsel

  • Are we using publisher content directly, through indexes, through vendors, through cached snippets, or through another retrieval path?
  • Can we identify what sources were available to the system at the time of a challenged output?
  • Who owns intake and tracking for rights-holder correspondence?
  • Do we preserve prompts, retrieval records, citations, and output examples when a notice or complaint arrives?
  • Do vendor contracts allocate responsibility for training, retrieval, citation, and output-related claims?
  • Are public-facing claims about source use and answer generation consistent with how the product actually operates?

How to use this signal

Use the docket update as a litigation-readiness checkpoint. For products that generate answers from third-party materials, the practical next step is to test whether the company can move from a rights-holder objection to a coherent evidence file: source path, contractual basis, product behavior, correspondence history, and escalation record.

That file should be assembled before a dispute hardens, not after pleadings are filed.