Guideline 1.1
Guideline 1.1 - Safety: Objectionable Content in App Marketing
Our Take
Apple is rejecting your app because its marketing materials — specifically the App Store metadata like the description, subtitle, keywords, or promotional text — include terms or imagery that reference objectionable content or services. This doesn't mean your app itself contains objectionable material. The issue is specifically with how it's presented on the App Store. Common triggers include: 1. Description text that mentions adult content, drug use, excessive violence, or other objectionable themes, even in passing 2. References to features that could be used to create or distribute objectionable content 3. Marketing copy that uses provocative or suggestive language to attract downloads 4. Keywords or subtitle text that references objectionable categories The frustrating part is that Apple doesn't tell you which words or phrases are objectionable in their rejection. It's a bit of a guessing game. Apple enforces this because the App Store is meant to be safe and appropriate for a general audience (the storefront itself, not just the app). Apple may have a list internally, but they don't make it public.
Resolution Guide
**Identify the flagged metadata field(s)** — Apple's rejection email usually specifies which field triggered the issue (description, subtitle, keywords, etc.). If not specified, audit all metadata fields.
**Review your app description** — Look for any language that references adult content, violence, drug use, gambling, or other objectionable themes. Even context like "we don't allow adult content" can trigger this rejection because it mentions the term.
**Audit subtitle and keywords** — Remove any keywords that could be associated with objectionable content categories, even if your intent was to differentiate your app from those categories.
**Check screenshots and preview videos** — Ensure no visual content references objectionable material, even in UI text visible in screenshots.
**Rewrite with neutral language** — Replace problematic phrases with neutral alternatives. Instead of saying what your app doesn't do ("no adult content"), focus on what it does do ("family-friendly experience").
**Resubmit with Review Notes** — Explain what changes were made to the metadata and confirm all references to objectionable content have been removed.
Prevention
Example Rejection Email
Consider Appealing
Appeals are rarely successful for this rejection since it's about metadata you control. Instead, revise the flagged metadata fields and resubmit. Only appeal if you believe Apple misidentified standard, non-objectionable language — in that case, quote the specific text and explain why it's appropriate for a general audience.
Before & After
Description: 'Our AI filter blocks all NSFW, adult, and explicit content — keeping your feed clean and safe for work.'
Description: 'Our AI filter ensures your feed stays clean, professional, and appropriate for all audiences.'
What changed: Even mentioning that you block objectionable content uses terms Apple flags. Focus on the positive outcome instead.
Description: 'Create and share any content — we don't censor violence, controversial opinions, or edgy humor.'
Description: 'Create and share content with your community. Express yourself through text, images, and video.'
What changed: Referencing features that enable objectionable content creation is itself a violation. Keep messaging neutral.
Community Solutions · 0
Sign in to share your solution.
More Guideline 1 (Safety) rejections
- 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
- Guideline 1.1.7 - Safety: Exploiting Recent Events or Tragedies