Everyday
Readiness, Assistance Points, safety planning and community conditions.
WITH. / How it works
The system
One protection engine. Different moments of risk.
The interface stays simple while the underlying system prepares, guards, notices, verifies, acts, reaches help and supports recovery.
Guardian
A protected journey, ride, walk, drive or short Safety Countdown.
Private Risk
Scheduled check ins and a prepared pathway for risk involving someone known.
Core rule
An incident must survive the phone.
If a phone is taken, damaged or goes offline during an active incident, the backend should preserve the last trusted state and keep the escalation process alive.
Phone disappearsServer keeps active session, last heartbeat, last location and incident state.
No mobile dataLocal logic continues, events queue, and available fallback paths are tried.
Trusted contact does not answerOne person is not the whole safety chain.
Responder does not acknowledgeThe incident remains open and escalation continues.
Guardian Journey
Protect a journey.
- destination and travel mode
- expected route and arrival
- major deviation
- connection and heartbeat state
- Trusted Circle
- Assistance Points nearby
Safety Countdown
Protect a short vulnerable moment.
- choose 5, 10, 15 or 30 minutes
- quiet timer
- discreet check in
- safe, help or no response outcome
Private Risk
Prepare quietly.
- scheduled check ins
- safe destination
- duress PIN
- Trusted Circle
- Emergency Identification Pack
Incident
Make response measurable.
- created
- delivered
- acknowledged
- responder assigned
- en route
- arrived
- user located
- resolved