StayKnown
STAYKNOWN

Safety & Anti-Stalking Policy

Version 1.0 • Updated: February 22, 2026

StayKnown is a safety product. This policy explains how StayKnown is intended to be used, what anti-stalking protections exist, and what we do when misuse is suspected or reported.

Safety first
StayKnown is designed for voluntary safety check-ins and alerts to trusted contacts. It is not designed for covert tracking or monitoring without consent.

1) Overview

Safety tools must be built carefully because they can be abused. StayKnown’s approach is: consent, transparency, user-control, and anti-abuse enforcement.

What StayKnown is for
  • A person starting a Visit session to reassure family while traveling.
  • A user sending an SOS alert to trusted contacts when they feel unsafe.
  • Contacts receiving safety emails that clearly show it is a safety tool and user-triggered.

2) Safety-by-design (how it’s meant to work)

  • User initiated: sessions and SOS are started by the account holder.
  • Stop anytime: ending the session stops sharing.
  • Trusted contacts: you choose who receives alerts.
  • No stealth: the product is not built for hidden tracking.
  • Abuse controls: rate limits, restrictions, and review processes exist to reduce misuse.

You must have a lawful basis and consent to share someone’s details or to notify them. You must inform your contacts that they may receive safety alerts.

  • Only add contacts you have permission to notify.
  • If a contact asks you to stop, remove them and stop sending alerts.
  • Do not use alerts to pressure, threaten, or intimidate someone.

4) Anti-stalking rules (strict)

  • No tracking without consent or knowledge (covert surveillance).
  • No harassment or intimidation via repeated alerts.
  • No using location to control a person’s movement.
  • No violating protective orders or legal restrictions.
Not allowed
  • Sending repeated alerts to someone who asked you to stop.
  • Using safety logs to threaten someone (“I know where you are”).
  • Using StayKnown to coordinate harm or exploit someone.

5) How contacts should respond to alerts

Contacts receiving alerts should use judgment. If the user appears in danger, contacts should call the user and contact local emergency services as appropriate.

  • If an SOS is received: try direct contact first if safe, then escalate to local emergency services where appropriate.
  • If location updates seem delayed: treat them as approximate—networks may delay delivery.
  • Never attempt unsafe intervention—use official emergency channels when needed.

6) Misuse prevention & enforcement

We may restrict accounts/devices/features if suspicious patterns are detected, including mass messaging, repeated false alerts, high-risk network signals, or repeated abuse reports.

  • Warnings → feature restrictions → suspensions → permanent bans (depending on severity).
  • We may preserve logs if required by law or necessary to prevent harm.
  • We may cooperate with valid legal process.

7) Reporting abuse

Email: support@stay-known.com

Include what happened, dates/times, and any screenshots you can safely share. If you are in danger, contact your local emergency number first.

Appendix A — In-app text this policy expands

  • StayKnown is not designed for covert surveillance and is not intended for stalking, harassment, or monitoring anyone without permission.
  • You may not use StayKnown to stalk, harass, intimidate, or threaten anyone, or track people without consent or knowledge.
  • Violations may result in warnings, restrictions, suspensions, or permanent bans.
A 6 Clement Joshua service
2026 • stay-known.com