Google Play AI content policy: the in-app report button
Google Play says apps that generate content with AI need in-app reporting or flagging that works without leaving the app. What that means for an AI video app.

Yes. Google Play's AI-Generated Content policy says apps that generate content using AI must contain in-app user reporting or flagging features, so users can report offensive content to developers without needing to exit the app. Image or video generated from text, image or voice prompts counts as AI-generated content.
From the Google Play policy page, read 2026-10-01. The requirement sits in your app, not in the generation API behind it; this post covers what to wire up when that API is Sume.
What does the policy require?
Apps must comply with existing developer policies, including preventing generation of restricted content such as content that facilitates the exploitation or abuse of children, and content that enables deceptive behavior. The page adds that developers should use user reports to inform content filtering and moderation.
| Item | What the page says |
|---|---|
| Counts as AI content | Image or video generated by AI from text, image or voice prompts |
| Reporting | In-app reporting or flagging, without exiting the app |
| Use of reports | Inform content filtering and moderation |
| Also applies | Existing Google Play Developer Policies, incl. restricted content and deceptive behavior |
What do I need to store to act on a report?
A report is only useful if it points to a specific output. Sume's runs docs say to log the request_id, and that media URLs are durable media.sume.com HTTPS URLs that "do not expire" and are public to anyone holding the URL. Save the job id, the output URL and the user id in your own database when you show a result, so a flag from the app maps to one record.
Which features need extra care?
Anything involving real people's faces. Avatar Face Swap 1.0 is a Beta endpoint, and video_url must be a fetchable public HTTPS video URL. An app that lets users submit arbitrary source videos should treat reports on those outputs as a priority. See face swap versus avatar talking video for the choice.
Does a public URL change the moderation story?
It can. Because a durable URL is public, removing an item from your app does not remove the file from media.sume.com. The docs suggest proxying or copying media when you need per-customer access control, which gives you a place to enforce takedowns.
What should I do before submitting the app?
Add a report action on every generated result screen that works in place, store the job record behind each result, and decide who reviews reports. Check the live policy page when you submit. This is not legal advice.
Sources
Related posts
More in Developers
- Google Vids caption font, position, animation: Sume design overrides
Google Vids lets you change caption font, position and animation. Sume's caption overrides cover colour, size, placement, phrasing and motion, not a Latin font.
- Goose MCP HTTP retries and Sume paid calls: reuse the key
When goose retries an MCP HTTP call to Sume, the same idempotency_key keeps a paid generate call a dedup, not a second job. Check status before resubmitting.
- GPT-5.5 retires Oct 14 in Codex: what to change for Sume
Codex retires GPT-5.5 on October 14, 2026. A Sume server entry names no model, and Agent Completions only accepts sume-agent, so check your own settings.
- gpt-image-2.5-flare-2026-09-08 on Sume: use openai/gpt-image-2.5
OpenAI lists the snapshot gpt-image-2.5-flare-2026-09-08. Sume documents catalog slugs, so send openai/gpt-image-2.5 and check /v1/images/models for ids.
Written by Sume