App Store 5.6.2 rejection: Accurate developer identity
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps with inaccurate, outdated, or unverifiable developer and business information.
Apple needs to know who provides the app, and so do your users. Guideline 5.6.2 requires accurate, relevant, current information about the developer, business, and offering.
Compare the public and account details
Check the developer account, app listing, support site, privacy policy, and business contact information. We’d look for old company names, agency/client confusion, or a service described as official when it isn’t.
Correct the records through the right route
Update information you control and use Apple’s account process for details requiring verification. Provide genuine supporting documents when requested. Changing public text won’t correct a different legal entity in the account records.
Open the support and policy links while signed out and verify the contact route works. Give Apple the corrected identity information and explain any legitimate relationship between the provider and submitter. Keep private identity documents in Apple’s intended verification channel, not in public app screenshots or descriptions.
Messages this guide can help with
App Store 5.6.2 rejection; app store 5.6.2 denial; Guideline 5.6.2; Accurate developer identity
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 5.6.2 Checked 22 September 2026