Mobile app geolocation: permissions, accuracy, geofencing and privacy
Mobile app geolocation is how an app learns where the device is, and it powers maps, delivery tracking, store finders, check-ins, field work and arrival alerts. It is also one of the most restricted features on iPhone and Android: the user decides whether the app may use location, whether it is precise or approximate and whether it may run in the background, and both app stores review how the app uses it. This guide explains how location works on each platform, the limits that shape design, the store rules and the GDPR, with links to the official documentation.
The short version
- Ask for location only when the user starts a feature that needs it, and explain why in one sentence.
- Prefer foreground location ("while using the app"). Background location is restricted on both platforms and reviewed by both stores.
- Design for approximate location, because users can refuse precise location at any time.
- Use geofencing for arrival and departure alerts rather than constant tracking, and respect the limits on how many regions an app can watch.
- Treat location as personal data: collect only what the feature needs, keep it for a defined time and say so in the privacy policy.
How location works on a phone
An app does not read the GPS chip directly. It asks the operating system's location service, Core Location on iPhone and the fused location provider on Android, which combines satellite positioning, nearby Wi-Fi networks, mobile network cells and motion sensors. The service returns a position with an accuracy estimate and decides how often to power up the radios, which is why location quality and battery life depend on how the app asks.
Android's location permissions documentation describes the two accuracy levels (read 11 November 2026). Approximate location is accurate to within about 3 square kilometres. Precise location is usually within about 50 metres and sometimes within a few metres or better. On iPhone, the user can likewise grant full or reduced accuracy, and the app has to work with whichever it gets.
Permissions on iPhone
Apple's documentation on requesting authorization to use location services describes two levels (read 11 November 2026):
- When in Use. Location updates are available only when someone uses the app. If the app has enabled background location updates, it can continue while location services are active, for example during a navigation session the user started.
- Always. Location updates are available at any time, and the system can launch the app quietly to handle some updates, such as entering a region.
The app must include a usage description string that explains why it needs location, and it can ask for Always later, separately, once the user has seen the feature work. A good pattern is to ask for When in Use when the user taps the feature, and to ask for Always only for a feature that cannot work without it, such as an arrival reminder.
Permissions on Android
Android separates two dimensions: foreground or background, and approximate or precise. Apps declare ACCESS_COARSE_LOCATION for approximate and ACCESS_FINE_LOCATION for precise, and the documentation states that if the user grants only approximate location, the app has only approximate location regardless of what it declares. On Android 10 (API level 29) and later, background access requires the separate ACCESS_BACKGROUND_LOCATION permission, requested at runtime after foreground access. A feature that keeps tracking after the user leaves the app, such as navigation or a courier's active delivery, should run as a foreground service of type location, which shows a persistent notification.
Background updates are also rationed. According to Android's background location guide, on Android 8.0 and higher an app running in the background receives location updates only a few times each hour (read 11 November 2026). Designs that assume continuous background tracking without a foreground service will not work as expected.
Geofencing
Geofencing alerts the app when the device enters or leaves an area, without the app tracking every movement. It is the right tool for arrival reminders, check-in at a site, "your order is ready as you arrive" and automatic time recording at a workplace. Both platforms set limits:
| Platform | Limit | Source |
|---|---|---|
| iPhone | Core Location prevents a single app from monitoring more than 20 conditions of any type at the same time | Apple: monitoring proximity to geographic regions |
| Android | Up to 100 active geofences per app, per device user; in the background, the device responds to geofence events every couple of minutes | Android: create and monitor geofences |
An app that needs more places, for example a chain with hundreds of stores, registers only the nearest ones and refreshes the list when the user moves a significant distance. Geofences are also not instant: Android's documentation notes that a higher responsiveness value saves battery by increasing the latency of alerts. Design the feature so a delay of a few minutes does no harm. (Sources read 11 November 2026.)
What the app stores require
Apple. Guideline 5.1.5 of the App Review Guidelines says to use Location Services only when directly relevant to the features and services the app provides, to notify and obtain consent before collecting, transmitting or using location data, and to explain the purpose in the app. It also says location-based APIs should not be used to provide emergency services or autonomous control over vehicles, aircraft and other devices, with exceptions for small devices such as lightweight drones and toys.
Google Play. Background location is reviewed. Google's help page on location in the background permissions lists what an app must provide: a permissions declaration form, a video demonstration, a prominent in-app disclosure and a privacy policy both in the app and on its store listing. Apps that request background location without a core feature that needs it are rejected. (Both read 11 November 2026.)
Location data and the GDPR
Article 4(1) of the GDPR names location data among the identifiers that can make a person identifiable, so location is personal data. A trail of positions reveals home, work, habits and sometimes health or religion, so it deserves more care than most app data. In practice:
- A lawful basis and a clear purpose for each use, written in the privacy policy.
- Collect only the accuracy and frequency the feature needs; a store finder does not need a trail.
- A retention period: delete or aggregate positions when the purpose is served.
- No location data in analytics or advertising SDKs unless the user has agreed to that specific use.
- For employees, workplace monitoring rules apply on top of the GDPR. Track work time and work sites, not people off duty, and agree the rules with staff representatives where national law requires it.
Design patterns that work
- Ask in context. Request permission when the user taps "Find stores near me", not on the first screen.
- Degrade gracefully. If location is refused or approximate, offer a postcode or city search instead of a dead end.
- Show accuracy. Draw the uncertainty circle, and do not claim "you are here" from a 3 km estimate.
- Stop when done. End location updates when the delivery is completed or the session ends, and tell the user.
- Test in the real world. Indoors, underground, in moving vehicles, with battery saver on and with permissions changed while the app runs.
How we help
We build location features into iPhone and Android apps, from store finders and check-ins to live delivery tracking and field crew apps, with the permissions, store declarations and privacy design done from the start. See app development, field service management software, taxi app development and on-demand app development. Our guide to food delivery app development covers courier tracking in more detail.
Questions people ask
How does a mobile app get the user's location?
Through the operating system's location service, Core Location on iPhone and the fused location provider on Android. The system combines GPS, Wi-Fi, mobile network and sensor data, and gives the app a position with an accuracy estimate, but only after the user grants permission.
Can an app track location when it is closed?
Only with background permission. On iPhone, Always authorization lets the system launch the app for some location events. On Android 10 and later, the app must declare and request background location separately. Both stores restrict background location to features that genuinely need it, and Google Play requires a declaration and a video for review.
How many geofences can an app use?
Core Location lets a single app monitor at most 20 conditions at the same time, and Android allows up to 100 active geofences per app per device user. Apps with more places to watch register the nearest ones and update the list as the user moves.
Is location data personal data under the GDPR?
Yes. The GDPR names location data as one of the identifiers that can make a person identifiable. Collecting it needs a lawful basis, a clear purpose, data minimisation and a retention limit, and tracking employees' location raises additional rules on workplace monitoring.
Why is the location in my app inaccurate?
Common causes are approximate permission instead of precise, poor GPS reception indoors or between tall buildings, battery saver modes, and background limits that deliver updates only a few times an hour. A good app shows the accuracy it has and asks for precise location only when a feature needs it.
Sources
- Apple: Requesting authorization to use location services (read 11 November 2026)
- Apple: Monitoring the user's proximity to geographic regions (read 11 November 2026)
- Apple: App Review Guidelines, 5.1.5 (read 11 November 2026)
- Android: Request location permissions (read 11 November 2026)
- Android: Access location in the background (read 11 November 2026)
- Android: Create and monitor geofences (read 11 November 2026)
- Google Play: Understanding location in the background permissions (read 11 November 2026)
- Regulation (EU) 2016/679 (GDPR), Article 4(1) (read 11 November 2026)