Editorial Policy | Happy Horse 2
Every public page on Happy Horse 2, from the home page and pricing to the showcases and these policies, follows the rules below. They exist so that a visitor can tell what the studio itself does, what a third-party engine does, and how sure we are about each statement.
Checking against the live studio
Before a workflow description goes live, someone walks through it in the current interface: uploading a still, choosing between text or image to video, reference-to-video, and first-and-last-frame mode, picking an engine, and reading the credit figure displayed before rendering. If a step on a page no longer matches what the studio shows, the page is wrong and gets fixed, not the other way round.
Sample clips on the site illustrate a single run. Because two renders from an identical photo and prompt rarely match, we present them as examples of a technique, never as the output every user will receive.
Engine specifications and sources
Facts about Veo 3.1, Sora 2, Seedance 1.5 Pro, or any image engine, such as supported durations, aspect ratios, resolutions, or native audio, are taken from the provider's own documentation or release notes whenever those exist. If a claim relies on an outside source in a meaningful way, we name or link it. Model names remain the trademarks of their owners, and Happy Horse 2 is described as an independent studio that routes jobs to those engines, with no link to Alibaba's HappyHorse model.
Speed, quality, and cost comparisons
Statements like "renders faster", "looks sharper", or "costs less per clip" are published as facts only when we can show the method. That means recording the engine and version where known, the source image or prompt, the settings, how many runs were made, the date, and the conditions of the test. Without such a record, the wording stays descriptive and makes no promise. Credit prices quoted in prose must match the figures the studio and the pricing page display at the time of publishing.
When a page gets a new date
The visible updated date changes when something substantive changes, for example an engine joining or leaving the lineup, a revised credit cost, a new input mode, or an edited legal clause. Fixing a typo or adjusting layout does not move the date. Pricing and policy pages are re-read whenever engines, plans, workflows, or legal terms shift.
Reporting an error
If you believe something on the site is inaccurate, write to support@happyhorse2.video with the page address, the exact statement you dispute, and any evidence that supports your view. Reports are investigated, confirmed mistakes are fixed, and the page date is refreshed if the fix alters what the page means.
Use of AI writing tools
Drafts may be outlined, summarised, or polished with AI writing assistants. A human editor still checks the final text against the studio's behaviour and the relevant sources before it goes live, and text produced by a language model never counts as proof that a claim is true.
Who decides
Final editorial calls rest with the Happy Horse 2 team. Sales targets do not override the duty to flag limitations, name third-party dependencies, and mark claims we have not verified. For background on the studio itself, see About Happy Horse 2.