Seedance content policies
Is the Seedance API uncensored?
Creative freedom does not mean moderation-free access. Know the provider requirements before you integrate or submit a reference.
Updated · Provider requirements, not an approval guarantee
Are platform policies and model policies the same?
No. JMovie API controls customer access, Key budgets and task accounting. BytePlus controls the available model’s content and reference requirements. A valid Key, funded wallet or approved asset does not guarantee that every generation request will be accepted.
Is the Seedance API uncensored?
We serve the uncensored creative market, but Seedance is not moderation-free. BytePlus content policies apply to prompts, reference assets and generated outputs. JMovie API does not bypass provider restrictions.
What happens if the provider rejects my request?
Provider rejection codes such as PROHIBITED_CONTENT remain visible. Correct the input or references rather than resubmitting the same rejected content. A lost response is an unknown result, not proof of rejection or a reason to automatically generate again.
Can I use references of real people?
Only use material you are authorized to use. Local file verification is not supplier approval. Where the provider requires an approved library asset, it must be Active and owned by your API customer. Biometric enrollment is a separate opt-in authorization flow, not an approval bypass.
Read the provider requirements
BytePlus service-specific terms · BytePlus reference asset guide
See reference validation and error handling in our docs
Working in a production team? Read the workspace policy guide