Journeys
Destination-based live sharing and safe-arrival workflows
A Journey is a destination-based session shared with watchers you pick, running until you arrive, cancel, or complete it. It is its own sharing scope: watchers see the Journey whether or not they are in a Crew with you, and Crew sharing keeps whatever state you set for it.
Journeys are a Pro entitlement and need a destination and service access to start. Local progress can continue when connectivity drops, but watcher delivery, server-side position persistence, arrival, and overdue processing all depend on the network.
Overdue escalation is partial. It runs on deployed server schedules and push or email delivery, checks on you before it alerts anyone, and lets you extend the ETA first. It notifies the people you chose; it does not contact public emergency services.
A watch link is a capability rather than an account check — anyone holding it may be able to follow that Journey until it ends, so treat it as sensitive.
How to Start a Journey
Open JOURNEYS, choose to start one, select a destination and optional watchers, set an expected arrival if wanted, and tap START JOURNEY. STALKR must be Live for the Journey scope.
How Journey Watch Links Work
A Journey creates a capability link that lets selected recipients follow that Journey’s live progress on the web. Treat the link as sensitive because anyone who receives it may be able to view that Journey.
How Expected Arrival Alerts Work
Choose an expected arrival when starting a Journey to arm overdue detection. If you have not arrived, STALKR can check on you first, allow an ETA extension, and then alert watchers if you do not respond.
How to End or Complete a Journey
Use the active Journey controls to mark arrival or end the session. Arrival records safe completion; ending early records cancellation instead.