GateTrue

What each generator documents about marking its output

Luma AI is precise about rights, silent on bytes

Luma AI's licensing guide is unusually exact about what happens to generated files over time. Neither it nor the pricing page names a provenance scheme, a metadata field or a detection route. As of 2026-09-22.

Two kinds of statement, and what each one needs to be completeA rights statement is complete when it attaches a permission to a file. A provenance statement is not complete until it names something a reader can inspect. One document here does the first thoroughly and does not attempt the second.A rights statementA provenance statementWhat it attachesA permission, to a fileA signal, inside a fileComplete whenThe permission and its scope are statedA scheme or field is namedWho it servesWhoever commissioned the workWhoever receives the file laterOn this rowUnusually exact, in both directions intimeNothing published at allWhy one careful document leaves this column empty
Fig. 1 The columns need different genres of page, which is what the whole register finds across its fifteen rows.
One cell of the register, and what it rests on. Read from the vendor's licensing guide on 2026-09-22.
The readingWhat it holds
The recorded valueNot documented
The vendor's own wordsNo provenance scheme, metadata field or detection route is named on either page.
How the reading was takenRead from a licensing guide and a pricing page, neither of which describes the contents of a file.

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.

1Exactness about one thing and silence about another

This is the entry that says what happens to files already generated: a watermark applied under the free or entry plan is not lifted by a later upgrade, and clean files made while a subscription was active are not described as changing when it ends. That is more precision about the life of a file than any other page here offers.

The same pages say nothing whatever about what is written inside those files. Precision about rights and silence about bytes coexist comfortably in a licensing document, because a licence is a statement about permissions and not a specification of an artefact.

2Why the two are not the same kind of statement

A rights statement can be complete without describing anything technical: it attaches a permission to a file and the permission is the whole content. A provenance statement cannot. It has to name a scheme or a field, because the point of it is that somebody else can inspect the artefact.

So the empty cell here is not evidence of carelessness in a document that is otherwise careful. It is evidence that the two columns need different genres of page, which is exactly what the register finds across all fifteen rows: the vendors who fill this column were read from references and cards, not from terms and grids.

3What a reader is left able to establish

Given a file from this product, a reader can establish a great deal about whether it may be used, provided they know which plan produced it and when. They can establish nothing at all about whether the file itself says it was generated, because no name, field or route is published.

Those two capabilities serve different people. The rights precision serves whoever commissioned the work; the provenance silence affects whoever receives it later, with no knowledge of the plan or the date. This register keeps the two in separate columns for that reason.

4Sources

  • Machine-readable marking
    Not documented on the vendor's public pages (as of 2026-09-22)not raised on the licensing pageLuma, Dream Machine licensing guide / recorded 2026-09-22
  • Paid tier
    Content generated under the Plus, Unlimited and Enterprise plans carries commercial usage rights with no watermarkfrom Plus upwardLuma, Dream Machine licensing guide / recorded 2026-09-22

The value above is read from lumalabs.ai, the vendor's licensing guide, 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 machine-readable marking column page. Neighbouring readings: Kling AI, free tier, Pika, free tier.