GateTrue

What each generator documents about marking its output

Reasons printed beside a mark, and where

Three entries publish a reason beside a marking decision: compliance, disclosure, and avoiding a collision with a platform's own label. Two of those argue for keeping a mark and one for removing it. As of 2026-09-22.

Three 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. Compliance is given for a stamp on one surface, while another route to the same models defaults to no stamp. Avoiding a second label is given as a reason for removal.Reasons for keeping a markA reason for removing oneThe argumentDisclosure, and legal complianceA destination adds its own labelWhere it appearsA pricing page, and a console guideA compliance guideHow far it reachesTwo plans, and one surfaceWherever a platform labels outputWhat it predictsA mark that survives repackagingA switch that stays availableThe register records that a reason was given, not whether it is sound
Fig. 1 Twelve 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
SceneMixerYes, in settingscompliance guide
WanA request parameter, not a planvideo generation guide

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.

1Three 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 console guide gives compliance, attributing an unremovable stamp to legal requirements. A compliance guide gives an operational reason for removal, that a publishing platform adding its own label would put two labels on one frame.

None of the other twelve 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 any of the three. Whether a legal requirement actually obliges the stamp, and whether the disclosure argument is the real motive, 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 compliance argument covers one surface and the same models are reachable through another that defaults to no stamp. The removal argument covers the case where a destination adds a label of its own.

Each reason is therefore narrower than it first reads, and none of the three is presented 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.

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
  • Control
    The console watermark cannot be turned off from the console UI, which the page attributes to legal compliance requirementsno switch on the console surfaceModel Studio, video generation guide / recorded 2026-09-22
  • User toggle
    An AIGC watermark switch in settings turns it offno plan condition statedSceneMixer, compliance guide / recorded 2026-09-12

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.