GateTrue

What each generator documents about marking its output

D-ID's control sits a tier above the first payment

D-ID's control is a plan benefit like ten other rows, with one difference the vendor writes out: the trial and the first paid plan are both marked, so paying once does not exercise the control. As of 2026-09-22.

What a billing record proves on this rowWhere control is a plan benefit, the state of a file is normally recoverable from an invoice. Here two plans are on the marked side of the boundary and one of them is paid, so an invoice establishes that somebody subscribed without establishing what their files carry.What does a subscription tell you about the fileOn nine other plan-gated rowsEnoughAny paid plan is on the unmarked side, sopayment settles the question.On this rowNot enoughThe first paid plan is named as marked, sothe plan name decides, not the payment.Why the register records a boundary rather than a yes or no
Fig. 1 The plan name has to be known. Nothing in the file distinguishes the two paid states unless the mark itself is visible in it.
One cell of the register, and what it rests on. Read from the vendor's pricing page on 2026-09-22.
The readingWhat it holds
The recorded valuePlan benefit, not a setting
The vendor's own wordsVideos carry a D-ID watermark on the Trial and Lite plans.
How the reading was takenRead from a sentence naming the two marked plans, which places the control above the cheaper one.

Inclusion rule. One row for the value, one for the sentence or absence behind it, one for the method. Nothing here is drawn from output, support replies or coverage by anyone else. Order. Fixed order: the value, then its evidence, then the method.

1The same mechanism, and a boundary in an unexpected place

Ten rows here read plan benefit and most readers convert that into free is marked, paid is not. This vendor states the exception in a sentence: videos carry the mark on the Trial and Lite plans. The mechanism is ordinary and the position of the boundary is not.

Two rows in this register have a paid plan on the marked side of the line. On the other one the fact has to be read off an icon; here it is written. That makes this the clearer of the two and the reason the register records a mechanism and a boundary rather than a yes or no about removability.

2What an invoice proves, and what it does not

When control is a plan benefit, the state of a file is recoverable from the billing record, which is the advantage of this mechanism. On this row the billing record has to be read carefully: it proves a subscription and the subscription might be the one whose output is still marked.

For a production collecting footage from contributors that is a question to settle before material is gathered. Paying does not stand in for the plan name here, and there is no way to tell from the file which of the two paid states it came from unless the mark is visible in it.

3A reason published beside the mark, and where it stops

The page gives a rationale: transparency about the synthetic nature of the videos users generate. Read against the boundary, the argument covers the trial and the first paid plan and is not extended upward. The register records the rationale and the boundary as separate rows and leaves the seam visible.

A stated reason is worth recording because it predicts what a change looks like. A mark justified by disclosure has an argument for surviving a repackaging; a mark justified by nothing at all moves whenever the grid does. Two vendors here publish a reason, and this is the one that publishes it on a commercial page.

4Sources

  • Paid tier
    Videos carry a D-ID watermark on the Trial and Lite plans, so the first paid plan is still markedmarked one plan above freeD-ID, pricing / recorded 2026-09-22
  • 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

The value above is read from d-id.com, the vendor's pricing page, on 2026-09-22. The whole row for this generator is on its own page, and the rule for what this column may hold is on the control column page. Neighbouring readings: Sora, file contents, Veo, file contents.