SenseDefend

Synthetic-media instruments, by article and effective date

Synthesia on the conditions under which a mark appears

Almost every tier-gated entry here states a price. This one states conditions, and the two named conditions are unrelated: one is what was bought, the other is a flag set by whoever wrote the request. As of 2026-09-22.

Two unrelated causes, one visible resultThe article names a plan and an API test flag as conditions under which the mark appears. One is chosen once and shows on an invoice; the other is set in code and leaves no trace on any account page.The plan conditionThe test-mode conditionSet byWhoever holds the accountWhoever wrote the integrationVisible afterwardsOn an invoiceNowhere, unless loggedHow it is undoneUpgrade, then generate againClear the flag and request againOn a finished fileA new render is neededA new render is neededSame mark, two places to look for the cause
Fig. 1 The phrase such as also signals the list is not closed, and the cell keeps that hedge rather than tidying it away.
Synthesia on the deployer disclosure column, and what that column leaves open. Recorded 2026-09-22.
PointWhat the record holds
Article 50(4), deployer disclosureA visible mark under stated conditions, including Basic plan and test mode
Read fromA knowledge-base article, written to answer a support question
What it does not settleWhich other conditions the phrase such as covers

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.

1Conditions are more honest and less tidy than a price

A cell reading removal from the paid tier is easy to compare and quietly wrong whenever a second cause exists. Here the page names two causes with nothing in common, which is harder to tabulate and closer to how products behave.

The phrase such as also signals that the list is not closed. The cell reproduces that hedge instead of tidying it away, because a reader relying on a closed list would be relying on something the page did not say.

2A test flag is the cause nobody remembers

A plan is chosen once and shows up on an invoice. A test flag is set in code, often by somebody building an integration months before the first delivery, and nothing on an account page will later reveal it was on.

That makes it the condition most likely to surprise a production, and it is why this entry carries a separate row about permanence. What a flag did to a finished file is not always undoable afterwards.

3Avatar video makes the disclosure question sharper

The duty on deployers concerns content that is generated or manipulated, and the deepfake language in the paragraph is aimed squarely at a synthetic person on screen. An avatar platform is the case the drafters plainly had in mind.

None of which decides anything for a particular publication. The cell records what a support page says about when a mark appears, with its address and the date it was read, and stops there.

  • Synthesia (synthesia.io)
    The watermark appears on videos generated under certain conditions, such as being on the Basic plan or generating in API test modean avatar video platformSynthesia, knowledge base / recorded 2026-09-22
  • Article 50(4)
    Deployers must disclose image, audio or video content that is a deep fakefirst subparagraphAI Act Explorer, Article 50 / recorded 2026-09-12

4Sources

Wording taken from the knowledge-base article at help.synthesia.io, consulted 2026-09-22. All four rows for this generator sit on Synthesia; the same column across every entry is read down on What it asks for. Filed beside it: HeyGen on two plans and a free tier, Hailuo on an AIGC label parameter.