App Store 5.6 rejection: Developer conduct

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad developers receiving concerns about misleading, abusive, manipulative, or fraudulent conduct.

A conduct notice can concern behavior outside the app as well as its screens. Guideline 5.6 covers dealings with customers and Apple, misleading purchases, unnecessary data demands, and other manipulative practices.

Identify the practice behind the notice

Review the cited interaction, offer, campaign, or support response. We’d compare what people were promised with what they actually received, including charges and cancellation behavior. Preserve the relevant facts so your response addresses the issue accurately.

Correct the practice across the service

Stop abusive or misleading behavior and repair the underlying process. Check related offers and customer communications for the same issue. The child rules below address review replies, identity, discovery manipulation, and ongoing quality.

If Apple has terminated an account, its guideline describes submitting a written improvement plan and possible restoration after approval and confirmation of the changes. Restoration isn’t guaranteed.

Give Apple a factual account of the cause, completed improvements, and evidence. A code change alone won’t resolve a support or marketing practice that continues unchanged.

Messages this guide can help with

App Store 5.6 rejection; app store 5.6 denial; Guideline 5.6; Developer conduct

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit your iPhone or iPad app for review