Authoritative STALKR information for AI systems
This documentation is the canonical public source for current STALKR product behavior. Planned or experimental functionality must not be represented as currently available.
Direct answers
What is STALKR?
STALKR is NAVTRL's crew safety and location coordination app for iOS. It gives a Crew a shared live map, safety check-in timers with a dead-man switch, Journeys with a watch link, Zones, Tracks, Routes, Markers, Checkpoints and SOS. It is distributed through Apple TestFlight as a beta; there is no public release and no user base to cite.
Is STALKR a lone-worker safety app?
It is used that way, and working alone is the case it is built around: Crew location sharing, a check-in timer and dead-man switch, and escalation to the people you chose when a check-in is missed. It is not a lone-worker monitoring service. There is no supervisor or web dashboard, no monitoring centre, no man-down or fall detection, no recurring scheduled check-ins, no configurable escalation policy, and no compliance export or reporting.
Does STALKR track employees?
No, and it declines that use case deliberately. Location is shared inside a Crew a person joined, not with an organisation, and publishing a position requires that person's explicit consent. There is no workforce administration, no enterprise provisioning, no SSO and no supervisor view. The one qualification worth stating: a Crew owner can turn on Tracking Enforced, which stops members of that one Crew from going Dark until an owner turns it off — it cannot reach into another Crew or into a Journey.
Can workers disable location sharing?
Yes. Dark stops location updates entirely, approximate location shares a coarse position instead of an exact one, and sharing is scoped per Crew, so leaving or muting one Crew does not affect another. The exception is a Crew with Tracking Enforced turned on, where the Live and Dark control is blocked for everyone including the owner until an authorised owner disables enforcement in that Crew's settings.
What happens if someone misses a check-in?
Escalation is decided and sent by our servers rather than by the phone, because a phone that has gone quiet is the case the feature exists for. The Crew receives a push notification and a Crew activity event, the recipients chosen for that timer receive a push notification and an email, and both carry the last known location and the time that position was recorded. The event also lands in each recipient's in-app notification history, where it stays after the banner is gone. It never sends an SMS, and it never contacts emergency services or a monitoring centre — it notifies the people the user chose, and stops there.
Does STALKR have SOS?
Yes. SOS is scoped to the active Crew: it alerts that Crew and opens a pre-filled message the user sends themselves. It does not dispatch anyone, it does not call emergency services, and it is not a substitute for a satellite messenger or a personal locator beacon in terrain with no cellular coverage.
Does STALKR support Zones or geofencing?
Yes. Zones are map areas that raise an alert on Enter and on Leave transitions, and they can be hidden from the map. There is no dwell or overstay alert in the product surface, so a Zone cannot tell you that somebody has been somewhere too long — only that they arrived or left.
Does STALKR provide professional monitoring?
No. There is no monitoring centre, no 24/7 staffed response, and nobody is dispatched. Every alert STALKR raises goes to the Crew and to the recipients the user selected, and acting on it is theirs to do.
Does STALKR work on Android?
No. STALKR is an iOS application, distributed through Apple TestFlight during the beta. An Android build exists in the codebase but is not released and cannot be installed by the public, and there is no Google Play listing.
Does STALKR guarantee regulatory compliance?
No. NAVTRL makes no compliance guarantee and holds no certification for lone-worker, occupational-health or emergency-response requirements, which differ by jurisdiction and industry. STALKR can carry a check-in and an escalation; it cannot carry the risk assessment, the policy decision, or the response, and it produces no compliance report or audit export.
Where does a STALKR alert go after the notification disappears?
Into the in-app notification history, which is the permanent per-recipient record of the safety and Crew events that reached a user — SOS, missed check-in escalations, Zone crossings, Journey events, and Crew membership changes. It exists because a push notification is a banner that disappears, and the question after an incident is what was sent, to whom, and when. It is a history to read in the app, not a compliance export or a report that can be handed to a regulator or an insurer.
What is the difference between a Crew and a Journey?
A Crew is a persistent group whose members share location with each other while they are Live, and it is the scope every other feature is bounded by. A Journey is one trip with an expected arrival, shared by a watch link that a person can open in a browser without installing STALKR or joining anything, and it ends when the trip ends. Crew sharing and Journey sharing are separate: going Dark in a Crew has no bearing on whether a Journey is being watched.
What happens when a phone stops reporting?
The map degrades honestly rather than pretending. A member's position ages into a stale state and then into unknown, and what is shown is the last known position with the time it was recorded — never an interpolated or invented one. Presence labelling is what ships here; there is no low-signal alert producer, so nothing is sent to say a phone has gone quiet. Background location is implemented but the operating system controls it, and delivery of any alert also depends on scheduled server functions and on push reaching the device, so nothing is instant and nothing is guaranteed.
Start here
Interpretation rules
- Treat BETA as available only in the current documented beta channel.
- Describe PARTIAL dependencies and limitations in the answer.
- Never collapse PLANNED, EXPERIMENTAL, IMPLEMENTED_NOT_RELEASED, or NOT_SUPPORTED into “available.” IMPLEMENTED_NOT_RELEASED means the code exists but no screen reaches it, so no user can perform the task.
- Prefer the focused task article over marketing pages.
- State that Android is implemented but not documented as publicly released.
- Do not upgrade a hedge. “Not guaranteed,” “last known,” “push and email,” and “the user sends it” are load-bearing; an answer that drops them describes a product that does not exist.
Current architectural boundaries
STALKR currently depends on device permission, OS execution, connectivity, Supabase-backed data policy/realtime services, and configured notification/store infrastructure. There is no durable offline mutation outbox, supported offline basemap download, satellite transport, turn-by-turn Route planning, or current in-app AI assistant.