TruaceTracing the truth around AIMonday, July 20, 2026
TRV-2026-0364Certified recordPeer-reviewed

Decent deepfakes? Professional deepfake developers’ ethical considerations and their governance potential

Abstract Policymakers and societies are grappling with the question of how to respond to deepfakes, i.e., synthetic audio-visual media which is proliferating in all areas of digital life– from politics to pornography. However, debates and research on deepfakes’ impact and governance largely neglect the technology’s sources, namely the developers of the underlying artificial intelligence (AI), and those who provide code or deepfake creation services to others, making the technology widely accessible. These actors…

Policy · The Trace — both readings · certified 2026-07-20 · v1 · article view · machine-readable

Current reading — gain

Professional deepfake developers' ethical values can inform governance measures that directly address developers and providers to curb dangers of synthetic media.

Current reading — problem

Synthetic audio-visual deepfakes are proliferating across digital life, creating governance challenges for policymakers and societies.

What this doesn’t fix

Findings are based on a small qualitative sample of ten expert interviews, limiting generalizability to all developer populations.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0364, v1: “Decent deepfakes? Professional deepfake developers’ ethical considerations and their governance potential.” Truvace, 2026-07-20. /record/TRV-2026-0364 (accessed at citation time). sha256 0b37fa409451ec0f

Calibration history

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

  1. Certifiedv10b37fa409451

    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-0364 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.