Google Play: declare AI-generated store images and videos, per asset
Play Console asks you to declare AI-generated listing and promo images and videos, one asset at a time. How the checkbox works and what to log for Sume clips.
Google Play has a declaration for AI-generated assets, and it works one asset at a time. Play Console Help, read on 2026-10-05, says developers declare AI-generated content for images and videos used in store listings, promotional content and YouTube videos. The help page says each item must be declared on its own merits.
The mechanism is a standardised checkbox in the creation flow for Store listings or Promotional content. The page's wording is that regulations require AI-generated content to be labelled under certain circumstances.
How it works
| Question | Answer on the page |
|---|---|
| Which assets? | Images and videos in store listings, promotional content, YouTube videos |
| How declared? | A checkbox in the creation flow, or in the Asset library |
| Detected or self-declared? | Self-declared by the developer |
| What happens? | Declared assets are AI-labelled on Google Play and other surfaces |
| Dates? | The page gave no deadline |
Applying it to a Sume-made preview video
A preview video or promo clip made with the Sume video API is an AI-generated asset in the sense the page describes. Tick the declaration for that specific video; do not assume a declaration on one screenshot covers the video.
Because the model is per asset, build a small ledger: asset file name, asset type, whether you ticked the AI box, and the Sume job id. Sume jobs accept your own metadata, stored on the job and not sent to the provider, so you can tag the listing and the asset slot there.
Mixed assets
Because the declaration is a self-certification and the label appears on the store, a wrong "no" is your risk and a safe "yes" costs one label. Re-read the page before each release; I only describe it as of 2026-10-05. Sume's docs describe a metadata field on video, image and music jobs that Sume stores on the job and does not send to the provider. I found nothing in the docs about Sume adding, keeping or removing C2PA credentials, watermarks or platform labels, so treat that as undocumented and check the delivered file.
- A real screen recording with a generated voice-over: declare it if the generated part is the content people will hear.
- A real gameplay clip cut with a non-generative editor: not the target of the declaration.
- A feature graphic from an image model: it is an image used in your store listing, so it belongs in the same ledger.
Sources
Related posts
More in Use cases
- Google Vids Omni edits: color grade and restyle prompts for Sume
Google Vids fixes color grading and restyles video with Omni, but not in the EEA, UK, Switzerland, Texas or Illinois at launch. Try edit prompts on Sume.
- GPT Image 2.5 21:9 first frame, then Seedance 2.5: a still for $0.01
A 2560x1088 GPT Image 2.5 still costs $0.0109 at medium quality and $0.0431 at high. Use it as the first frame of a 21:9 Seedance 2.5 clip on Sume.
- 48% thought Griffin was real: add a disclosure line to your clip
Tavus reports 48% of people took Griffin for a person after a one-minute call. If viewers cannot tell, label the clip: burn a disclosure line with caption cues.
- Guard a Sume run's text output with a yes/no model before you post it
Read output from a completed Sume run, ask a small decision model whether it is safe to publish, and treat a degraded outcome or null output as a hard stop.
Written by Sume