TruaceTracing the truth around AIMonday, July 13, 2026
TRV-2026-0198Certified recordPeer-reviewed

"That's another doom I haven't thought about": A User Study on AI Labels as a Safeguard Against Image-Based Misinformation

As generative AI is increasingly contributing to the spread of deceptively realistic misinformation, lawmakers have introduced regulations requiring the disclosure of AI-generated content. However, it is unclear if labels reduce the risk of users falling for AI-generated misinformation. To address this research gap, we study the effect of labels on users’ perception and the implications of mislabeling, focusing on AI-generated images. We first explored users’ opinions and expectations of labels using five focus…

Policy · P Space — documented harm · certified 2026-07-13 · v1 · article view · machine-readable

Current reading — problem

The same survey found overreliance on labels, making participants more susceptible to false claims with human-made images and more hesitant to believe true claims illustrated with labeled AI-generated images.

What this doesn’t fix

Labels showed unintended side effects from overreliance, including increased susceptibility when false claims used human-made images and reduced belief in true claims when illustrated with labeled AI images.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0198, v1: “"That's another doom I haven't thought about": A User Study on AI Labels as a Safeguard Against Image-Based Misinformation.” Truvace, 2026-07-13. /record/TRV-2026-0198 (accessed at citation time). sha256 6a4afeeafa1b6682

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv16a4afeeafa1b

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0198 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.