Google Play user-generated content policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for Google Play apps with user posts, messages, shared media, or access to a user-content platform.

A report button is useful only if someone can act on the report. Google’s UGC policy requires ongoing moderation, accepted terms before content creation or upload, rules defining prohibited behavior, and controls suited to the interaction.

Match controls to the experience

Public communities need in-app reporting of users and content, plus user blocking. One-to-one interactions need blocking. Restricted communities, such as a verified school group, still need in-app reporting. We’d test with two accounts and follow a report through to the person handling it.

For AR content, consider both the content and where it is placed, such as private or restricted locations. Also check whether paid rewards encourage objectionable behavior.

Repair the process

Add missing controls, remove offending material, and make moderation responsibility clear. Test blocked-user behavior and new uploads, not only the button’s appearance. If sexual content is incidental, check the separate incidental-content conditions.

Give Google the terms acceptance, reporting and blocking routes, and the handling process. A community policy alone doesn’t show that the app follows it.

Messages this guide can help with

User-generated content; User-generated content policy violation; User-generated content rejection; User-generated content denied

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit a Google Play release with working review access