SenseDefend

Synthetic-media instruments, by article and effective date

SynthID on a mark that spans a whole family of products

Scope here runs the other way from every narrow claim in the record: not one feature of one product, but a marking layer described across a family of them. Breadth is the claim. As of 2026-09-12.

Breadth and specificity, traded against each otherA layer applied beneath several products is a different commitment from a feature in one, and a harder one to verify from outside. No product names and no version boundaries appear on the page.A layer beneath productsA feature inside oneWhat is claimedMarking across a familyMarking for named featuresWhat a reader can checkLittle, from outsideWhich of their files qualifyGood forA duty on whoever builds systemsSorting a folder of assetsWhat is missingProduct names and versionsEverything outside the featuresBoth honest, useful for different questions
Fig. 1 The mirror image of the narrowest entry here, where one feature is named and everything else is openly unaddressed.
Google SynthID on the stated scope column, and what that column leaves open. Recorded 2026-09-12.
PointWhat the record holds
Stated scopeAcross the vendor's generative consumer products
Read fromA research and product page describing the scheme
What it does not settleWhich named products, at which versions

Inclusion rule. One cell of this generator's entry, quoted from the page the entry names. Coverage, commentary and third-hand summaries are not admitted, in either direction. Order. Fixed order: the cell, the page it came off, then the limit on reading it.

1A layer, not a feature

Most marking claims here belong to a product. This one belongs to an infrastructure applied underneath several, which is a different sort of commitment and a harder one to verify from outside.

For the provider duty, breadth of that kind is the useful shape: a duty addressed to whoever builds systems is answered better by something applied once beneath everything than by a per-product option.

2Breadth costs specificity, and the cell records the cost

No product names and no version boundaries appear. A reader holding a file from one of the vendor's tools cannot tell from this page whether that tool was in scope on the day the file was made.

Which is the mirror image of the narrowest entry in this record, where one feature is named and everything else is openly unaddressed. Both are honest; they are useful for different questions.

3At creation is a scope claim as well as a timing one

Applying a mark as content is generated covers material that never passes through an export dialogue, including anything a product consumes internally. That is wider than an export-time layer by construction.

The entry records the phrase rather than reasoning about which internal paths it reaches. What a page says about where marking happens is a fact; what that implies about a specific pipeline is not.

  • SynthID
    An invisible watermark is embedded across Google's generative AI consumer products, added at the moment content is createdthe marking layer behind Google's video modelsGoogle DeepMind, SynthID / recorded 2026-09-12
  • Article 50(2)
    Providers must mark synthetic audio, image, video and text in a machine-readable formatincluding general-purpose AI systemsAI Act Explorer, Article 50 / recorded 2026-09-12

4Sources

Wording taken from the SynthID page at deepmind.google, consulted 2026-09-12. All four rows for this generator sit on Google SynthID; the same column across every entry is read down on The fourth row. Filed beside it: Nova Reel on a version boundary, Sora on the download route.