Approximate location
Asks for a city-block level location instead of the exact spot.
In one line
Can see roughly where you are, in a region of a few to 20 km
Asks for a city-block level location instead of the exact spot.
Reveals the neighborhood but not the exact address. Useful for weather and local content; still shows commuting patterns over time.
What it can and can't do
What the user does: You tap Allow and choose Approximate location, or turn Precise off on iPhone
It can
- Find your area within a few square kilometers on Android
- Find your region (about 1 to 20 km) on iPhone
- Show nearby stores or local weather without your exact spot
It cannot
- See your street or building
- Follow your moves in fine detail
- Get exact location unless you allow it, or the app asks once for temporary full accuracy on iPhone
- Choose approximate for you; you pick it in the prompt
How it differs between platforms: Android coarse location is about 3 square kilometers. iPhone reduced accuracy is a region of 1 to 20 km and updates less often.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 6.0 (API 23) | iOS 14 |
| Permission or entitlement | ACCESS_COARSE_LOCATION | NSLocationWhenInUseUsageDescription (user turns Precise Location off) |
| Protection level | dangerous | prompt |
| How access is granted | prompt | prompt |
| What the user sees | Android 12+: Approximate chosen in the Precise or Approximate selector | Precise Location off in the iOS 14 prompt returns reduced accuracy |
| How long it lasts | Until revoked; one-time option available (Android 11+) | Until the user switches Precise back on in Settings |
| How to take it back | Settings > Apps > Permissions > Location > Use precise location toggle | Settings > Privacy & Security > Location Services > app > Precise Location |
| Store policy | Play: same location data-safety disclosure as fine | App Review 5.1.1 |
| API | FusedLocationProviderClient (PRIORITY_BALANCED_POWER_ACCURACY) | CLLocationManager.accuracyAuthorization == .reducedAccuracy |
| Notes | Android documents coarse accuracy as about 3 square kilometers. | Reduced accuracy returns a region of roughly 1 to 20 km and updates less often. |
Data you get
What comes back: Blurred coordinates
Shape: object
How often: reduced update rate (a few fixes per hour)
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
latitude | float | degrees | -90 to 90 | about 3 square km on Android; roughly 1 to 20 km region on iOS |
Technical limits
- Apps cannot force precise after the user picks approximate
- Android requires the app to ask for COARSE together with FINE
The story
What it is
An app learns roughly where you are, like your neighborhood, but not your exact spot.
For you
You see a location prompt with a choice for approximate or exact. If you pick approximate, apps know your area but not your door, so weather and local news still work. Delivery or ride apps may ask for exact.
For makers
Makers can often do their job with an area, and less sensitive data means fewer privacy worries. It is enough for weather, local results and regional content. It is not enough to find your door, so some features ask for more.
Where you see it
| Type | Example | Apps |
|---|---|---|
| utilities | A weather app shows the forecast for your area without knowing your street. | AccuWeather, Weather Channel |
| news | A news app puts local stories at the top for your city. | Apple News, Patch |
| shopping | A store app shows the nearest region's deals and stock. | Walmart, Target |
| games | A game picks a nearby server or a regional event based on your area. | None named |
| social | A social app shows trending local events without pinpointing you. | Nextdoor |
| ads | An advertiser targets a neighborhood, and repeated reads over time can still reveal home and work. | None named |
Risks
- Slow tracking of home area
- Many apps still ask for exact
Android and iPhone in short
- Android: Android lets you grant approximate location only, and apps must work with it when asked for exact too.
- iPhone: iPhone has a Precise Location switch for each app, and apps get a rough area when it is off.
What the platform says
- Google: Approximate location. Android 12 lets you share an approximate location, a block or so wide, instead of your exact spot.
- Apple: Precise Location off. iPhone lets you turn off Precise Location so apps see only your general area.
Good uses and abuse
Legitimate uses
- Weather
- Local news
- Regional search results
Known abuse
- Slow tracking of home and work area
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
A real example: LinkedIn
Play Data safety lists Approximate location as collected (not optional). iOS label lists Coarse Location, Linked to You. Server side, LinkedIn also derives location from IP address (policy section 1.5).
History
- 2020-09, iPhone iOS 14: Reduced accuracy introduced with a lower update rate
- 2021-10, Android 12 (API 31): Approximate became a user-visible choice that apps cannot override
Related capabilities
Related
- Precise location. Can see your exact GPS spot while you use the app, after you allow
Same idea on the web
- Geolocation. Can find where your device is, once or while the page is open
Sources
- Android 12: Approximate location
- Android: Request location permissions
- Apple: CLAccuracyAuthorization
- Apple: Requesting authorization to use location services
- Google Play Data safety, LinkedIn (com.linkedin.android)
- App Store listing and App Privacy label, LinkedIn (id288429040)
How well checked: Checked against real behavior.