Guideline 1.1.4
Guideline 1.1.4 - Safety: Sexual or Pornographic Content
Our Take
Apple is rejecting your app because it contains overtly sexual or pornographic material. This guideline covers explicit descriptions or displays of sexual organs or activities intended to stimulate erotic feelings. It also applies to 'hookup' apps and apps that may facilitate prostitution, human trafficking, or exploitation. This is a hard line for Apple — there is essentially no path to getting explicit sexual content approved on the App Store. The rejection may be triggered by user-generated content (photos, messages), app-provided media, or even the app's marketed purpose. For dating or social apps, the key distinction is between a dating app (acceptable) and a hookup app with pornographic elements (not acceptable). If your app allows photo sharing, you need robust NSFW detection and content moderation. Web-based content that includes incidental 'NSFW' material can be shown only if it's hidden by default and requires a user toggle on your website (not in the app).
Resolution Guide
Remove explicit content
If the app itself provides sexual content, remove it entirely. There is no age-gating workaround for pornographic material on the App Store.
Implement NSFW detection
For apps with user-generated images, integrate an NSFW detection API (e.g., Apple's own CSAM detection, Google Cloud Vision SafeSearch, or similar) to automatically flag and remove explicit uploads.
Add robust content moderation
Implement user reporting, automated flagging, and human review for any user-generated content that could contain explicit material.
Reframe the app's purpose
If the app is perceived as a hookup/adult app, reposition it as a dating or social connection app with clear community guidelines against explicit content.
Handle web-based content properly
If your app displays web content that may include NSFW material, ensure it's hidden by default and only accessible via a toggle on your website, not within the app.
Prevention
Example Rejection Email
Before & After
User photo uploads are unfiltered, allowing explicit images to be shared in public feeds
All photo uploads pass through NSFW detection API, explicit images are automatically removed, and users who upload them receive warnings
What changed: Apple requires proactive prevention of explicit content, not just reactive removal.
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.6 - Safety: False Information or Fake Features
- Guideline 1.1.7 - Safety: Exploiting Recent Events or Tragedies