Last reviewed: November 17, 2026
Our approach
The people who use this site may be watched by someone who wants to find or hurt them, so we design for that. No system is perfectly secure, and we will never claim to be “unhackable.” Here is what we do and what we don't.
What runs on your device
The safety screening, safety plan, evidence checklist, police report composer, protective-order statement builder, cease-and-desist letter, and safety audit run in your browser. What you type into them is not sent to our servers.
No tracking
We do not use advertising pixels, third-party analytics scripts, or session recording. Our Content Security Policy blocks scripts from other websites. We see only aggregate traffic counts from our hosting provider.
What we store, and how
We store information only when you send it to us on purpose: a newsletter sign-up, or a data removal request. For removal requests:
- Your name, email address, and links are encrypted before they are saved (AES-256-GCM).
- Confirmation links are single-use, expire in 24 hours, and are stored only as a one-way hash.
- Unconfirmed requests are deleted automatically.
- We never store IP addresses. Abuse limits use one-way hashes.
Connection security
Every page is served over HTTPS with HTTP Strict Transport Security, and strict browser security headers that stop other sites from framing our pages or reading responses.
Report a vulnerability
Email security@stalking.org. Please include steps to reproduce. Do not include anyone's personal information.
Please test only against your own data, don't access or change other people's data, don't degrade the service, and give us reasonable time to fix the issue before disclosing it. We will not pursue legal action against good-faith research that follows these rules. Our machine-readable contact is at /.well-known/security.txt.