SenseDefend

Synthetic-media instruments, by article and effective date

What each generator publishes about marking its output

Each generator is read only from its own public pages. What is marked, what is removable and what is written into the file are recorded separately, because the obligations treat them separately. As of 2026-09-12.

Two marks, two audiences, and one common gapA visible watermark addresses a viewer. A machine-readable mark addresses a platform or a detector. The obligations recorded here assume both kinds exist. Generator documentation reliably covers the first and is usually silent about the second.Best documented firstVisible watermarkSeen by a viewer, croppable, documented on almost every pricingpage.Container metadataAttached outside the picture. Survives nothing more than acareful export.Machine-readable markRead by a platform or a detector. Almost never documented byname.The layer the obligations lean on hardest
Fig. 1 Silence in the third column is the most repeated finding in this record, and it is a fact about documentation rather than about the files.

The reason for keeping three columns is in the text rather than in the products. A visible watermark satisfies a disclosure expectation aimed at viewers; a machine-readable mark satisfies one aimed at platforms and detectors. A product that does the first and not the second has met one expectation and not the other.

Where a vendor's pages say nothing, the entry records silence rather than absence. A mark may well exist and be undocumented, and an undocumented mark is of no use to anyone trying to demonstrate compliance.

Entries carry the address and the reading date, so a page that has since been updated can be compared against what it said when the record was made.

1The generators

  • SceneMixer — What SceneMixer publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • Pika — What Pika publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • LTX Studio — What LTX Studio publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • Kling AI — What Kling AI publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • Runway — What Runway publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • Google SynthID — What Google SynthID publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • OpenAI Sora — What OpenAI Sora publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • Adobe Firefly — What Adobe Firefly publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • Synthesia — What Synthesia publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • HeyGen — What HeyGen publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • MiniMax Hailuo — What MiniMax Hailuo publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • Alibaba Wan — What Alibaba Wan publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • ElevenLabs — What ElevenLabs publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • Meta AudioSeal — What Meta AudioSeal publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • Amazon Nova Reel — What Amazon Nova Reel publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).
  • Microsoft Designer — What Microsoft Designer publishes about marking, set against the provider duty in Article 50(2) and the deployer duty in Article 50(4).

A generator is recorded when its own pages address marking at all, including when they address it only to say nothing is applied.

Elsewhere in the record: EU, Duties, Statements, Pairs, Fields, Questions, Terms, Learn, Data. How an instrument is read is set out on the sourcing page.