Seedance Input Image Rejected? Sensitive Content and Real-Person Errors

Which Seedance image error did you receive?

The following observed messages are normalized to remove private request IDs and variable array positions:

InputImageSensitiveContentDetected
The request failed because the input image 'content[n]' may contain sensitive information.

InputImageSensitiveContentDetected.PrivacyInformation
The request failed because the input image 'content[n]' may contain real person.

InputImageSensitiveContentDetected.PolicyViolation
The request failed because the input image 'content[n]' may be related to copyright restrictions.

The first names image content; the second points to the real-person branch; the third points to copyright restrictions. None is a file-dimension or expired-URL error. A failure saying "resource download failed" needs a URL-access check instead.

Find the rejected image before replacing references

Check the exact request that failed, including first and last frames, reference images, and assets inserted by your app. The upstream content array can mix media and text: an index is not a universal position in your image picker. If several entries are named, inspect them all.

Record each entry's role and source privately. For a reusable asset, verify the actual returned asset ID, review state, owning account and compatible group/context. Re-uploading the same file creates more work without explaining a content rejection. Changing aspect ratio addresses dimensions, not a content-review reason.

Seedance input image may contain real person

The wording is a classifier warning, not proof of who the person is or a legal conclusion about privacy. A realistic synthetic character can also be flagged. Its being AI-generated does not establish that the selected provider accepts it as an ordinary direct-URL reference.

For a real portrait, obtain the person's authorization and check the APIMaster portrait and material workflow. Availability depends on model, route capabilities and account entitlement. Current documentation distinguishes non-celebrity material review from the celebrity owner-verification flow. Do not start a liveness session just because a non-celebrity photo was rejected.

For a fictional character, retain its creation/source evidence and ask support which review workflow is supported. Do not claim the classifier is definitely identifying a real person. Approval by another platform, account or model does not automatically transfer.

Use an authorized asset that has actually passed review

The supported path is capability discovery → the applicable group/review workflow → asset submission → review query → an Active asset → generation in a compatible context. The material API documentation gives request schemas and the portrait guide explains which workflow applies.

Uploading gives a file URL; submitting material starts review. Neither confirms approval. A batch can partially succeed: inspect usable and failed assets individually. Keep the returned asset_url unchanged and use only approved, accessible assets in the account/context they belong to.

This illustrative generation body assumes asset://asset_example has already been approved for the caller and selected workflow. It is not a working public asset or a way to approve a raw photo:

Prefer the console? Manage authorized reference materials.

{
  "model": "seedance-2.5",
  "prompt": "The person slowly turns toward the camera in natural light.",
  "image_with_roles": [
    {"url": "asset://asset_example", "role": "first_frame"}
  ],
  "aspect_ratio": "adaptive",
  "duration": 5,
  "resolution": "720p",
  "generate_audio": false
}

Asset review and video review are separate. An Active asset is not a promise that every motion, scene or generated output will be accepted. Keep consent and media rights valid for the actual use.

What to do if a legitimate image is still rejected

Ask support to identify the flagged entry and the supported review path. Include the model, UTC time, exact redacted error, public asset/review/task IDs and whether the source is original, licensed or an authorized portrait. Do not publish the portrait, signed download URL, owner-verification link or API key in a forum.

If submission timed out, recover the original receipt before another generation. Portrait requests can use their dedicated saved video-request receipt; ordinary keyed generation uses its documented submission receipt. Follow the recovery guide and the portrait guide for the applicable path. A failed asset review is separate from a failed paid video generation and its billing receipt.

Use Seedance with visible pricing and task receipts

Check Seedance 2.5 pricing, or compare Fast and Mini for a different budget. Then register, create an API key, and use https://apimaster.ai/v1 with the exact model ID, such as seedance-2.5. Read the generation API guide before submitting a paid request.

For a supported request, obtain a non-binding quote before generation and keep the resulting task ID for status and settlement checks. Switching platforms or paying less does not guarantee moderation approval.

Sources and scope

Error meanings were checked against the official ModelArk error catalog on 2026-11-11 and redacted operational error messages. Positions are normalized to content[n]; request IDs and private media are omitted. Examples illustrate response handling, not a new paid generation test. Provider wording, supported assets and billing rules can differ. APIMaster procedures follow its linked current documentation.

Different error? Open the Seedance error index.

FAQ

Why is my AI-generated character flagged as a real person?

The warning can apply to realistic-looking synthetic faces. The error does not expose the classifier's reasoning. Preserve source evidence and ask about a supported review path instead of assuming that any synthetic face is automatically eligible.

Will prompt changes fix a rejected reference image?

They do not change the image's source, review status or authorization. First address the specific image error. A request can separately contain text and output-review issues.

Can I use an asset ID from another service?

Do not assume it is portable. Use assets returned to your APIMaster account within a compatible context. Official owner verification, ordinary asset approval and channel material review are distinct results.