App Store 5.1.5 rejection: Location data

Apple may be asking why your app needs location at all. Under 5.1.5, location must directly relate to the app’s features, with an explanation and consent before collection, transfer, or use.

Match the request to a task

Find the first location request and identify the feature it supports. Check background use and third-party libraries too. We’d test declining access and using an alternative such as a manually entered address when the task supports it.

Narrow the use and explain it

Remove unrelated location collection and request access at a point where its purpose makes sense. Align the permission explanation, app screens, and data sharing.

Apple also restricts location APIs for emergency services and autonomous vehicle or device control, with specified small-device exceptions. If that describes your product, assess the exact use rather than treating ordinary navigation permission as approval for it.

Test permission refusal, approximate/available location conditions, and any background behavior. Give Apple the feature, why location is necessary, and the corrected route. A more persuasive purpose string won’t fix collection unrelated to the app.