StayKnown Law Enforcement & Emergency Requests Policy for lawful process, preservation, and safety disclosures.

1) Legal request summary

StayKnown exists to help people move, visit, communicate, and share safety context with trusted people. Because the Service may process safety sessions, contacts, notifications, location context, account records, chat metadata, payment records, and abuse-prevention signals, legal requests must be handled carefully.

2) Legal request principles

• StayKnown respects applicable laws and may respond to valid legal process as required.
• StayKnown reviews requests for proper authority, scope, clarity, urgency, safety risk, and legal basis.
• StayKnown may reject, narrow, or ask for clarification if a request is overbroad, vague, informal, unsafe, or inconsistent with applicable law.
• StayKnown does not support covert surveillance, stalking, harassment, coercion, retaliation, or unlawful monitoring.
• StayKnown may preserve relevant logs and records where required by law or where reasonably needed to investigate abuse, threats, fraud, safety risks, or legal process.
• StayKnown may cooperate with lawful emergency requests where there is credible risk of death, serious injury, kidnapping, trafficking, exploitation, or imminent harm.
• StayKnown aims to protect user privacy while also supporting lawful safety, child protection, fraud prevention, and emergency needs.

3) Types of requests StayKnown may receive

StayKnown may receive different types of requests from law enforcement, courts, regulators, government agencies, lawyers, users, contacts, guardians, or safety reporters. Not every request results in disclosure.

A preservation request asks StayKnown to preserve existing records for a limited period while valid legal process is obtained. Preservation does not automatically mean disclosure.

Legal process may include a subpoena, court order, warrant, regulatory demand, legal notice, production order, or other formal request that is valid under applicable law.

Emergency requests may involve credible risk of death, serious physical injury, kidnapping, trafficking, exploitation, child-safety risk, or imminent harm. These requests are reviewed with urgency.

Users, contacts, and guardians may report abuse, stalking, harassment, threats, fraud, false emergencies, child-safety concerns, or suspicious activity. Those reports may lead to safety review, enforcement, record preservation, or legal cooperation where appropriate.

4) What legal requests should include

To help StayKnown review a request efficiently, legal requests should be specific, lawful, dated, signed where applicable, and tied to identifiable accounts or events.

• The requesting agency, court, authority, regulator, or legal representative.
• The name, title, badge number, agency reference number, court reference, case reference, and contact information of the requester.
• The legal authority for the request.
• The exact user, account, email, phone, username, session, alert, map link, contact, message, payment reference, or event being requested.
• The specific data requested and the relevant date/time range.
• The reason the data is needed and how it relates to the investigation, emergency, legal process, or preservation request.
• A signed document, court order, subpoena, warrant, preservation letter, emergency disclosure statement, or official letterhead where applicable.
• For emergency requests, a clear explanation of the imminent danger and why normal legal process cannot wait.

5) Categories of data that may exist

The data available depends on the user’s plan, device permissions, active features, region, retention settings, technical logs, provider systems, and whether the user actually used the relevant feature.

• Account identifiers, such as email, user ID, profile identifiers, username, and basic account metadata where available.
• Safety session records, such as Visit start time, end time, session state, SOS state, manual capture events, or history records.
• Location points during active safety sessions where the user granted permission and where records exist.
• Notification delivery metadata, such as recipient contact identifiers, delivery status, timestamps, email metadata, push metadata, and alert type.
• Contact approval, invitation, decline, expiration, removal, blocked-add, and consent-related records where applicable.
• Chat, stories, stickers, media, files, safety gallery, translation, or message metadata where features are enabled and retained.
• Device, network, VPN, security, rate-limit, fake GPS, platform-integrity, and abuse-prevention signals where available.
• Payment, subscription, wallet, coins, receipt, chargeback, refund, and fraud-prevention records where applicable.
• Support reports, abuse reports, enforcement notes, appeal records, preservation notes, and legal request records where applicable.

StayKnown may not always have the data requested. Records may not exist, may have expired, may not have been generated, or may not be available because permissions, feature states, provider behavior, or retention rules limited collection.

6) Preservation of records

Where required by law or reasonably needed to investigate abuse, fraud, threats, or safety risks, StayKnown may preserve relevant logs and records. Preservation is intended to prevent deletion or alteration of records while proper review or legal process is pending.

• Preservation may apply to safety session logs, location records, notification delivery records, abuse reports, account records, chat metadata, payment records, support records, or relevant security logs.
• Preservation does not automatically mean that records will be disclosed.
• Disclosure may still require valid legal process, emergency justification, user consent, or another lawful basis.
• Preserved records may be retained longer where required by law, legal process, safety investigation, fraud review, or abuse-prevention needs.
• A preservation request should identify the account, session, event, date range, and legal basis clearly.

7) Emergency disclosure requests

In limited emergency situations, StayKnown may disclose information if we reasonably believe disclosure is necessary to prevent death, serious physical injury, kidnapping, trafficking, exploitation, child-safety harm, or imminent harm.

• Emergency requests should identify the person at risk.
• Emergency requests should explain the immediate danger.
• Emergency requests should identify the specific StayKnown account, session, alert, contact, message, map link, or event involved.
• Emergency requests should come from an authorized emergency responder, law enforcement officer, safeguarding authority, child-safety authority, or appropriate authority where possible.
• StayKnown may ask follow-up questions or request formal legal process after emergency disclosure where appropriate.
• StayKnown may limit disclosure to what appears reasonably necessary for the emergency.

8) User notice

Where legally permitted and safe, StayKnown may notify a user when their information is requested. However, notice may be delayed or withheld when prohibited by law, when the request is confidential, or when notice could create risk.

• Notice may be withheld if legally prohibited.
• Notice may be delayed if it could compromise an investigation.
• Notice may be withheld if it could create risk of harm, retaliation, stalking, harassment, evidence destruction, child-safety harm, or platform abuse.
• StayKnown may challenge overbroad gag orders or confidentiality demands where appropriate and legally permitted.
• StayKnown may be unable to provide full detail about a request if doing so would violate law, expose another person, or create safety risk.

9) When StayKnown may reject, narrow, or challenge requests

StayKnown may reject, narrow, or challenge requests that do not meet applicable requirements or create safety, privacy, legal, or misuse concerns.

• Requests that are informal, unsigned, or lack legal authority.
• Requests that are too broad, vague, or not tied to identifiable accounts or events.
• Requests that seek data outside the relevant time period.
• Requests that conflict with applicable law, privacy obligations, or user safety.
• Requests that appear to support stalking, coercion, harassment, retaliation, political intimidation, unlawful surveillance, custody misuse, workplace misuse, school misuse, or non-safety misuse.
• Requests from private parties that require formal legal process before disclosure.
• Requests seeking data that does not exist, was not generated, has expired, or is outside StayKnown’s control.
• Requests that ask StayKnown to create new surveillance, monitor future activity, or secretly track a user outside lawful process.

10) International and cross-border requests

StayKnown may be used by people in different countries. Legal requests may involve cross-border issues, different privacy rules, different emergency systems, different child-protection rules, and different standards for disclosure.

• Requesters should use the appropriate legal process for their jurisdiction.
• Cross-border requests may require mutual legal assistance, court orders, production orders, diplomatic channels, regulator channels, or other formal routes.
• StayKnown may consider applicable privacy, human rights, safety, child-protection, due-process, and data-protection obligations when reviewing requests.
• Access to the Service may be limited in regions where sanctions, export controls, platform rules, app-store rules, payment restrictions, or legal restrictions apply.
• StayKnown may reject or narrow requests that conflict with applicable law or create safety risk.

11) Nigeria, United States, United Kingdom, EU, and global official-request context

Official request handling may differ by country. StayKnown may consider the location of the user, the location of the incident, the requester’s authority, the legal basis, the data location, the emergency risk, and applicable privacy or safety obligations.

• In Nigeria, StayKnown may receive reports or requests involving safety alerts, location context, contact abuse, fraud, scams, extortion, false SOS, kidnapping concerns, child-safety concerns, or emergency situations.
• Nigerian requests should identify the requesting authority, legal basis, account or event, relevant date range, and specific data requested.
• If immediate danger exists, 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, child-safety authorities, or nearby responsible responders depending on the situation.
• StayKnown does not replace Nigerian police, ambulance, hospitals, fire service, road safety, civil defence, disaster management, child-protection authorities, or any official authority.

• In the United States, StayKnown is not 911, law enforcement, EMS, fire department, child protective services, or rescue service.
• In the U.K. and EU, StayKnown is not 999, 112, police, ambulance, fire service, safeguarding authority, child-protection authority, or official emergency dispatch.
• European users may have stronger data protection rights, lawful-basis expectations, user notice rules, minimization requirements, and cross-border data handling requirements.
• In all countries, official requests should be lawful, specific, safety-aware, and tied to a clear legal or emergency basis.

12) Minor safety and vulnerable users

Requests involving minors, exploitation, trafficking, grooming, kidnapping, coercion, unsafe contact, or vulnerable users may require urgent review. StayKnown takes child safety and vulnerable-user safety seriously.

• If a minor is in immediate danger, contact emergency services or the proper local child-safety authority first.
• Reports involving minors should include the age or estimated age if known.
• StayKnown may preserve records where required or where reasonably necessary to prevent harm.
• StayKnown may cooperate with valid legal process or appropriate emergency requests involving child safety.
• StayKnown does not support unlawful monitoring, grooming, exploitation, or misuse of minor-related safety data.

13) Abuse investigations and platform integrity

StayKnown may review and preserve information when we detect or receive reports of abuse, fraud, stalking, harassment, false emergencies, repeated mass messaging, suspicious network behavior, payment abuse, attempts to bypass safeguards, or high-risk safety events.

• StayKnown may restrict accounts, devices, contacts, notifications, chat, stories, media, stickers, SOS, Visit features, payment features, wallet features, or other product surfaces.
• StayKnown may preserve logs and records when needed to investigate abuse, fraud, threats, or safety risks.
• StayKnown may cooperate with lawful requests where required or appropriate.
• StayKnown may take action even before receiving legal process where platform safety, user safety, child safety, fraud prevention, or abuse-prevention rules require it.
• StayKnown may withhold investigation details where disclosure would create risk, expose another user, violate law, or undermine platform integrity.

14) Retention limits and deletion requests

StayKnown may retain safety logs for a reasonable period to provide history, prevent abuse, resolve disputes, comply with legal obligations, support billing/accounting where applicable, and meet safety auditing needs. Some records may be retained longer where required by law or for legitimate safety interests.

• A deletion request may not remove records that must be retained for legal, security, safety, fraud-prevention, billing, child-safety, or abuse-prevention reasons.
• Preserved records may be held while valid legal process, emergency review, abuse investigation, payment dispute, fraud review, or dispute resolution is pending.
• Records not retained or not generated cannot be produced later.
• Backup copies or provider-level records may remain for a limited period where operational systems require it.

15) No covert surveillance or unlawful monitoring

StayKnown is not built to help anyone secretly track another person. Legal cooperation does not change the product’s anti-stalking and consent-aware purpose.

• StayKnown does not authorize users to track people without permission, lawful basis, or required consent.
• StayKnown does not support private parties using legal threats to obtain another person’s data outside valid legal process.
• StayKnown does not support use of the Service to violate protective orders, restraining orders, custody rules, workplace restrictions, school restrictions, or similar legal boundaries.
• StayKnown may restrict accounts or refuse requests that appear connected to stalking, coercion, intimidation, harassment, retaliation, custody misuse, workplace misuse, or non-safety monitoring.
• StayKnown may preserve or disclose information where lawful and necessary to prevent harm, but that does not make StayKnown a real-time surveillance service.

16) Contact for legal requests and related policies

For legal requests, abuse reports, preservation concerns, emergency safety concerns, or official request handling, contact StayKnown support. If there is immediate danger, contact the official local emergency number or proper local authority first.