SEEDANCE2.5 VIDEO

Make the evidence better

Feedback and rollout corrections

The fastest useful report includes the affected URL, product surface, country or region, observation date, and what the interface actually showed.

Send a structured report

This page does not pretend to submit a server-backed form. Use the button below to open a prefilled email in your mail app.

Email a structured report

What to include

  • Rollout correction: surface, country, account type, model label, and date.
  • Factual correction: the exact sentence and a first-party source.
  • Tool problem: browser, device, action, expected result, and observed result.
  • Accessibility issue: assistive technology, keyboard path, and blocked task.

What not to send

Do not email passwords, session links, API keys, private prompts, unreleased media, identity documents, or third-party personal data. A redacted screenshot is usually enough to explain an interface state.

Response expectations

We prioritize broken core flows, incorrect access claims, security reports, and accessibility barriers. A report is not proof that a product is universally available; we verify the affected surface before updating the status table.