App Store Guideline 5.6.2 explained: Developer Identity

Guideline 5.6.2 sits in Apple's Legal section and is most relevant to App Review compliance.

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

Apple will evaluate whether this part of the app is clear, complete, safe, and consistent with the App Store Review Guidelines.

Apple will evaluate whether this part of the app is clear, complete, safe, and consistent with the App Store Review Guidelines.

The same issue can appear in the binary, metadata, screenshots, privacy disclosures, or review notes.

A strong submission removes ambiguity before the reviewer has to ask for clarification.

The app behavior and App Store product page do not tell the same story.

Reviewers cannot verify a claim, feature, policy, or required safeguard.

The submission lacks enough explanation for a non-obvious business, safety, privacy, or design choice.

Make the requirement visible in the app or explain it clearly in review notes.

Remove unsupported claims and update screenshots or metadata if they create confusion.

Prepare a concise Resolution Center reply that describes exactly what changed.

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