App Store Guideline 2.3.2 explained: In-app purchase disclosure in metadata

Guideline 2.3.2 sits in Apple's Performance section and is most relevant to metadata and screenshots.

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

Your App Store product page should match the submitted build and current feature set.

Your App Store product page should match the submitted build and current feature set.

Screenshots, previews, descriptions, keywords, and claims should avoid overstating what the app does.

Reviewer notes should call out any new or non-obvious functionality that affects the product page.

Screenshots show marketing art, splash screens, outdated UI, or features that reviewers cannot find.

The app description, keywords, or promotional text mention claims that are not visible in the build.

A product page field implies pricing, platform support, content, or affiliation that is not accurate.

Compare every metadata field against the submitted binary before resubmission.

Replace vague claims with specific in-app functionality.

Update review notes with the location of features that could otherwise be missed.

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