Safety
SOS, timers, and emergency contacts
Every safety feature here tells people you chose. SOS reaches the active Crew, overdue escalation reaches that Journey's watchers, and a check-in timer reaches the recipients you set. None of them contact public emergency services.
Each one runs on a chain that can break: location permission, battery, what iOS allows the app to execute, connectivity at the moment it matters, deployed server functions, and delivery to the recipient's device. A link that fails is not retried from a queue — SOS in particular reports that it could not reach the service rather than holding it for later.
Emergency contacts are stored recipients, not subscribers. Saving one sends nothing and tells that person nothing; they hear from STALKR only when you select them for a Journey or a timer and that delivery succeeds.
SOS, check-in timers, and emergency contacts are presented as Pro capabilities in the subscription UI. Rally points are not available in the current build at all.
How to Send an SOS
On the map, press and hold the red SOS button until the deliberate hold completes. STALKR creates a panic incident and attempts to alert the active Crew; it does not contact public emergency services.
How to Use a Check-In Timer
Open Safety & Alerts, choose the safety timer, set when STALKR should check on you and who should be notified, then arm it. Acknowledge or resolve it before escalation.
Are Rally Points Available?
No. Rally points are not available in the current STALKR beta. The capability exists in the codebase, but no screen exposes it, so a Crew cannot set, see, or clear a rally point today.
How to Manage Emergency Contacts
Open Settings → Safety & Alerts → Emergency Contacts. Add a person manually or choose from device Contacts, then use them as Journey watchers or safety recipients.
What STALKR Safety Features Do Not Do
SOS, check-ins, overdue alerts, and arrivals are coordination aids. They do not contact public emergency services and depend on permission, battery, OS execution, connectivity, server functions, and recipient delivery.