GateTrue

What each generator documents about marking its output

Reasons printed beside a mark, and where

Two entries publish a reason beside a marking decision: disclosure on one pricing page, and named rules for a two-layer mark on another, whose visible half the same vendor's guide gives a reason for removing. From 2 source pages, read 2026-09-22 to 2026-10-13; no maker pays to be listed.

Published reasons, and how far each one reachesDisclosure is given as the reason for a mark on two plans, and is not extended to the plans above them. Named rules are given for a two-layer mark on every output. Avoiding a second label is given as a reason for removing the visible half.Reasons for keeping a markA reason for removing oneThe argumentDisclosure, and named rulesA destination adds its own labelWhere it appearsA pricing page, a set of termsA compliance guideHow far it reachesTwo plans, every outputThe visible half onlyWhat it predictsA mark that survives repackagingA switch that stays availableThe register records that a reason was given, not whether it is sound
Fig. 1 Thirteen other entries print a marking line with no justification at all, which is what a feature grid ordinarily looks like.
The rows this finding rests on, with the value each one's own pages support. Recorded 2026-09-22.
GeneratorUser toggleDocument read
D-IDPlan benefit, not a settingpricing page
SceneMixerPlan benefit, a switch for paid membersterms of service

Inclusion rule. Entries whose pages give a stated reason for applying a mark or for allowing it to be removed. A price is not a reason, and neither is an unexplained feature line. Order. Alphabetical by generator name.

1Two arguments, from three kinds of document

A pricing page gives disclosure as its reason: the mark is there so that there is transparency about the synthetic nature of the videos users generate. A set of terms gives named rules, China's deep-synthesis provisions and Article 50 of the EU AI Act, for a two-layer mark, and the same vendor's compliance guide gives an operational reason for removing the visible half: a publishing platform adding its own label would put two labels on one frame.

None of the other thirteen entries offers a reason of any kind. Their marking lines are packaging decisions printed without justification, which is the ordinary state of a feature grid: nothing on it explains why a feature exists, only which plan includes it.

2Why a stated reason is worth recording

It predicts what a future change looks like. A mark held in place by a compliance argument does not move when a pricing page is redesigned, because the argument is not about packaging. A mark held in place by nothing at all moves whenever the grid does, and a reader planning around it should expect that.

The register cannot audit either one. Whether the disclosure argument is the real motive, and whether the named rules oblige what the terms say they do, are questions no published page settles. What can be recorded is that a reason was given, which reason, and by whom.

3Where each argument stops

The disclosure argument covers two plans and is not extended to the ones above them, so the mark that discloses synthetic origin disappears when a customer pays enough. The removal argument covers the case where a destination adds a label of its own, and the terms beside it keep the invisible layer on whatever happens to the visible one.

Each reason is therefore narrower than it first reads, and only the terms are written as a policy about the product. The register records the scope alongside the reason for the same purpose it records everything else: so a reader can see where the statement stops.

An earlier version of this page counted a third entry, with a reason attached to a stamp on one surface. The guide behind it has since been replaced and no longer prints that reason, so the register no longer records it.

4Sources

  • Rationale
    The pricing page gives a reason for the mark: that there is transparency about the synthetic nature of the videos users generatepublished beside the markD-ID, pricing / recorded 2026-09-22
  • Machine-readable marking
    An invisible, compression-resistant watermark or content credential is applied to output and never removedstated in the termsSceneMixer, terms of service / recorded 2026-10-13
  • User toggle
    Paid members can switch the badge off for later renders; the terms make removing the visible label an optional paid feature where the law permitstied to a paid membershipSceneMixer, terms of service / recorded 2026-10-13

Every row above is read from the vendor page named beside it, on 2026-09-22. The same values in register form are on the support table, the rule for this column is on the control column page, and what may fill a cell at all is on the what earns a row page. Other findings: marks that get described, paid plans still marked.