# Guideline 1.2 - Safety: UGC App Used Primarily for Objectionable Content

**Guideline:** 1.2 · **Store:** Apple App Store · **Severity:** high · **Fix difficulty:** hard · **Typical turnaround:** 1-3 days

Canonical URL: https://appstorereject.com/rejections/apple/1/guideline-12-safety-ugc-app-used-primarily-for-objectionable-content

## Description

Apple is rejecting (or removing) your app because it has become primarily used for pornographic content, anonymous random chat (Chatroulette-style), objectification of real people ('hot-or-not' voting), physical threats, or bullying. Unlike the missing-features rejection, this is about the app's actual usage pattern, not a missing checklist item. This is a much more serious rejection than the missing UGC features rejection. Apple may remove these apps 'without notice,' meaning you might not get a standard rejection — the app could simply be pulled from the store. The distinction is important: having moderation features doesn't protect you if the app's primary use case is objectionable. If the majority of user activity in your app is explicit content, anonymous harassment, or objectification, Apple will reject it regardless of how robust your moderation is.

## Common variations

- App is being used primarily for pornographic content
- App enables Chatroulette-style random or anonymous chat experiences
- App facilitates objectification of real people (hot-or-not voting)
- App is used primarily for making physical threats or bullying
- App may be removed without notice due to objectionable usage

## Example rejection email

```
Guideline 1.2 - Safety - User-Generated Content

Upon further review, we found that your app is being used primarily for objectionable content, including [pornographic content / anonymous bullying / objectification of real people]. Apps that are used primarily for such purposes do not belong on the App Store and may be removed without notice.

Next Steps:
Please make significant changes to your app to ensure it is not used primarily for objectionable purposes. You may want to reconsider your app's core functionality and user experience.
```

## Resolution steps

## Quick Assessment
- **Risk level:** High — app may be removed without standard review process
- **Resolution path:** Major app changes required, then resubmit
- **Typical turnaround:** 1-3 days minimum

## The Fix

01. **Assess the core problem** — Is the app's design inherently facilitating objectionable use? Anonymous random chat, unmoderated photo rating, and open live video are high-risk patterns.

02. **Add identity and accountability** — Remove anonymity. Require account creation, and consider requiring profile photos or verification. Users are less likely to post objectionable content when they're identifiable.

03. **Implement proactive moderation** — Move from reactive (wait for reports) to proactive (automated scanning, AI moderation, human review of flagged content). Apple wants to see you're ahead of the problem.

04. **Restrict high-risk features** — Consider limiting random video chat, removing anonymous messaging, or adding delay/review to photo sharing.

05. **Provide usage data to Apple** — Show moderation logs, content removal rates, and evidence that the majority of usage is appropriate.

## Prevention
- Design with abuse prevention as a core feature, not an afterthought
- Monitor actual usage patterns, not just intended use
- Consider how anonymous features will be misused before building them

## Appeal guidance

Only appeal if you can demonstrate with data that the app's primary use case is NOT objectionable — e.g., content moderation logs showing the vast majority of content is appropriate, and objectionable content is a small percentage that is being actively removed.

## Before / after examples

**Before:** Anonymous random video chat app where 60%+ of sessions involve explicit content despite having a report button
**After:** Video chat now requires verified accounts, AI-powered real-time nudity detection pauses streams, and users must complete a brief profile before matching
**Why it works:** Structural changes to prevent objectionable use are required — moderation features alone aren't sufficient when the primary usage pattern is objectionable.

## Common questions

**Can you appeal a 1.2 rejection?**

Only appeal if you can demonstrate with data that the app's primary use case is NOT objectionable — e.g., content moderation logs showing the vast majority of content is appropriate, and objectionable content is a small percentage that is being actively removed.

**How long does this typically take to fix?**

Typical turnaround is 1-3 days (difficulty: hard). After resubmission, most re-reviews complete within 24-48 hours.

---
*Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=guideline-12-safety-ugc-app-used-primarily-for-objectionable-content*