Apple
Apple 5.1.1 Privacy
Tell people what you collect, why a sensitive permission is needed, and link a real privacy policy.
Read the official pageThese are the review rules ShipCheck looks for. A scan names the rule. The paid fix shows the change for your project.
Apple
Tell people what you collect, why a sensitive permission is needed, and link a real privacy policy.
Read the official pageApple
If someone can create an account, the app has to let them delete it. Sending them to a support email is not enough.
Read the official pageApple
Apps that use common iOS calls need a privacy manifest. Tracking also has to be disclosed.
Read the official pageApple
If you track people across apps or websites, ask before the tracking starts.
Read the official pageApple
If you offer Google, Facebook, or another social login for the account, you also need Sign in with Apple as an equal option.
Read the official pageApple
Digital features, subscriptions, and unlocks inside the iOS app have to use In-App Purchase. A Stripe card form for those items gets rejected.
Read the official pageApple
The build reviewers open has to work. Placeholder text, dead links, and unfinished screens are a common reason for a 2.1 rejection.
Read the official pageApple
The app needs a reason to exist on the phone. A thin wrapper around a website is a common 4.2 rejection.
Read the official pageGoogle Play rejects new apps and updates whose target API is behind the current requirement.
Read the official pageThe Data safety form in Play Console has to match what the app collects. Reviewers reject mismatches for email, location, photos, and advertising ID.
Read the official pageBroad access to photos and files is limited. Declare only what the app really needs.
Read the official pageAllowing cleartext HTTP can get the app flagged when user data is sent without HTTPS.
Read the official page