What this rejection means
Guideline 5.1.1 covers several privacy requirements at once, and a rejection often cites the guideline as a whole. Which requirement your app missed, and what Apple will accept for your type of app, is not always obvious from the message.
What is at stake
Privacy issues touch the app, its back end, its listing and its legal texts at once. A rejection here can also point to a compliance problem beyond the App Store, such as with the GDPR.
When to talk to us
- The message doesn't make clear what to change
- You resubmitted and got the same answer
- A launch, an update or a campaign is waiting on this
- You're not sure whether to reply, resubmit or appeal
Why it takes more than a quick fix
A privacy rejection usually needs changes in several places that must agree with each other. Changing one and missing another leads to the same answer.
How we help
- You send us the caseThe reviewer's message, the app and what changed since the last approved version.
- We find the real causeWe look at your case the way the store does, and find what is really behind it.
- You get a clear planWhat has to change, written for your team, or we work on it with them.
- We help you answerYour reply to the reviewer or your appeal, and follow-up until the review is closed.
Questions
Does a privacy rejection mean our app breaks the law?
Not necessarily: Apple's requirements and the law overlap, but they are not the same. We look at both.
Can you guarantee approval?
No one outside Apple and Google can promise how a review will go. What we can do is find the real cause, remove what we can see would block approval and give the reviewer everything they need.
Do you need access to our accounts?
It helps, but it is your choice. We can work from screenshots, exports and a build, or with a limited role you add and remove yourself.