StayKnown Emergency Disclaimer for SOS, live location, and trusted-contact alerts.
StayKnown can help notify approved contacts and provide safety context, but it does not replace official emergency services in Nigeria, the United States, the United Kingdom, the European Union, or any country. If immediate danger exists, contact the official emergency number or local emergency authority first.
1) Emergency disclaimer summary
StayKnown is a safety-awareness and trusted-contact service. It can support safety communication, location context, SOS alerts, manual capture, Visit sessions, LIVE sharing, chat context, and approved-contact notifications. It does not guarantee rescue, police response, ambulance response, fire response, medical care, official dispatch, prevention of harm, or any specific outcome.
2) Immediate danger comes first
If you, a minor, a dependent, a contact, or another person is in immediate danger, contact the proper local emergency number, emergency agency, law enforcement, medical provider, fire service, rescue service, trusted responder, or local authority first.
- Do not wait for a StayKnown alert, email, push notification, chat message, map update, or location point if immediate action is needed.
- Use local emergency numbers, official emergency apps, police, ambulance, fire, medical, rescue, road-safety, civil-defence, disaster-management, or local safety channels where appropriate.
- If it is unsafe to call, follow local emergency guidance for silent, text-based, family, community, or trusted-responder options where available.
- If a StayKnown contact receives an urgent alert and cannot reach the user, the contact should use responsible judgment and official emergency channels where danger seems credible.
3) StayKnown’s role in safety situations
StayKnown can help a user communicate safety context to trusted people during Visits, LIVE sharing, SOS events, manual capture updates, chat, and related safety flows.
- Notifying trusted contacts when a user starts or updates a safety session.
- Sharing user-triggered safety context during an active Visit, SOS flow, or manual capture event.
- Helping contacts understand that a safety event is active or recently changed.
- Providing history and delivery context where records are available.
- Supporting safer communication through chat, voice notes, translation, media, and profile trust where enabled.
- Providing map or place-label context so approved contacts can better understand a user’s safety location.
4) What StayKnown is not
StayKnown does not become an official emergency responder simply because a user starts a Visit, triggers SOS, sends manual capture, shares LIVE context, sends a chat message, or shows a map.
- StayKnown is not police, ambulance, fire service, rescue service, medical service, private security, emergency dispatch, public safety answering point, or government emergency authority.
- StayKnown is not U.S. 911, U.K./EU 999 or 112, Nigerian police, Nigerian ambulance, FRSC, NSCDC, NEMA, state emergency agencies, hospitals, fire service, or any official emergency body.
- StayKnown does not guarantee that any contact will receive, read, understand, or act on an alert.
- StayKnown does not guarantee real-time location, exact coordinates, exact address, building-level location, or perfect delivery.
- StayKnown does not guarantee intervention, rescue, prevention of harm, or a specific outcome.
- StayKnown does not monitor every session live or make emergency decisions for users or contacts.
5) What StayKnown can do
Depending on plan, region, device permissions, connectivity, feature availability, third-party providers, and user settings, StayKnown may support several safety functions.
- Send user-triggered safety notifications to trusted contacts.
- Share Visit status and location context during an active session where permissions allow.
- Support SOS alert flows where available.
- Support manual capture safety updates during active safety flows.
- Show safety history logs to help users review personal safety activity.
- Provide notification delivery context where available.
- Support chat, media, voice notes, translation, stories, stickers, and profile trust where enabled.
- Support verified stop flows for sensitive ending actions where configured.
6) What StayKnown cannot guarantee
- Real-time delivery of emails, push notifications, app updates, map links, or chat messages.
- Perfect location accuracy or continuous GPS availability.
- That a phone will remain charged, online, unlocked, permitted, or able to transmit data.
- That a contact will see, understand, believe, or respond to an alert.
- That emergency services will be contacted by a recipient.
- That official responders will act based on StayKnown data.
- That network providers, email providers, app stores, GPS, operating systems, payment providers, map providers, or hosting providers will perform without delay.
- That a safety event will prevent harm.
7) SOS use and limitations
SOS is a serious safety signal. It should be used only when the user needs urgent trusted-contact attention or feels unsafe.
- SOS may notify selected contacts depending on plan, settings, connectivity, permissions, and feature availability.
- SOS does not automatically call police, ambulance, fire service, rescue, 911, 112, 999, FRSC, NSCDC, NEMA, or any official emergency system unless a separate official emergency system is used.
- SOS does not guarantee that contacts are awake, online, reachable, willing, or able to help.
- SOS may include location context if permissions, device state, and network state allow it.
- SOS should not be used as a prank, test, threat, manipulation, false claim, or pressure tactic.
- In immediate danger, contact local emergency services directly.
Detailed rules for Visit sessions, LIVE sharing, SOS, manual capture, chat maps, VPN gates, and accuracy limits.
8) Visit, LIVE sharing, and manual capture limitations
Visit, LIVE sharing, and manual capture can help trusted contacts understand safety context, but they are not a guarantee of safety, location truth, or intervention.
- Visit sessions depend on location permission, GPS, network access, battery, device settings, app state, provider availability, and plan features.
- LIVE links may show delayed, approximate, incomplete, stale, or unavailable location data.
- Contacts should treat LIVE information as safety context, not exact proof of current location.
- A Visit ending does not guarantee the person is safe unless the user confirms safety through real-world communication.
- Manual capture may fail or delay if the device cannot get location or send data.
- Manual capture must not be used to spam, frighten, manipulate, mislead, or pressure contacts.
9) How trusted contacts should respond
Contacts receiving StayKnown alerts should act carefully, lawfully, and safely. They should not take unsafe action or treat approximate app data as absolute proof.
- Attempt safe direct contact first by calling or messaging the user where possible.
- Check whether the alert is SOS, Visit, manual capture, chat map, end state, or another safety update.
- If danger seems likely, contact the appropriate local emergency service or trusted local safety channel and provide relevant context.
- Do not attempt unsafe personal intervention.
- Do not publicly share the user’s location, profile, alert, chat, safety gallery, or map details unless necessary for safety or law.
- Treat timestamps, location, and place labels as approximate and potentially delayed.
Rules for approved contacts, SOS responders, consent records, blocked-add settings, removals, and trusted-contact duties.
10) Location accuracy limitations
Location data depends on many factors outside StayKnown’s full control. It may be approximate, delayed, stale, missing, or wrong.
- GPS may be weak indoors, underground, in dense buildings, in markets, in rural areas, on roads with poor coverage, or during poor environmental conditions.
- Battery saver, denied permissions, background restrictions, device settings, or app state may stop updates.
- Network issues may delay or prevent upload of location points.
- Reverse-geocoded place labels may be approximate, outdated, or unavailable.
- VPN, fake GPS, device tampering, modified apps, emulators, or unreliable network state may reduce location confidence.
- A displayed location may not represent the user’s exact current position.
11) Network, provider, and delivery delays
StayKnown depends on third-party systems such as mobile networks, operating systems, email providers, push systems, hosting providers, app stores, payment processors, maps, translation systems, and geocoding providers.
- Emails may be delayed, filtered, blocked, rejected, or sent to spam.
- Push notifications may be delayed by phone settings, battery saver, OS rules, or network state.
- Map links may load slowly or fail if the recipient has poor connectivity.
- App background behavior may vary across devices and operating systems.
- Third-party outages may affect alerts, maps, emails, storage, subscriptions, wallet, translation, or chat.
12) Nigeria, United States, United Kingdom, EU, and global emergency use
Emergency systems differ by country. StayKnown is not a replacement for any country’s official emergency system, government agency, police, ambulance, fire, medical, road safety, civil defence, or disaster-management service.
- In Nigeria, StayKnown is not the Nigeria Police Force, ambulance service, fire service, hospital, FRSC, NSCDC, NEMA, state emergency agency, private security, or any official authority.
- If immediate danger is suspected, users and contacts should use appropriate local channels, which may include trusted family, local police, medical help, FRSC, NSCDC, NEMA, state emergency agencies, private security, or nearby responsible responders depending on the situation.
- Network issues, power supply, rural coverage, city congestion, road conditions, device quality, and provider delays may affect StayKnown alerts and location accuracy.
- StayKnown should support safety awareness; it should not replace real-world emergency planning, direct calls, community support, or official help.
- In the United States, StayKnown is not 911, a public safety answering point, law enforcement, EMS, fire department, hospital, or rescue provider.
- If immediate danger is suspected, call 911 or the correct local emergency service.
- StayKnown data may be delayed, approximate, unavailable, or insufficient for official response.
- In the U.K. and EU, StayKnown is not 999, 112, police, ambulance, fire service, emergency dispatch, medical service, or official rescue.
- If immediate danger is suspected, use 999, 112, or the official local emergency number for the place where the event is happening.
- Local privacy, consent, emergency, telecom, child-protection, workplace, school, and safety laws may apply.
13) False emergencies are prohibited
False emergency use can cause panic, waste resources, damage trust, and endanger others. StayKnown prohibits false SOS events and misleading safety claims.
- Do not create fake SOS alerts.
- Do not create false Visit or manual capture events to manipulate contacts.
- Do not use emergency language to threaten, harass, scare, extort, or pressure someone.
- Do not use StayKnown to frame, mislead, lure, exploit, or endanger another person.
- Repeated false emergencies may result in feature restrictions, account suspension, permanent ban, preservation of records, and lawful cooperation where appropriate.
Detailed prohibited-use rules for false alerts, contact abuse, location misuse, chat abuse, payment misuse, and platform abuse.
14) Minors and vulnerable users
Emergency and safety features involving minors or vulnerable users must be handled with heightened care.
- Under 13 users are not permitted to create an account or use StayKnown.
- Minors who are permitted under policy require appropriate guardian permission and lawful safety use.
- StayKnown must not be used to groom, exploit, coerce, threaten, or secretly monitor minors.
- If a minor is in immediate danger, contact local emergency services or the proper local authority first.
- Reports involving minors may require urgent review and preservation of relevant records.
Dedicated rules for minors, guardians, families, schools, vulnerable users, and youth safety.
15) Records, history, preservation, and privacy
StayKnown may retain certain safety records to provide history, troubleshoot delivery, prevent abuse, investigate reports, comply with law, and support safety auditing.
- Safety session records may include start time, stop time, state changes, SOS events, and manual capture events.
- Notification records may include timestamps, recipient identifiers, and delivery status where available.
- Location records may exist only where permissions and feature state allowed collection.
- Records may be preserved where required by law or reasonably needed to investigate abuse, threats, false emergencies, fraud, or serious safety concerns.
- Retention does not guarantee every record exists or can be produced later.
16) Legal cooperation and emergency requests
StayKnown respects applicable law and may respond to valid legal process. In limited emergency circumstances, StayKnown may review urgent requests where disclosure may be necessary to prevent death, serious injury, kidnapping, trafficking, exploitation, or imminent harm.
- StayKnown may preserve records where required by law or where reasonably needed for safety review.
- StayKnown may disclose information if required by law or necessary to protect rights and safety, prevent fraud, prevent harm, or enforce policies.
- StayKnown may reject, narrow, or question requests that are overbroad, unlawful, unsafe, unclear, or connected to abuse.
- StayKnown does not support covert surveillance or unlawful monitoring.
Dedicated policy for official requests, emergency disclosures, preservation, legal process, and user notice.
17) Contact and related policies
For safety questions, abuse reports, legal concerns, emergency-related policy questions, security reports, or privacy requests, use the proper StayKnown support route.
- Support: support@stay-known.com
- If there is immediate danger, contact your local emergency number or official emergency authority first.
- Use Abuse Reporting for stalking, harassment, impersonation, false emergency use, unwanted contact, or unsafe behavior.
- Use Law Enforcement & Emergency Requests for official requests, preservation, emergency disclosure, or urgent legal concerns.
- Use Security Disclosure for vulnerability reports or platform-integrity concerns.
Main agreement for accounts, lawful use, safety limits, subscriptions, enforcement, and liability limits.
Anti-stalking, anti-harassment, anti-coercion, false emergency, and trusted-contact safety rules.
Visit sessions, LIVE sharing, SOS, manual capture, chat maps, VPN gates, and accuracy limits.
Approved contacts, SOS responders, consent records, blocked-add settings, and removal rights.
Report stalking, harassment, unwanted contact, false emergencies, impersonation, or unsafe use.
Responsible vulnerability reporting and platform-integrity route.
18) Changes to this Emergency Disclaimer
StayKnown may update this disclaimer to reflect new safety features, SOS behavior, manual capture changes, map providers, emergency-service expectations, legal requirements, country-specific language, provider limitations, or operational needs. If updates are material, StayKnown may provide notice through the app, website, email, or another reasonable method.
Appendix A — In-app short emergency notice
StayKnown does not replace emergency services, police, ambulance, fire service, medical care, rescue services, road safety agencies, civil defence, disaster-management agencies, 911, 112, 999, Nigerian emergency authorities, or official emergency dispatch in any country. If immediate danger exists, contact the official local emergency number or proper local authority first. StayKnown can help notify trusted contacts and provide safety context, but alerts, maps, chat, emails, push notifications, and location data may be delayed, approximate, unavailable, missed, or wrong. Do not create false emergencies or misuse SOS.