BrandVideoAI

What each vendor's terms say about commercial use

A seat, and why a permission attached to one moves with people

A seat is a named place on a subscription. Where a product is priced per seat, a permission granted to paying customers attaches to an account, and accounts belong to people who join projects, leave them and change employers. As of 2026-09-22.

A permission attached to a login, and a file that shows nothingOn a per-seat product the permission attaches to an account. The exported file carries no trace of which account produced it, so the fact has to be written down at the time or lost.A seat isassignedTo a person,who may bestaff, acontractor oran agency.A permissionWork isexportedThe permissionis in force.Nothing in thefile recordswhose it was.A deliverableThe seatlapsesSomebodyleaves, andthe account isreassigned orclosed.A questionA review asksWhich accountproduced this,and was itactive.Answerableonly fromrecords.
Fig. 1 Neither the account nor the date is recoverable from the file afterwards.
Questions that per-seat pricing turns into records rather than readings. Recorded 2026-09-22.
QuestionWhat the phrase answers
Which account exported the fileThe fact the permission attaches to
Was that seat active at the timeDecides whether the grant was in force
Who holds the seat nowIrrelevant to work already exported, and often assumed
Can a freelancer's seat cover client workA sublicensing question, usually unaddressed

Inclusion rule. Phrases that appear in more than one vendor's permissions documents and that change what a sentence means. A phrase used by a single vendor in a single clause is described on that vendor's own page instead. Order. Reading order: where you meet it, then what it settles, then what it does not.

1The licence question becomes an identity question

On a per-generation product the permission attaches to the transaction. On a per-seat product it attaches to a person's login, and the deliverable carries no trace of which login produced it.

That is not a defect in the pricing model. It is a reason the record worth keeping is the account and the date, kept at export, because neither is recoverable from the file afterwards.

2Freelancers are the awkward case

A contractor holding their own seat and delivering to a brand is passing on a permission they hold, which is a sublicensing question most documents do not address. The work usually ships anyway.

Where it matters is later: the contract ends, the seat lapses, and the brand is relying on a permission held by somebody who no longer has access. The asset does not stop existing, and the basis for it becomes hard to evidence.

3What to ask before a seat is decommissioned

Whether output produced on it remains usable, and whether the account's history is exportable. Both answers are short, and neither is usually on the plan page.

A team that asks once and writes the answer down has converted a recurring question into a policy. A team that asks each time a contractor leaves will eventually ask too late.

4What the output is for

Alongside the terms behind “Seat”, SceneMixer's guides describe the work itself this way:

For places, every photo you add becomes a set the shots can move through, up to four.

SceneMixer, An AI Ad for a Store or a Property — “Can I add several rooms?” (read 2026-10-13)

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)

5Where the sourced wording is

A word page, not an entry in the register: nothing above is attributed to any vendor and nothing above is legal advice. The quoted clauses are on commercial use, the column this phrase turns up in is commercial use from, and the reading rules are on the reading page. Next words: Community licence, Permissive licence, Monthly active users.