Privacy and Safety
Privacy and safety are often treated as the same goal in anti-violence technology, but for a Victim-Survivor they pull in opposite directions and must be balanced deliberately. The data that makes a safety tool useful — real-time Location Sharing, cloud backups, message logs kept as Evidence Documentation — is exactly the data an abuser will try to reach if they retain access to a device, account, or family plan. NNEDV’s Safety Net Project frames technology safety as protecting “safety, privacy, accessibility, and civil rights” together, and stresses that the burden should fall on holding perpetrators accountable, not solely on survivors restricting themselves. Yet practical safety planning still requires hard privacy choices: which device is trustworthy, which accounts are compromised, and what should never be stored where an abuser can find it.
This is why every safety app sits in tension here. A design that collects rich location history to “build evidence” also builds a honeypot that Stalkerware or a coercive partner can exploit, and the Datafication of MeToo critique shows how such collection can become extraction rather than protection. Privacy-protective alternatives respond with data minimisation, on-device storage, encryption, and Discreet Access, and safety guidance cautions that even removing monitoring can escalate danger if an abuser feels they’ve “lost control.” Getting this balance right is the central problem of Survivor-Centered Design and Trauma-Informed Design.
In this vault
- Tension withPersonal Safety Apps
- Threatened byStalkerware
- Related toDiscreet Access
- Related toSurvivor-Centered Design