App Store Guideline 1.1.6 explained: False information and prank functionality

Guideline 1.1.6 sits in Apple's Safety section and is most relevant to objectionable content and user safety.

This page summarizes the review risk in practical terms and links to the official Apple source for the exact rule text.

Apple will check whether the submitted app, sample data, screenshots, and moderation model can expose users to content that is unsafe or inappropriate for the App Store.

Apple will check whether the submitted app, sample data, screenshots, and moderation model can expose users to content that is unsafe or inappropriate for the App Store.

Entertainment, parody, social, news, and community apps should make the intended context clear and avoid content patterns that look harmful during review.

If the app hosts dynamic content, reviewer notes should explain safeguards, reporting paths, and how unsafe content is removed.

Screenshots, sample content, onboarding, or demo accounts show unsafe, abusive, misleading, adult, or exploitative material.

The app appears to encourage harmful behavior, illegal activity, harassment, or misleading prank functionality.

The submission relies on a broad disclaimer instead of changing the product behavior or reviewed content.

Replace risky demo content and screenshots with clearly compliant examples.

Add or document moderation, reporting, blocking, safety filters, or eligibility controls where relevant.

Use reviewer notes to point Apple to safeguards and explain the intended content context.

If Apple cited Guideline 1.1.6, reply with the exact change you made and where the reviewer can verify it.

If you believe the app already complies, provide concise evidence, navigation steps, and any supporting documentation instead of a generic appeal.

Keep the tone factual and cooperative. Avoid promising approval or arguing beyond what the submitted build and metadata can prove.