Google Play user-generated content policy: what your app needs
Google Play's user-generated content policy is more specific than Apple's Guideline 1.2: it says, by type of app, whether you need reporting, blocking or both. Here is what applies, what changes for incidental sexual content, and how it compares with Apple.
If you publish an app with comments, chat or profiles on Google Play, it has to meet the User Generated Content policy. It covers any content users contribute that at least some other users can see or access. Apps that are only a client for such a platform are covered as well.
Google Play is a trademark of Google LLC.
The three core requirements
Google asks for “robust, effective, and ongoing UGC moderation”. The policy lists four points, which boil down to three requirements:
1. Terms before the first post. Users must accept the app’s terms of use or user policy before they can create or upload content. Those terms define objectionable content and behaviour in line with Google Play’s Developer Program Policies, and prohibit it.
2. Moderation with in-app reporting and blocking. Moderation must be reasonable and consistent with the type of content your app hosts. That includes an in-app system for reporting and blocking objectionable content and users, and taking action against content or users where appropriate.
3. No bad incentives from monetisation. You need safeguards so that in-app monetisation does not encourage objectionable behaviour. One violation the policy names: paid features that principally encourage sharing objectionable content.
The policy also lists typical violations: insufficient safeguards against threats, harassment or bullying, particularly towards minors, and apps that continually fail to address user complaints about objectionable content.
What applies to which app type
Unlike Apple, Google says outright that different apps need different levels of moderation:
| App type | Example | Required in the app |
|---|---|---|
| A specified set of users, identified by verification or offline registration | an app used only within one school or company | report content and users |
| Features for one-to-one interaction with specific users | direct messages, tagging, mentions | block users |
| Publicly accessible content | social networking apps, blogger apps | report users and content, block users |
| Augmented reality | AR content anchored to places | moderation covering objectionable AR content and sensitive anchor locations |
If your app combines these, say a public feed plus direct messages, every matching row applies.
Child Safety Standards for social, dating and anonymous chat
Anonymous and random chat apps, and apps in the Social and Dating categories, must also meet the Child Safety Standards policy: published standards against child sexual abuse and exploitation (CSAE), an in-app feedback mechanism, addressing child sexual abuse material (CSAM), compliance with child safety laws, and a child safety point of contact. According to Google, this applies even if the app is meant only for adults. Separately from the store rules, Art. 28 DSA applies to online platforms that minors can use; see protecting minors under Art. 28 DSA.
Incidental sexual content: filters and age screening
In apps that mainly offer non-sexual content and do not actively promote or recommend sexual content, Google allows “incidental” sexual content. All of these conditions must then be met:
- The content is hidden by default behind filters that take at least two user actions to disable completely, such as an obscuring interstitial or a safe search setting.
- Children, as defined in the Families policy, are explicitly kept out by age screening, such as a neutral age screen or a system appropriate under applicable law.
- You answer the user-generated content questions in the content rating questionnaire accurately.
Sexual content that is illegal, and child endangerment content, is never “incidental” and is not permitted. Apps whose primary purpose is objectionable user content, that end up used mainly for it, or that gain a reputation for it, are removed from Google Play.
Comparison with Apple 1.2
If you ship on both stores, build the stricter version once. The differences at a glance:
| Google Play | Apple 1.2 | |
|---|---|---|
| Terms before posting | explicitly required | asked for in published rejections, not in the wording |
| Filtering before posting | not in general, only for incidental sexual content | required |
| Reporting | in-app, depending on app type | required, with timely responses |
| Blocking | in-app, for one-to-one contact and public content | required |
| Contact details | not in this policy (child safety contact for social and dating) | required |
| Monetisation | safeguards against bad incentives required | not in 1.2 |
| Response time | no deadline stated | “timely”, 24 hours in rejection texts |
| Account deletion | separate policy | Guideline 5.1.1(v) |
The Apple side is covered in detail in the guide on App Store Guideline 1.2.
Account deletion
If your app lets users create an account, Google’s account deletion policy requires an in-app path to delete the account and its data, plus a web link where users can request deletion without the app. You delete the user data associated with the account. Data you need to keep for limited reasons, such as fraud prevention or legal obligations, you may retain if you disclose it. This matters for moderation: decide which moderation records you still need after a deletion, for example to handle appeals, and for how long.
And the EU Digital Services Act?
Apps offered in the EU also fall under the Digital Services Act. Reporting and acting map closely to notice and action under Art. 16 and statements of reasons under Art. 17; see the guide on notices under Art. 16 DSA. For how bans take effect in your backend, see reporting and banning users with Flutter and Firebase and banning users in Supabase.
How to do this with Limenia
Limenia’s store checklist covers Google Play’s policies on user-generated content and account deletion for each app. What Limenia detects itself, such as incoming reports, an active webhook, redress information and policies, the checklist shows on its own. The rest, such as blocking and account deletion, you tick off. More on the DSA notice and action page.
Sources
- Google Play Console Help: User Generated Contentsupport.google.com
- Google Play Console Help: Child Safety Standards policysupport.google.com
- Google Play Console Help: account deletion requirementssupport.google.com
- Apple: App Review Guidelines, 1.2 User-Generated Contentdeveloper.apple.com