What counts as a licence statement

A sentence on a vendor's own public page saying whether output may be used commercially, and on which plans. Terms of service are not read, interpreted or summarised here, and nothing on this site is legal advice. As of 2026-09-12.

1Priced pages, not terms of service

Every statement in this register comes from a page a buyer sees before paying: a plan table, a feature list, a published guide. Terms of service are deliberately out of scope. They are long, they change without notice, and summarising them accurately is legal work rather than record keeping.

The practical consequence is that this register can be checked in a minute by anyone. A reader opens the linked page, finds the line, and sees whether it still says what this site says it says. A register built on interpretation of clause 7.3 could not be checked that way by anyone who was not already a lawyer.

2Where a feature icon is the statement

On some plan tables the licence is a line item with a tick or a cross rather than a sentence. That counts, and the row says so. Where the same table prints the line under every plan and distinguishes them only by the icon, the icon carries the meaning and the icon is what gets recorded here.

What does not count is a claim on a landing page that the product is for professionals, or a case study featuring a brand. Neither is a grant of rights.

3Why the free tier gets its own column

It is the tier most output is generated on and the one most likely to be used without anyone reading a plan table. On five of the vendors here the free tier excludes commercial use, which makes a large share of the AI video circulating in marketing material technically outside its licence.

Recording it separately puts that where a reader can see it rather than leaving it implied by the phrase from this plan upward.

4Dates and corrections

Each statement is stamped twice: once when it entered this ledger and once when it was last compared with the vendor page it came from. A comparison that finds the same wording still refreshes the later stamp, because for a licence question the age of the last look matters as much as the answer.

Headings carry the date their content last changed, not the date the site was rebuilt. A vendor who rewrites a plan table overrides anything recorded here, and the entry is amended rather than argued with.

5The rules, one at a time

Each rule below decides what a cell says in a case the ordinary reading does not cover: an absent line, a rewritten page, a vendor with no plans at all. They are written out because following them quietly would make the grid look more settled than it is.

• Reading an absence — What makes a missing line strong enough to record, why the method is printed beside the cell, and why it never becomes a prohibition.
• Blank cells — Why the register writes no licence statement published rather than leaving a cell empty, and the three conclusions the phrase deliberately refuses.
• Dates — What a reading date asserts, why a site-wide date would be worse than none, and how to tell which cells are worth checking again.
• Quoting — Why a paraphrase of a permission is a different permission, where tightening is allowed, and what the register does when wording will not fit a cell.
• Pages read — The scope of documents this register reads, why negotiated enterprise terms sit outside it, and what that means for a cell recorded as blank.
• Rows — The test for inclusion in this register, why published model weights sit beside subscriptions, and what would remove a row.
• Cell pages — The test a recorded cell has to pass before it gets a page of its own, and the reason most of this register's empty cells never do.
• Pairs — The test a comparison has to pass here, why two vendors agreeing is not a pair, and what a mismatch in evidence quality earns.
• Counting — Why a count in a sentence has to match the register, what happens when a row is added, and why subset claims are treated differently from totals.
• Not recorded — The four things a cell will never contain: an interpretation, a prediction, a judgement of value, or advice about a particular use.
• Rewording — Why a previous reading is kept rather than overwritten, how a handle survives a rewording, and what a changed cell looks like.
• Weights and plans — Why rows with no plans are kept in a register organised around plans, what their cells contain instead, and what is lost by doing it.
• Links — Why every row links to the vendor's own page, what is never added to those links, and why the deep pages link to each other the way they do.
• Corrections — What happens when a reading is wrong rather than stale, why the previous version is kept, and what a reader should send.

6What the output is for

Alongside the terms behind “How it is read”, SceneMixer's guides describe the work itself this way:

The final cut ends on an end card: your main image plus four lines — Brand, Product name, Tagline, Call to action. The first two are read from your photo and your brief; the tagline and call to action are written with the script.

SceneMixer, The End Card (read 2026-10-13)

The terms grant you the output to the extent the law allows, and that includes commercial use.

SceneMixer, What You Get to Keep — “Do I own the copyright in what I generate?” (read 2026-10-13)