App Store Guideline 1.2: how to pass App Review with user-generated content
Apps with user-generated content often get stuck in App Review on Guideline 1.2. Here is the exact wording, what reviewers ask for in published rejections, and how to build filtering, reporting, blocking and contact details so the reviewer can find them.
If you submit an app with comments, profile photos, chat or posts, sooner or later you meet Guideline 1.2 of the App Review Guidelines. The rule is short, but reviewers check it closely. The good news: the requirements are concrete, and you can tick them off before you submit.
Apple and App Store are trademarks of Apple Inc.
The wording of 1.2
Apple puts it like this (App Review Guidelines, last updated 16 October 2026):
Apps that enable users to create, generate, upload, share, or otherwise contribute content present particular challenges, including intellectual property infringement, nonconsensual intimate imagery, and anonymous bullying. This includes social media, user-generated content platforms, and AI content creation apps. To prevent abuse, such apps must include:
- A method for filtering objectionable material from being posted to the app
- A mechanism to report offensive content and timely responses to concerns
- The ability to block abusive users from the service
- Published contact information so users can easily reach you
Apple sharpened the wording on 16 October 2026. Until then, the guideline spoke of “apps with user-generated content or social networking services” and named intellectual property infringement and anonymous bullying as challenges. Now it describes the activities (“create, generate, upload, share”), lists social media, user-generated content platforms and AI content creation apps, and adds nonconsensual intimate imagery.
A paragraph further down is easy to miss: it is your responsibility to remove content that violates 1.2, your terms of service or your community standards. New since the update: developers who fail to implement appropriate safeguards, or fail to fix violations after Apple points them out, may be considered in violation of the Developer Code of Conduct (Guideline 5.6). That concerns you as a developer, not only the single app. If Apple finds such content, it will ask you to remove it and to provide a plan to improve compliance. Egregious or repeated behaviour can get the app removed from the store and you removed from the Apple Developer Program.
What reviewers ask for in rejections
The guideline is brief. Rejections that developers have published show how reviewers read it. One example from the Apple Developer Forums in November 2025: the published rejection asked the developer to implement these precautions:
- Require that users agree to terms (EULA) and these terms must make it clear that there is no tolerance for objectionable content or abusive users
- A method for filtering objectionable content
- A mechanism for users to flag objectionable content
- A mechanism for users to block abusive users
- The developer must act on objectionable content reports within 24 hours by removing the content and ejecting the user who provided the offending content
A second rejection of the same app added an 18+ age rating, a way for users to immediately remove posts from their feed, and contact information inside the app itself.
A rejection text is not the guideline
The 24 hours and the zero-tolerance terms are not in the wording of 1.2. They come from published rejections. Reviewers ask for them all the same, so plan for both.
Building the four pieces
Filtering before posting
“Filtering objectionable material from being posted” means a check before content becomes visible to others. Common approaches:
- Word lists for slurs, spam patterns and links in comments and usernames.
- Image checks for profile photos and uploads, automated or by a person.
- Approval before publishing for sensitive content, such as the first profile photo in a dating app.
The filter does not have to be perfect, but it has to exist and the reviewer has to be able to see it. Describe it briefly in your App Review notes.
Reporting with timely responses
Every piece of content and every profile needs a report option, usually in the overflow menu. Good reporting flows:
- offer a few clear categories (spam, harassment, nudity, violence, other) plus optional free text,
- confirm receipt to the reporter,
- land in a queue that someone works through every day.
The timely response is the part that shows up in rejections. Decide who handles reports, including weekends, and how fast. The report does not have to go straight from the device to your moderation tool: the app sends it to your backend, and your backend forwards it to your moderation tool. The page on moderation for Flutter apps shows what that looks like in a Flutter app.
Blocking
Blocking is a user feature, not a ban by you. After blocking someone, the user should:
- no longer see the blocked person’s content and messages,
- no longer be contacted or mentioned by them,
- be able to undo the block in settings.
Store blocks on the server, not just in the app, or they disappear after a reinstall. Separately, you need a way to suspend accounts yourself when reports are justified.
Publishing contact information
“Published contact information” means users can reach you without hunting for it. An email address or contact form in the app’s settings and on your support page is usually enough. In one published rejection, Apple explicitly asked for contact information inside the app.
Apps Apple does not want
Guideline 1.2 names apps that do not belong on the App Store and may be removed without notice: apps with user-generated content that end up being used primarily for
- pornographic content,
- Chatroulette-style experiences and random or anonymous chat,
- objectification of real people (Apple’s example is “hot-or-not” voting),
- making physical threats or bullying.
Content from a web-based service may include incidental mature content if it is hidden by default and users can only turn it on via your website.
Creator apps: 1.2.1 and age limits
Apps where a community of “creators” publishes video, articles, audio or casual games fall under 1.2.1. Apple treats that content as user-generated, so 1.2 applies in full. On top, 1.2.1(a) says:
Creator apps must provide a way for users to identify content that exceeds the app’s age rating, and use an age restriction mechanism based on verified or declared age to limit access by underage users.
Showing the reviewer it works
Many 1.2 rejections happen because the reviewer cannot find the features. Guideline 2.1 already asks for demo account details if your app has a login, and a working backend. Use the App Review notes for a short walkthrough:
- A demo account with existing content from other users, so reporting and blocking are visible.
- Where the filter applies, with an example the reviewer can try.
- Where the report button is (“overflow menu on every post and profile”).
- How blocking works and where to undo it.
- How fast you respond and who handles reports.
- Where the terms and contact details are, noting that users accept the terms before their first post.
If your app has accounts, account deletion inside the app is required too (Guideline 5.1.1(v)).
Guideline 1.2 and the EU Digital Services Act
Apps offered in the EU are also subject to the Digital Services Act (DSA). Much of it lines up:
| Apple 1.2 | DSA |
|---|---|
| Reporting mechanism | Notice and action under Art. 16, for every hosting service |
| Timely responses | Art. 16(6): timely, diligent, non-arbitrary and objective |
| Removing content, banning users | Statement of reasons to the affected user under Art. 17 |
| Contact information | Single point of contact for users under Art. 12 |
| Blocking | no equivalent |
| Filtering | not required, but automated filters belong in the transparency report (Art. 15(1)(e)) if you have to publish one |
The DSA goes further in one respect: you must explain decisions and tell affected users about redress. See the guides on notices under Art. 16 DSA and statements of reasons under Art. 17. Google’s rules are compared in the guide on the Google Play user-generated content policy.
How to do this with Limenia
Limenia’s store checklist shows per app what Limenia detects itself: incoming reports, an active webhook, redress information, policies. The rest, such as blocking, contact details and account deletion, you tick off. For filtering before posting, the Pro plan includes review before publishing, for example for profile photos. More on the DSA notice and action page.
Sources
- Apple: App Review Guidelines, 1.2 User-Generated Contentdeveloper.apple.com
- Apple: App Review Guidelines, 5.6 Developer Code of Conductdeveloper.apple.com
- Apple: Guideline 5.1.1(v), account deletiondeveloper.apple.com
- Apple Developer Forums: published Guideline 1.2 rejection text (November 2025)developer.apple.com
- Regulation (EU) 2022/2065 (Digital Services Act), Art. 16 and 17, EUR-Lexeur-lex.europa.eu