5.1.5 — Location Services

Requesting "Always" location access, rather than "While Using," is held to a higher bar — the app needs a real, disclosed feature that requires continuous background location, like navigation or a location-based safety alert, not just analytics convenience.

Frequently caused by requesting background or always location for a feature that could reasonably work with foreground-only access instead.

The short version, in more detail

Guideline 5.1.5 deals with location access. Asking for "Always" access instead of "While Using" is held to a higher standard, so the app needs a real, disclosed feature that depends on continuous background location, such as navigation or a safety alert. Requesting broad access only for analytics or convenience is likely to be questioned.

Why this rule exists

Continuous location tracking reveals where people live, work and travel, which is highly sensitive. Apple lets users choose between limited and continuous access and shows reminders when apps use location in the background. The guideline keeps requests proportional: apps should ask for the least access that makes the feature work, so that users are not asked to accept constant tracking for features that do not need it.

What this guideline covers

• Foreground and background location permissions.
• The purpose strings that explain location use.
• Features that genuinely need continuous location.
• Use of location data for advertising or analytics.

What usually triggers this rejection

• Requesting Always access for a feature that works with foreground location.
• A vague purpose string for background location.
• Collecting location for analytics with no user benefit.
• Sharing location data with third parties undisclosed.
• Requesting location at launch with no feature in view.

How reviewers evaluate it

• Reviewers compare the permission requested with the feature that uses it.
• They read purpose strings and in-app explanations.
• They check whether the app works without Always access.
• They look at where location data goes.

Common misunderstandings

• More location access is not a safer default. It attracts more scrutiny.
• A purpose string cannot justify access the feature does not need.
• Approximate location is often enough for features that seem to need precision.

Common questions