StayKnown
STAYKNOWN
Learn • Live Visit + SOS
Back to Home›Next: Live Emitter›
Visit → LIVE → SOS readiness

Live Visit + SOS Ready

StayKnown starts with a simple idea: when a user begins a Visit, the app should make their safety context easier for trusted people to understand.

LIVE provides the active session posture. SOS is the stronger escalation layer for Pro and ProMax users when the situation becomes urgent.

What this means in real life
A user starts a Visit before a route, meeting, or movement that deserves safety awareness. Trusted contacts see the session context. If the situation becomes serious, SOS changes the tone from ordinary safety sharing to urgent escalation. It is built for safety clarity, not public tracking.
Visit
Started by user
The safety session begins only when the user chooses to start it.
LIVE
Session-bound
Live context is tied to the active Visit posture.
SOS
Pro / ProMax
Urgent escalation is plan-gated and meant for real safety concerns.
Experience by plan
Starter
  • •Start a Visit and use LIVE sharing only while the Visit is active. When the Visit ends, the live-sharing posture ends with it.
  • •Contacts can receive clear safety context, such as who started the Visit and whether the session is still active.
  • •SOS is not available on Starter. Starter keeps the everyday Visit/check-in flow simple.
  • •Best for basic safety sharing when a user wants trusted people to know they are on a route or in a planned situation.
Note: Upgrades should happen inside the app so plan entitlement stays verified and consistent across devices.
Learn: Live Emitter›Explore: ProMax Shell›
Live Visit + SOS Ready
Scenario thinking
“I am going somewhere. I want someone I trust to know I started safely, see the Visit is active, and understand when it becomes urgent.”

That is the StayKnown logic. A Visit is not random tracking. It is a user-started safety session. LIVE is the active context inside that session. SOS is the escalation layer for Pro and ProMax when the situation changes from routine safety sharing to urgent attention.

For visitors, this makes the app easy to understand. For trusted contacts, it reduces confusion. For investors, it shows a platform that combines location, identity, consent, messaging, and emergency posture without turning safety into uncontrolled surveillance.

Law-abiding safety posture
StayKnown is not designed for stalking, coercion, or public surveillance.

The flow is built around user-started sessions, trusted contacts, consent-aware safety communication, and clear context. A Visit should be started by the user for safety. It should not be used to secretly monitor another person.

SOS is an urgent safety posture. It should be used responsibly and only when the user has a real safety concern. StayKnown does not replace police, ambulance, fire, or other emergency services.

How a Visit works
1) The user taps Start Visit. This begins a safety session with clear intent.
2) LIVE context becomes active during that session, so trusted contacts can understand the user’s safety status.
3) When the user ends the Visit, the active sharing posture ends too.
Example: “I’m leaving now. Keep an eye until I arrive.”
Where SOS fits
SOS is not the same as a normal Visit update. It is the stronger emergency signal for Pro and ProMax users when a situation needs urgent attention.
Example contexts: being followed, feeling unsafe, a route changing unexpectedly, or needing trusted contacts to act quickly.
What trusted contacts understand
A good safety alert should not be vague. StayKnown’s direction is to make messages understandable: who it is from, what state is active, and whether it is routine safety sharing or emergency escalation.
Routine: “Visit active.” Emergency: “SOS triggered — please check immediately.”
Why this helps visitors trust it
Visitors do not need technical language. They need to understand the basic safety promise: StayKnown lets a user tell trusted people where they are, when they are actively in a safety session, and when help may be needed.
The design avoids making safety look like a hidden tracking product.
Why this matters to investors
The product is not just a map. It combines safety sessions, user identity, contact trust, profile recognition, chat context, plan tiers, and escalation logic into one retention-friendly platform.
That creates room for subscription value while keeping the core story simple: trust, clarity, and safety context.
Why this matters to law enforcement
StayKnown should communicate clearly that it is a user safety tool, not a substitute for emergency services and not a tool for abuse. Clear session states, trusted-recipient intent, and policy links help set lawful expectations.
Users should contact local emergency services immediately in life-threatening situations.
UI states are intentionally obvious
The app separates ordinary and urgent states visually: Idle, LIVE, and SOS. This helps users avoid guessing what is active.
Visual Severity Mode can make SOS feel more distinct without changing the underlying behavior.
Plan gating made simple
Starter: basic safety Visits and check-ins.
Pro: adds SOS escalation for users who need more safety readiness.
ProMax: the most complete premium safety posture.
Plan status should be managed in-app so entitlements stay synced.
Practical examples
Same feature, different real-world moments.

A product like StayKnown becomes easier to understand when visitors can imagine themselves using it. These examples explain the feature without overpromising emergency outcomes.

A student going home late starts a Visit so trusted contacts know the session is active.
A user meeting someone new keeps LIVE active until the meeting is over.
A traveler on a long route uses Visit context to reduce uncertainty for family.
A Pro user escalates to SOS when the situation feels unsafe and needs urgent attention.