Permissions
Location, background access, contacts, camera, and notifications
STALKR asks for each permission at the moment the workflow needs it, and denying one does not require granting another. Contacts is requested only when you open the device picker, camera only when you capture, photo-library read only when you choose an image, and photo-library add only when you export one back.
Location has two levels that do different jobs. While-using access covers your self marker and foreground sharing; Always access is what lets eligible Crew sharing, Track recording, Zone transitions, and Marker arrivals continue when the screen is locked or the app is backgrounded.
Background execution is partial, and the honest description is that iOS decides. Force-quitting stops ordinary background location updates, iOS region monitoring may still wake the app for eligible circular regions but is OS-controlled, and physical-device validation is still an open release gate.
Notifications permission controls whether alerts can appear at all. Without it, local detection still happens and remote events still occur, but nothing surfaces on the device.
Why STALKR Needs Background Location
Always/background location lets STALKR continue eligible Crew sharing, Track recording, Zone transitions, and Marker arrivals while the screen is locked or the app is backgrounded. OS limits and force-quit still apply.
What Happens When Location Is Off
STALKR cannot show or share a current self position when location access is denied. It refuses to claim that you went Live and offers to open system Settings.
Contacts, Camera, Photos, and Notification Permissions
Contacts is used only when you choose people from the device; Camera/Photos are used for media workflows; Notifications are used for local and push alerts. Denying one does not require granting unrelated permissions.