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.
How this works
Every safety feature here tells people you chose. SOS reaches the active Crew, overdue escalation reaches that Journey's watchers, and a timer reaches the recipients you set — none of them reach 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.
That is why the labels are blunt about age and failure. A stale position is shown as stale, a delivery problem is surfaced rather than hidden, and nothing that was only attempted is presented as sent.
What happens next
Treat every alert as a message to people who chose to help, not as a dispatch.
Common problems
- STALKR does not contact public emergency services.
- A failed SOS, timer, or overdue escalation is not queued and replayed later.
Questions this answers
- Can I rely on STALKR as a rescue beacon?
- Does STALKR dispatch emergency services?