Google Play incidental sexual content policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for Google Play user-content apps with primarily non-sexual content and limited incidental sexual material.

Google’s incidental-content allowance has specific conditions. It doesn’t cover an app built around sexual content or one that actively promotes or recommends it. Illegal sexual material and child-endangerment content never qualify as incidental.

Test the default experience

The content must be hidden behind filters that require at least 2 user actions to disable fully. Children must be excluded through appropriate age screening, and the content-rating answers must accurately describe the UGC.

We’d test a fresh account, recommendations, direct links, and remembered preferences. A filter on the feed won’t help if a notification or deep link displays the content immediately.

Correct access and promotion

Remove prohibited material, stop active sexual-content promotion, and enforce the required default filtering and age controls. Maintain the broader UGC moderation requirements.

Test the corrected paths with safe samples and fictional accounts. Give Google the default state, steps to change it, and age-screening behavior. An app that becomes primarily a destination for objectionable content can lose eligibility despite having filters.

Messages this guide can help with

Incidental sexual content; Incidental sexual content policy violation; Incidental sexual content rejection; Incidental sexual 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