AI Video Rated

What each video generator's own policy lets you put on screen

Policy questions people search, answered from each vendor's rules

Each page takes one policy question and reads the vendors' own texts for it: what the enforcement section states, where an appeal is published, which exceptions exist, and where the consent burden lands. Nothing here is advice, and every quote carries the page and date it was read from. As of 2026-10-13.

What feeds a page in this columnA page here is built from three sources: the vendor's own policy text read with its section and date, the counts and short quotations collected from one subreddit, and this file's own tool entries read the same way as everything else.The vendor's textTerms, usage policies andmoderation pages, in their ownwording.A quoteFiled with its sectionand dateOne subredditPost counts, comment mentionsand short quotations.CountsCited to the subredditand the dayThis fileTool entries read the same way,absences included.A rowComparable across toolsOne page in the columnWhere every line on the page comes from
Fig. 1 The first source decides what a page can assert; the other two are what it is set beside.

The four pages here start from the moments a production cannot script around: an account suspended mid-project, a prompt refused without a clear clause, a search for a service that advertises fewer restrictions, and a face that has to appear in advertising with the paperwork in order. Each question is answered the same way — by reading what the vendors publish, quoting it, and dating it. The first two begin, for instance, in Runway's usage policy and Kling's user policy.

Three kinds of material sit behind every page. The first is the vendor's own text: terms of service, usage and community policies, moderation pages, each quoted with the section it came from and the day it was read. The second is the community material collected for one subreddit — post counts, comment mentions and short quotations, cited to the subreddit and the day, never to a person. The third is this file's own entries, which include SceneMixer like any other tool: its published terms are the one place across these pages where the cost of a refusal is written down, since tasks blocked by content moderation are refunded automatically.

What the column will not do is act as a workaround. It does not test filters, rank them, or describe how to get past one; a policy question is answered from policy text or it is answered as an absence. Where a vendor writes no exception, states no appeal and prices a refusal, all three are recorded as they stand, and the tool pages behind each entry carry the same rows in full.

1The pages in this column

  • Higgsfield influencer content — the consent sentence, the moderation clause it sits beside, and the counted threads about whether this work pays.
  • Prompt flagging — the lettered restrictions Kling publishes, the appeal section folded into the same document, and how the CapCut-family terms word a suspension.
  • Runway account bans — what Runway's usage policy prints about enforcement, the one appeal address in it, and the community posts counted beside it.
  • Unfiltered services — the exceptions a few texts publish, the two platforms that sell access across models, and what the file records about the cost of a refusal.

The full register of texts is on the policies page, and how a quote becomes a row is set out on the method page. The policy quotations were read on 2026-09-25 and the community numbers were collected on 2026-10-14.