Guideline 1.2
Guideline 1.2 - Safety: User-Generated Content Missing Required Features
Our Take
Apple is rejecting your app because it includes user-generated content (UGC) or social networking features but is missing one or more of the four required safety features. This is one of the single most common App Store rejections. Apple requires ALL four of the following for any app with UGC: 1. A method for filtering objectionable material from being posted 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 This rejection catches many developers because any form of user interaction counts as UGC — comments, reviews, photo uploads, profile bios, chat messages, forum posts, or even custom usernames. If users can post anything that other users can see, you need all four features. The rejection is usually straightforward and not a judgment call — Apple is checking a literal checklist. If any one item is missing, you'll be rejected. The fix is mechanical: implement the missing feature(s) and resubmit.
Resolution Guide
Implement content filtering
Add a profanity/keyword filter on text input. For images, add NSFW detection. This doesn't need to be perfect — Apple wants to see you have a system in place.
Add a report button
Every piece of user content (comments, posts, images, profiles) needs a visible 'Report' option. Include a reason selector (spam, offensive, harassment, etc.) and ensure reports are stored and can be actioned.
Add user blocking
Users must be able to block other users. Once blocked, the blocked user's content should be hidden from the blocker. This needs to be accessible from the other user's profile or from any piece of their content.
Add contact information
Display a support email or contact form in the app's settings or about screen. This must be a real, monitored contact method — not just a website link.
Document everything in Review Notes
Tell Apple exactly where each feature is: 'Report button is on each post (tap ... menu), Block is on user profiles, Contact us is in Settings > Support, Content filter uses [approach].'
Prevention
Example Rejection Email
Before & After
Social app with user posts and comments but no report button, no block feature, and no published contact info
Every post/comment has a Report option, every user profile has a Block button, Settings screen shows support email, and a keyword filter screens new posts
What changed: All four required UGC safety features must be present and accessible.
Community Solutions · 0
Sign in to share your solution.
More Guideline 1 (Safety) rejections
- Guideline 1.1 - Safety: Objectionable Content in App Marketing
- Guideline 1.1.1 - Safety: Defamatory or Discriminatory Content
- Guideline 1.1.2 - Safety: Realistic Violence or Encouragement of Violence
- Guideline 1.1.3 - Safety: Weapons and Firearms Content
- Guideline 1.1.4 - Safety: Sexual or Pornographic Content
- Guideline 1.1.6 - Safety: False Information or Fake Features