What the user does
Send or accept an approved-contact request and decide who may participate in the supported safety relationship.
Consent-first safety
Safety access should have a beginning, purpose, and end.
StayKnown helps people move, visit, check in, and escalate danger through user-started safety sessions—without turning trusted relationships into permanent surveillance.
Approved contactsActive VisitsLIVE contextI’M SAFESOS
User-controlled safety session
Interactive safety journey
See exactly when safety access starts—and when it stops.
Move through each stage to understand the user action, the trusted contact experience, and the consent boundary that keeps StayKnown different from always-on tracking.
Stage 01 of 07
Approve
Permission relationship01
Move your pointer for a controlled 3D view
Permission relationship
Trusted access starts with mutual approval.
StayKnown begins with a visible relationship between people—not a hidden map. The user decides who can participate in supported safety flows.
What trusted contacts understand
The other person sees a clear request and approval state. They do not receive silent access to the user’s location.
Consent boundary
Approval creates a trusted relationship. It does not automatically start LIVE sharing.
Consent architecture
Approval is not the same as active location access.
StayKnown separates the trusted relationship, the active safety session, the emergency escalation, and the verified ending. That separation is the foundation of the consent-first model.
No hidden accessNo public mapNo permanent LIVE session
State 01
Approved contact
Relationship ready
The people know each other inside StayKnown, but no LIVE session is running.
State 02
Visit active
Selected access
Only the recipients selected for the active safety flow receive its context.
State 03
SOS active
Urgent escalation
The configured emergency circle receives the strongest available alert context.
State 04
Session ended
LIVE access closed
The safety session is finished and its LIVE access does not continue permanently.
Trusted-contact handoff
Context travels with the alert.
A safety notification should explain what happened, what protection is active, and what the trusted person can do next. StayKnown is designed around that handoff—not just a raw coordinate.
Identity and recognition
Visit or SOS state
Location confidence
Response actions
Visit started
Destination, selected recipients, and active safety context.
LIVE context
Permitted location, confidence, user recognition, and session state.
I’M SAFE
Direct reassurance with the supported check-in context.
SOS active
Urgent escalation with clear response actions and safety details.
Begin with understanding
Install the safety system you control.
Start with the free Starter plan, add an approved contact, practise the flow, and choose when a real safety session should begin.