StayKnown separates contact approval, active location access, urgent SOS escalation, communication, device integrity, minor protection, reporting, and verified completion so safety tools do not become control tools.
Select a trust pillar to inspect how StayKnown separates consent, location access, emergency escalation, communication, integrity, and minor safety.
StayKnown is built around people with a lawful and trusted safety relationship. A contact request can be accepted, declined, restricted, removed, or blocked.
Approval, an active Visit, SOS escalation, and a completed session are different states. Select one to see what location and contact access actually means.
Approval prepares the relationship for supported safety flows but does not start location sharing.
StayKnown prohibits misuse that turns consent, location, emergency alerts, communication, identity, or payment systems into harm.
Immediate danger, platform abuse, security vulnerabilities, account support, and billing issues require different response pathways.
Use the abuse-reporting route for stalking, repeated unwanted contact, coercive control, fake emergencies, unsafe content, or account misuse.
StayKnown keeps privacy, location, consent, anti-stalking, emergency, minor-safety, reporting, retention, legal, security, and billing information publicly accessible.
Contact the appropriate local emergency service or authority first. StayKnown does not provide official dispatch.
StayKnown is not police, ambulance, fire service, rescue service, hospital, road safety, civil defence, disaster management, government authority, or universal professional emergency response. Contact the correct local emergency service when immediate danger exists.
