Legal
Disclaimer
What BountEx Motion does, what it does not do, and what stays your responsibility. The short version: it orchestrates a build on your machine — we never render it for you in the cloud — and the final judgement about the film is yours.
Last updated: · Operated by BountEx Labs, LLC
This is a template. It has not been reviewed by counsel.
The text below was written by the people who build the product so that nothing about the subscription is hidden, but it is a working draft, not a lawyer-reviewed agreement. Before it is relied on as final it must be reviewed and adapted by qualified counsel in the jurisdiction BountEx Labs, LLC operates from — including the governing-law clause, which is a placeholder. Questions, or a correction you think we owe you: Telegram @bountexlabs.
1. What the software does
BountEx Motion is an orchestration layer. It inspects your material, interviews you, decides a story with you, writes a brief and a production prompt, storyboards the film, writes composition source, drives a renderer, and then runs an independent critic pass over the result.
The build and the render happen on your machine, through the HyperFrames toolchain you install and run yourself. We do not render video in the cloud, we do not host your assets, and we do not upload your project. Nothing about your footage, your briefs, your source files, or your renders is transmitted to us.
2. Output quality depends on your inputs and your review
The workflow is a method, not a guarantee. What it produces depends on the material you give it — your product, your assets, your references, your brand rules — and on the decisions you approve along the way. Two people can run the same workflow on the same product and get films of very different quality, because the inputs and the approvals were different.
It also depends on your own final review. The workflow is built to keep facts, inferences, and unknowns apart and to refuse to invent claims, and it finishes with a written list of what a human should check personally. That list exists because a machine should not sign off on your brand claims, your legal position, or your taste.
The critic loop improves a film against a written bar; it does not make the film objective, and it cannot know something you never told it.
3. No guarantee of a commercial result
We do not promise, and you should not expect, any particular commercial outcome: no conversion rate, no revenue, no view count, no virality, no client win, and no award. Marketing pages elsewhere on this site describe what the workflow does and how it differs from a generator or an agency; they are descriptions, not forecasts.
Any example, screenshot, or walkthrough we publish is illustrative of the process. It is not a promise that your film will look like it, and it is not evidence of a result you will get.
We also do not guarantee that a film will pass any particular platform review, advertising standard, or regulator’s requirements. That depends on content and jurisdiction, and it is your call before you publish.
4. You are responsible for what you publish
You are the publisher. That means you are responsible for the factual accuracy of claims in the films you release, for holding the rights to the footage, logos, music, voices, and trademarks you supply, and for complying with advertising, disclosure, and accessibility rules that apply to you.
The workflow helps by keeping facts and inferences apart and by producing a human-review checklist. It cannot verify a claim it was not given evidence for, and it cannot clear rights on your behalf. If a film makes a claim about your product, you are the one making it.
Where a film features a real person, a customer, or a partner, get their permission before publishing. Where output includes AI-generated media, disclose it if the law or the platform requires it.
5. Third-party tools are not ours
The workflow sits on top of products we do not own and do not resell. Each is governed by its own terms, and none of them is affiliated with, endorsed by, or sponsored by BountEx Labs.
HyperFrames
The composition and rendering toolchain the workflow drives. It is a separate product with its own licence and its own release cycle.
FFmpeg
Used for encoding, muxing, and audio measurement. FFmpeg is distributed under its own licence, and build-dependent licensing is your responsibility if you redistribute a binary.
Chrome and Chromium
The headless browser that draws composition frames on your machine.
The AI coding tools
Claude Code, Cursor, Codex CLI, OpenCode, GitHub Copilot, Antigravity, and Kimi Code are third-party products. You need your own account and subscription with whichever you use, and their terms govern what you do inside them.
6. Your machine has to be able to do the work
Building and rendering requires Node.js 22 or newer, FFmpeg on your PATH, and a Chrome or Chromium install, on a machine with enough CPU, memory, and disk for the film you are making. A machine that cannot run those tools cannot render, and no amount of subscription changes that.
Renders take time proportional to length, resolution, and complexity, and they use your electricity and your hardware. Repeated rendering wears hardware like any other heavy workload.
7. Limits of AI-assisted output
AI systems can be confidently wrong. The workflow is designed around that — it separates fact from inference, refuses to invent numbers and customers, and puts a fresh critic after every correction pass — but it cannot eliminate the risk. Review before you publish, especially anything factual, legal, financial, medical, or safety-related.
Nothing the workflow produces is legal, financial, medical, or other professional advice, and nothing on this site is either.
We do not warrant that output is free of third-party rights claims, particularly where you supplied reference material or asked for a style that resembles an existing work. Style is not protectable in most jurisdictions and copying is, and the line between them is your judgement call.
8. Warranty and liability
This page is a plain-language summary. The binding terms on warranty, limitation of liability, and what happens when things go wrong are in the Terms of Service, which also states that the service is provided "as is" and that our aggregate liability is capped at the amount you paid in the preceding twelve months.
9. Contact
Questions about any of the above, or something on this page you think is wrong: Telegram @bountexlabs. BountEx Motion is operated by BountEx Labs, LLC.