App Store Guideline 1.2 Rejection: User Generated Content

What guideline 1.2 actually says

Here is the text from Apple's App Review Guidelines. Apps that let users "create, generate, upload, share, or otherwise contribute content" must include:

• 1. A method for filtering objectionable material from being posted to the app
• 2. A mechanism to report offensive content and timely responses to concerns
• 3. The ability to block abusive users from the service
• 4. Published contact information so users can easily reach you

What rejection messages ask for on top of the guideline

The rejection message you get often asks for more than the guideline does. On the Apple Developer Forums, founders quote rejection messages that also ask them to do the two things below. So plan for four features and two rules, and have all six in place before you resubmit.

• Make users agree to terms (EULA) that say there is no tolerance for objectionable content or abusive users.
• Act on reports within 24 hours by removing the content and ejecting the user who posted it.

Why Apple rejects apps with user generated content

Apple doesn't reject your app for having user content. It rejects it because the reviewer couldn't find the safeguards in the build they tested. The cases quoted on the forums usually come down to one of these:

• Reporting only. You have a "Report" button but no filter and no block. One developer asked on the forums if a reporting system alone was enough. Going by the rejection wording, it isn't.
• Hidden features. Block exists, but only in a settings screen the reviewer never opened.
• No terms at sign up. Your terms of service link sits in the footer, but users never agree to them.
• Contact info only on your website. One rejection quoted on the forums asked for contact details inside the app itself.
• Missing pieces in a later round. The same thread shows a second rejection that also asked for an 18+ age rating and a way for users to remove their own posts right away.

The hard line: apps that don't belong on the App Store

Apple says apps "used primarily for" pornographic content, Chatroulette-style experiences, random or anonymous chat, "hot-or-not" voting, threats or bullying "do not belong on the App Store." If your core idea is anonymous chat with strangers, moderation features won't save it. Change the concept before you build.

The 4 required features and the 2 rules Apple adds

You don't need a big trust and safety team for a first version. Here is what each feature has to do, what the reviewer checks, and the smallest version that works.

• Filter. What the reviewer checks: objectionable text or images can't be posted freely. Smallest version for v1: a word list on posts, comments and usernames, plus image moderation on uploads if you allow photos.
• Report. What the reviewer checks: every piece of content and every profile can be flagged. Smallest version for v1: a "Report" option on each post, comment, message and profile, with a short list of reasons.
• Block. What the reviewer checks: a user can stop another user from reaching them. Smallest version for v1: "Block user" on profiles and in chat. Blocked users' content disappears from the feed.
• Contact. What the reviewer checks: users can reach you from inside the app. Smallest version for v1: a support email or contact form in Settings or Help.
• Terms (EULA), a rule from rejection messages. Users agree to zero tolerance before they post. The smallest version is a checkbox at sign up, linking to terms that say this in plain words.
• 24 hour action, a rule from rejection messages. Reports reach a human who can act. The smallest version is an email alert or an admin list of reports, with buttons to remove the content and ban the user.

Filtering objectionable content

A filter runs before content goes live. For a text-only community, a blocklist of words on posts, comments and display names is a common first step. If users upload photos, check them on upload too. That matters even more if your app uses AI to generate images, since 1.2 now names AI content creation apps directly.

Reporting and the 24 hour response

A report button is useless if nobody reads the reports. Send every report somewhere a person checks daily: an email inbox, a Slack channel, or a simple admin page. That person needs two actions: remove the content, and suspend the account. If you're a solo founder, that person is you.

Blocking abusive users

Blocking should work both ways. The blocked user can't message you or see your profile, and their posts vanish from your feed straight away. Put the button where the problem happens: on the profile and inside the conversation.

Published contact information

Add a "Contact us" or "Report a problem" item to your settings screen, with a real email address. It takes minutes. It also covers the case quoted on the forums, where Apple asked for contact details inside the app and not only on the website. Not sure what's missing from your build? Book a call and send us your rejection message. We'll point out each gap before you spend another review cycle.

How to fix a guideline 1.2 rejection and resubmit

Work through it in this order:

• 1. Read the rejection line by line. List every precaution Apple names. Treat each one as a ticket.
• 2. Build what's missing. Use the features and the two rules above. Don't stop at the items you think matter most.
• 3. Make it findable. Put report and block on the content itself, not three screens deep.
• 4. Update your terms. Add the zero tolerance wording and a required checkbox at sign up.
• 5. Check your age rating in App Store Connect so it matches the content users can post.
• 6. Give the reviewer a path. Provide a demo account with posts already in the feed, so they can report and block something in the first minute. Empty test accounts cause problems under guideline 2.1 too.
• 7. Reply in App Store Connect before you resubmit.

What to write to App Review

Keep the reply short and say where each feature is. For example: "We've added the precautions required under guideline 1.2." Then list each one. Only write the 24 hour line if you can really keep that promise. Apple says developers who fail to remove violations after notice may be in breach of the Developer Code of Conduct.

• 1. Terms: users must accept our terms at sign up. They state we have no tolerance for objectionable content or abusive users.
• 2. Filtering: posts, comments and usernames are filtered before publishing.
• 3. Reporting: tap the three dots on any post, comment or profile, then Report.
• 4. Blocking: open any profile, tap the three dots, then Block user.
• 5. Contact: Settings > Contact us.
• 6. Moderation: we review reports within 24 hours, remove the content and remove the user who posted it.
• Demo account: the login details are in the review notes.

Pre-submission checklist for social and community apps

Run this before you submit. It goes further than the forum threads because it includes what came up in the second rejection round quoted there.

• Every post, comment, message and profile has a Report option.
• Every profile and chat has a Block option, and blocked content disappears at once.
• Text and uploaded images go through a filter before going live.
• Users can delete their own posts right away.
• Sign up requires accepting terms with zero tolerance wording.
• Contact details are visible inside the app.
• Reports reach a human, with remove and ban actions.
• Age rating matches what users can post.
• If you host creator content, users can spot content above the app's age rating, and access is limited by age (guideline 1.2.1(a)).
• Demo account has real content to report and block.

When to bring in a developer

If your app came out of an AI builder, moderation is often the missing layer: the feed works, but there's no admin side, no report list and no ban action. Our AI prototype to production service covers this kind of gap, and our Lovable and AI builder guides explain the other rejections these apps tend to hit. If you're starting from scratch, plan moderation into v1 from day one. That costs less than adding it after a rejection. See what a focused first version includes on our MVP development page. We give you a fixed quote before we start, design is included, the code is 100% yours on your GitHub, and you get 2 weeks of fixes after launch. Ready to get past review? Book a call. It's a free 30-minute call about your app and your rejection.

What is guideline 1.2 user generated content?

It's the App Store rule for apps where users post, upload, share or generate content that other users see. It names social media, user-generated content platforms and AI content creation apps. These apps need a content filter, reporting, user blocking and contact details users can find.

Is a report button enough to pass guideline 1.2?

No. Apple lists four safeguards: filtering, reporting, blocking and contact information. Rejection messages also ask for terms with zero tolerance wording and action on reports within 24 hours. You need every item named in your rejection.

Does guideline 1.2 apply to apps with only chat or comments?

Yes. Any feature that lets one user show content to another counts, including comments, chat, reviews and profile photos. If users can only see their own content, the rule usually doesn't apply.

Do I need a full moderation team to pass App Review?

No. Apple needs to see that reports reach someone who can remove content and ban users quickly. For a small app, that can be the founder checking an admin list or an email alert every day.