Background location review: when needed and how to prove it
If foreground is enough, do not request background. When you must, prove use in notes, store copy, and permission prompts. Telegram @hagee66.
This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66
“Always allow” location is under review microscope: delivery tracking, family safety, workout logging may need it; many apps only need a map glance while open but request Always → Guideline 5.1.1. Goee (goee.cc): When In Use before Background; if background required, store page, prompts, demo video, and notes tell one story. iOS copy iOS permission strings; Android Android permission declaration. Eligibility fields per official pages.
What this guide solves
- Ride-hail/order apps continuously collect in background for one-time pickup.
- iOS Background Modes not configured but Always requested.
- Android
ACCESS_BACKGROUND_LOCATIONnot explained line-by-line in Console. - Core features break when user denies background—no fallback.
- Screenshots promise “real-time guard” but only cold-start pin.
- Nutrition label “coarse location” conflicts.
Who should read
| Role | Decision |
|---|---|
| Product | Prove closed loop requiring background |
| Mobile | Geofence vs continuous GPS |
| Compliance | Policy retention disclosures |
| Listing | Notes + screen recording path |
Read decision tree before adding fitness/battery/geofence marketing.
Core practice
Do you need background?
| Question | No → action |
|---|---|
| Must location continue after user leaves app? | No: foreground only |
| Can significant-place alerts replace continuous GPS? | Yes: geofence + foreground |
| Can user “share for N hours” manually? | Yes: shorten window |
| Business still valid if Always denied? | No: redesign or drop background |
iOS proof pack
| Item | Content |
|---|---|
| Purpose strings | Why continuous background |
| Store description | Matches screenshots, no hype |
| Notes | Steps to grant Always |
| Review video | Optional: legitimate off-screen tracking |
| Background Modes | Only real modes |
Android proof pack
| Item | Content |
|---|---|
| Staged permission | Foreground first, then background per OS flow |
| Console declaration | Closest official category |
| Foreground service | Continuous location meets FGS policy |
| Data Safety | Precise/coarse, sharing |
Degrade on deny
After “Always” denied: poll last known point, manual refresh, typed address, push to open app and update—pick one or more.
Copy-paste templates
Review notes (background location)
Background location is required for live trip sharing while the screen is off.
Steps:
1. Login → Start Trip → Enable "Share live location".
2. iOS: grant "While Using", then Settings prompt for "Always" with in-app explanation page (About screen 3).
3. Turn screen off 30s — recipient map still updates (demo trip ID: 9001).
Without Always: user can still complete trips with manual check-in every 5 km (Settings → Privacy → downgrade mode).
Privacy Policy [URL] section Location.
One-pager
Feature:
Foreground enough? Y/N
Background sample frequency:
Max duration screen off:
User stop control:
Retention:
Label/form fields:
Common mistakes
- Copy competitor Always request.
- Notes say “we educate users” with no in-app page.
- Background for ads/analytics—abuse signal.
- Test build disables background; production enables secretly.
- Reject: copy-only, collection unchanged.
- Family/kids products without extra safeguards.
FAQ
iOS Background Modes location checkbox enough?
No—legitimate use and visible controls; details official.
Workout track = background?
Depends on foreground service/lock screen UI—disclose actual behavior.
After reject, downgrade to foreground resubmit?
Remove permission, package, forms, description aligned—rejection fix.
Coarse location enough?
Many list/recommend scenarios yes; precision separate ask.
Goee location design review?
Checklist alignment—no approval promise.
Geofence vs battery copy
Continuous GPS drains battery; reviewers ask how users stop sharing. “Smart power saving” should mean lower rate or geofence, not hidden high accuracy. Settings need “Stop sharing” / “End trip” called out in notes step one.
Regional law and map SDK
EU/US state disclosures vary—legal appendices in policy; in-app short, details in policy. Never absolute “we never background locate” when you do. Driver/guardian scenarios need richer evidence packs; compliance letters from client counsel if needed. Map SDK network in background—declare network + location in Data Safety.
Execution rhythm
Location review before UI freeze—cutting background after map homepage designed is expensive. Policy “Location” section before screenshots with “real-time.” Seasonal share features auto-off after event. No remote “experiments” raising precision during review.
Evidence pack
| Asset | Purpose |
|---|---|
| Consent screen | Informed user |
| Stop button screenshot | User control |
| Redacted track sample | Real use case |
| FAQ link | Reviewer context |
Extra Apple declaration forms per official pages.
City-level server upload but precise client permission—justify in notes or drop precision. Trip logs for appeals—no user PII.
Support scripts
“Tracking at night” complaints: support sees share on/off and end time. Ticket fields match in-app state. User complaints can trigger investigations—eng and ops aligned.
After location rejection
Archive in rejection fix; downgrade permission, copy, or feature. Resubmit: “reviewer missed X; added on Y screen.” Do not keep Always with notes-only defense. If background mandatory, fuller evidence; if not, patch removing Background often faster than appeal.
Internal review and boundaries
Official pages rule. Defect vs wording. Telegram @hagee66 with build and checklist. No approval promise; no hidden features.
| Check | Goee | Client |
|---|---|---|
| Path/notes | Yes | Demo account |
| Policy URL | Yes | DNS |
| Forms vs package | Verify | SDK table |
| Legal | No | Counsel |
Next steps
Common rejection codes. Telegram @hagee66. No approval promise—permission and narrative aligned.
Back to guide library · Apple · Google