Digital Privacy at Protests: Protecting Your Emergency Communication
Your phone is the weak point at a demonstration. See how server-side check-ins and a message encrypted for each contact still work if it is seized.
On this page
TL;DR
Nine in ten U.S. adults carry a smartphone, and a standard SMS travels unencrypted. If your phone is seized, unlocked, or intercepted, every contact and message on it is exposed. An emergency message encrypted for each contact, which opens only with their PIN, keeps the sensitive part of your plan out of the alert email, and the alert fires from the server even if your device is gone.
Who is this for?
Anyone attending protests, demonstrations, marches, or large public gatherings who needs to keep emergency contacts informed without exposing their communication to surveillance, device seizure, or network interception.
Why Is Digital Privacy Critical at Protests and Large Gatherings?
Digital security belongs in every protest plan. The Electronic Frontier Foundation documents cell-site simulators (commonly called “Stingrays”) in use by U.S. law enforcement. They capture the identifiers of every phone within range, and some models can intercept calls and texts. Standard SMS travels unencrypted and can be read by any intermediary.
Meanwhile, 91% of U.S. adults own a smartphone (Pew Research, 2025), and device seizure during arrests exposes contact lists, message history, and location data. What matters is whether your communications are encrypted when they are intercepted.
91%
of U.S. adults own a smartphone (Pew Research, 2025)
75+
U.S. law enforcement agencies in 27 states and D.C. own cell-site simulators (ACLU tracker, last updated 2018)
0%
of standard SMS messages are encrypted between sender and recipient (SMS is not end-to-end encrypted)
- One password reused across accounts is enough for a single breach to open all of them
- Zero location data in a Safety Checkpoint alert: your message holds a position only if you put one in yourself
What Are the Main Digital Risks at Protests?
Understanding these threat vectors helps you choose the right countermeasures before you attend.
What Protocols Protect Your Emergency Communication?
Four layers of protection, from device hardening to post-event auditing.
01
Pre-event device hardening
Reduce the attack surface before you leave. Disable biometrics (Face ID / fingerprint), enable a strong alphanumeric passcode, and turn off lock-screen notifications.
Setup · Set up your Safety Checkpoint check-in protocol before the event. Your emergency message is encrypted separately for each contact, and so are saved links and documents on paid plans. Even if your device is seized, the server-side alert fires independently.
02
Encrypted check-in messaging
The sensitive part stays out of the alert itself. The alert email tells your contacts to open your emergency page, where the message and saved links are decrypted in their browser after their PIN.
Setup · The alert travels as a normal email, and as an SMS on Survival ($9.99/mo), and carries nothing you wrote: your name, the protocol, the missed time and a link. Put lawyer details in the message, and documents and credentials in the package on paid plans.
03
Minimal data exposure
Carry the least information possible. Log out of social media, disable location services for all non-essential apps, and clear your browser history before attending.
Setup · Your Safety Checkpoint check-in holds what you wrote, plus what the server needs to run it (its times, your contacts). There is no GPS breadcrumb trail and no continuous location sharing. The only positions are the one you insert with the GPS button while writing and, on a location protocol, the destination and the place you confirm from.
04
Post-event audit
After the event, review which apps accessed your location, check for unfamiliar login sessions, and rotate passwords for any accounts accessed on the device.
Setup · Stop your event-specific check-in protocol once you're safe, then delete it. A deleted protocol can no longer alert anyone and its files are purged 30 days later, but its record stays on the server until you delete your account.
Safety Checkpoint Encryption Breakdown
What is encrypted, how it’s encrypted, and who can access it, with no vague “military-grade encryption” claims.
How to Set Up a Secure Protest Check-in
Four steps the night before. Your check-in protocol runs independently once activated.
Harden your device
Disable biometrics and switch to an alphanumeric passcode. Turn off lock-screen notifications and previews. Log out of social media apps. This limits what's accessible if your phone is seized.
Create your encrypted check-in
Write your emergency message: "I'm attending [event] at [location]. If you're reading this, I did not confirm safe by [time]. Please call me, then contact [backup]." The alert email does not carry it. The message is encrypted for each contact (AES-GCM, with the key wrapped for each contact's key), and so are saved links, credentials and documents on paid plans.
Set your timer and delay
Schedule the check-in for when the event is expected to end. Set a 1–2 hour delay after the deadline (Delayed Delivery) to account for delays, crowd dispersal, or transit. If you don't confirm within the window, the alert fires.
Add and verify contacts
Choose contacts who are NOT attending the same event. Each contact accepts your email invitation and is given a PIN, and your message opens only with it. On the Survival plan ($9.99/mo), the alert also goes out by SMS for the contact who is not watching email.