Guideline explainers

App Store Guideline 5.6.4 explained: App Quality

Guideline 5.6.4 is an App Review legal rule about app quality. For iOS developers, the practical risk is usually not the guideline number itself; it is whether the submitted build, product page, screenshots, policies, and review notes make compliance easy for Apple to verify. Use this explainer to turn the rule into a pre-submission checklist, a resubmission fix plan, and a concise reviewer reply for user-generated content and moderation.

Developers searching for App Store Guideline 5.6.4 help, rejection causes, or fix guidance. Guideline 5.6.4 Official Apple source

What this guideline means in practice

Guideline 5.6.4 sits in Apple's Legal section and is most relevant to user-generated content and moderation.

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

Apps with user-generated content need visible moderation, reporting, blocking, and contact paths.

What Apple is likely checking

Apps with user-generated content need visible moderation, reporting, blocking, and contact paths.

Apple will look for safeguards that reduce abuse, objectionable content, and unsafe interactions.

Creator or community features should not change the native app into a store of separate apps.

Common rejection triggers

Users can post content without meaningful moderation or reporting controls.

The app lacks blocking, filtering, or a clear contact mechanism for abuse concerns.

Screenshots or sample content show objectionable material inconsistent with the app rating.

Fix checklist before resubmission

Add reporting, blocking, filtering, and moderation response paths.

Explain moderation controls in reviewer notes when they are not obvious.

Use safe, fictional sample content in screenshots and demo data.

Reviewer reply angle

If Apple cited Guideline 5.6.4, 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.

Check your app against Guideline 5.6.4

AcceptMyApp can compare your metadata, screenshots, privacy pages, app context, and rejection text against Apple guideline risks before you resubmit.

Get started