The wrapped-website syndrome
An app that's just a website wrapped inside an app. That's exactly what triggers tons of Apple 4.2 rejections.
"This app would like to access your location."
Today, tons of users get suspicious the second this message appears. And honestly ? It's logical.
Because users have learned to protect their data. And Apple has been pushing this logic hard for years.
Asking without explaining = immediate distrust
The problem is that many apps ask for permissions… without really explaining why.
Camera. Location. Notifications. Microphone. Contacts.
The user opens the app… and immediately receives a series of sometimes incomprehensible prompts. Result : distrust. And when distrust shows up… trust drops very fast.
Apple looks at the justification
Apple watches this topic heavily. And it's not only a technical question. Because Apple doesn't only look at "Does the permission work ?" They mainly look at "Is this request justified and understandable ?"
For example :
- why does the app need location ?
- at what moment ?
- for which specific feature ?
- is it indispensable ?
- is it consistent with the product ?
This is a review requirement, not a style preference. Guideline 5.1.1(ii) states it directly : "Ensure your purpose strings clearly and completely describe your use of the data." (Apple App Store Review Guidelines 5.1.1, 2026). The same clause requires that users can withdraw consent through "an easily accessible and understandable way", and that paid functionality must not depend on granting access. See also the Human Interface Guidelines on privacy.
In short : "Improve user experience" fails on both counts — it names neither the data nor the use. A purpose string that names 1 feature and 1 reason passes; one that names 0 of either is the single most avoidable rejection in this list.
Apple hates vague. So do users.
The problem is that many apps still use extremely vague descriptions like "Improve the user experience." But honestly… that says nothing.
And Apple hates vague. Users too. The key difference between a permission that gets granted and one that gets refused is usually 10 words of explanation shown at the right moment.
The real topic isn't the permission, it's trust
Because in the end, the real topic isn't the permission itself. The real topic is trust.
When an app clearly explains why it asks for something, how it helps the user, when that data is used, the perception changes completely.
Does the user understand what's happening ? Do they feel respected ? Do they feel manipulated ? These questions massively change an app's perception.
Apps that inspire trust are often the ones that ask the least… or that explain the best. Bottom line : Apple also requires that consent can be taken back, in "an easily accessible and understandable way", and that a privacy policy identify "what data, if any, the app/service collects, how it collects that data, and all uses of that data" (Apple App Store Review Guidelines 5.1.1, 2026). Asking for 2 permissions you can justify beats asking for 6 you cannot.
Do your iOS permissions explain their use clearly enough ? Book a 30-minute call to audit purpose strings before the next App Store Review.
