Last updated: March 21, 2026

A burner phone for protests provides separation between your protest participation and your primary identity, reducing law enforcement tracking risk and protecting contacts. This guide covers selecting appropriate hardware, configuring secure messaging, protecting evidence of police conduct, and operational security practices that minimize law enforcement surveillance during demonstrations.

Table of Contents

Why Burner Phones Matter for Protest Safety

Law enforcement attends protests with cell-site simulators (Stingrays) that intercept signals from all phones in an area. This technology identifies which phones were present at a location and when. Police can later cross-reference this data against subscriber information to target specific participants.

Additionally, if police confiscate your primary phone, burner phone separation prevents them from accessing protest contacts, messages, and communications. Digital evidence of police misconduct (photos, videos, audio) stored on a burner phone remains protected if your primary phone is seized.

Burner phones also prevent protest participation from appearing on your digital timeline. Your primary phone’s location data, if searched by law enforcement, won’t show protest attendance if you’re not carrying it.

Prerequisites

Before you begin, make sure you have the following ready:

Step 1 - Phone Selection

Buy a used phone in cash from a private seller to avoid purchase records. Avoid brand-new phones whose serial numbers are registered to you. Target older models (2-3 years old) because they’re cheaper used and less likely to have biometric authentication that law enforcement could force you to unlock.

Recommended specifications:

Why Android - Android allows installation of custom ROM (operating system) for maximum control and privacy. iOS requires relying on Apple’s default configurations and is harder to configure for forensic security.

Avoid - Brand new phones (purchase traceable to you), flagship models (distinctive to identify you with), phones with known security vulnerabilities.

Purchasing approach - Search local Facebook Marketplace, Craigslist, or OfferUp. Negotiate by text before meeting. Meet in a location with security cameras (retail stores, busy areas) to provide alibi if police question the purchase later. Pay cash. Do not provide your real name or contact info beyond the phone number you’re using.

Step 2 - SIM Card Setup

Use a prepaid SIM card purchased with cash. Bring only your burner phone and cash to the store, no ID, no wallet with identification.

Prepaid SIM options:

Activation process:

  1. Buy prepaid SIM with cash
  2. Do not provide ID, name, or personal information
  3. Use a generic name if system requires one (“John Smith” with birth date 01/01/1950)
  4. Provide a temporary email address (create throwaway email separately)
  5. Do not link to your primary phone, address, or any identifying information
  6. Activate minimal data plan ($5-10/month prepaid)

US carriers are increasingly requiring ID verification for activation. Some states require ID for any SIM purchase. Research your state’s requirements beforehand. If ID is required, use the burner phone setup as one-time protection with assumption that you’re identified but messages remain private.

Step 3 - Configure the Operating System Configuration

Before installing any apps or connecting to networks, configure the phone for privacy.

Android Setup:

  1. Power on without connecting to Wi-Fi or cellular
  2. Select “Skip” for all setup wizards and account linking
  3. Go to Settings → About → Build Number (tap 7 times to enable Developer Options)
  4. Go to Developer Options → Enable “USB Debugging”
  5. Disable location services: Settings → Location → Off
  6. Disable Wi-Fi: Settings → Wi-Fi → Off
  7. Disable Bluetooth: Settings → Bluetooth → Off
  8. Enable flight mode: Settings → Network & Internet → Flight Mode → On
  9. Only enable cellular connection (keep flight mode, tap airplane icon, disable flight mode for cellular only)
  10. Disable all Google services: Settings → Accounts → Remove any Google accounts

App Installation:

  1. Connect to burner phone via USB cable on a secure computer
  2. Install apps via USB without connecting to Google Play (prevents tracking via app install)
  3. Alternative: Use F-Droid app store (open source, privacy-focused)

Use ADB to install apps directly from your computer without touching Google Play:

Verify the burner phone is connected via USB
adb devices

Install Signal APK downloaded from signal.org
adb install Signal-Android-7.5.2.apk

Install F-Droid app store for future installs
adb install F-Droid-1.20.0.apk

Disable Google Play Services to prevent tracking
adb shell pm disable-user --user 0 com.google.android.gms
adb shell pm disable-user --user 0 com.android.vending

Verify disabled packages
adb shell pm list packages -d

Step 4 - Communication Apps

Select messaging apps that use end-to-end encryption and don’t require phone verification.

Signal

Briar

Wire

Jami (formerly GNU Ring)

Apps to avoid - WhatsApp (Facebook owned, metadata logged), Telegram (not fully end-to-end encrypted by default), Google Messages, Facebook Messenger.

Step 5 - Evidence Collection Setup

Protect photos and videos of police conduct with automatic encryption and secure backup.

Camera Configuration:

  1. Use default camera app (minimal metadata leakage)
  2. Disable geotagging: Camera app → Settings → Location tags → Off
  3. Disable saving to cloud: Settings → Disable Google Drive, OneDrive, Dropbox

Evidence Encryption:

  1. Install Nextcloud (encrypted cloud storage): Download APK from official source
  2. Set up Nextcloud account on non-protest email
  3. Configure automatic photo backup with client-side encryption
  4. Photos backup automatically and encrypted without your phone seeing plain content

Alternative - Local Encryption:

  1. Install VeraCrypt (open source disk encryption)
  2. Create encrypted volume for evidence storage
  3. Mount only when backing up evidence
  4. Keep volume unmounted during protest (evidence protected even if phone seized)

You can also encrypt evidence files directly on the phone using the age encryption tool via Termux:

Install Termux from F-Droid, then install age
pkg install age

Generate an encryption key pair
age-keygen -o protest-key.txt

Encrypt a photo or video file
age -r age1yourpublickeyhere -o evidence_encrypted.age DCIM/Camera/IMG_20260322.jpg

Encrypt all photos from today's protest
find DCIM/Camera -name "*.jpg" -newer /tmp/protest_start \
  -exec age -r age1yourpublickeyhere -o {}.age {} \;

Securely delete the unencrypted originals
shred -u DCIM/Camera/IMG_20260322.jpg

Step 6 - Operational Security During Protest

Phone Management:

Communication Protocol:

Location Awareness:

Law Enforcement Interaction:

Step 7 - Digital Forensics Protection

If law enforcement images your phone (forensic copy), maximize time between protest and forensic examination.

Forensic Delay Tactics:

  1. Create large video files in encrypted folder (forensic examination takes hours per GB)
  2. Fill remaining storage with dummy videos (unnecessary data increases analysis time)
  3. Change phone time to future date (confuses some forensic tools)
  4. Use encryption on entire phone filesystem (SlimRoms, Graphene OS on supported models)

Better approach - Don’t store sensitive evidence on the phone long-term. Back up evidence to encrypted cloud storage immediately after protest, then delete from phone.

Step 8 - Post-Protest Procedures

After protest:

  1. Back up evidence photos/videos to encrypted Nextcloud
  2. Verify backup succeeded
  3. Delete all evidence from phone
  4. Clear message history (Signal: chats → Settings → Data & Storage → Clear All)
  5. Document protest observations in writing (on computer, not phone)
  6. Do not connect burner phone to Wi-Fi
  7. Power down burner phone and remove SIM

One week later:

  1. Factory reset burner phone: Settings → System → Reset → Erase all data
  2. Remove SIM
  3. Destroy SIM card (cut into pieces, burn)
  4. Sell phone back via Facebook Marketplace (different seller than purchase to create distance)

Before factory reset, overwrite free space to make data recovery harder:

Connect via ADB and fill free space with random data
adb shell dd if=/dev/urandom of=/sdcard/wipe_fill bs=1M
Wait until "No space left on device" error appears
adb shell rm /sdcard/wipe_fill

Then perform factory reset via ADB
adb shell am broadcast -a android.intent.action.MASTER_CLEAR

Step 9 - Legal Context

Using a burner phone is legal. Burner phones have legitimate uses: protecting privacy, separating work/personal contexts, preventing identity theft. Simply possessing a burner phone is not illegal.

Law enforcement may investigate burner phone use as suspicious behavior if discovered. However, demonstrating that this was your only communication during protest (all encrypted) provides strongest defense that you were not orchestrating illegal conduct.

If arrested, your attorney will advise you whether to produce the phone or assert Fifth Amendment rights. Follow legal counsel, not this guide.

Cost Summary

The cost is low relative to legal expenses if you’re identified and charged. Even if you never use the burner phone setup, understanding these practices reduces anxiety about protest attendance and government surveillance.

Troubleshooting

Configuration changes not taking effect

Restart the relevant service or application after making changes. Some settings require a full system reboot. Verify the configuration file path is correct and the syntax is valid.

Permission denied errors

Run the command with sudo for system-level operations, or check that your user account has the necessary permissions. On macOS, you may need to grant terminal access in System Settings > Privacy & Security.

Connection or network-related failures

Check your internet connection and firewall settings. If using a VPN, try disconnecting temporarily to isolate the issue. Verify that the target server or service is accessible from your network.

Frequently Asked Questions

How long does it take to set up a burner phone for protests?

For a straightforward setup, expect 30 minutes to 2 hours depending on your familiarity with the tools involved. Complex configurations with custom requirements may take longer. Having your credentials and environment ready before starting saves significant time.

What are the most common mistakes to avoid?

The most frequent issues are skipping prerequisite steps, using outdated package versions, and not reading error messages carefully. Follow the steps in order, verify each one works before moving on, and check the official documentation if something behaves unexpectedly.

Do I need prior experience to follow this guide?

Basic familiarity with the relevant tools and command line is helpful but not strictly required. Each step is explained with context. If you get stuck, the official documentation for each tool covers fundamentals that may fill in knowledge gaps.

Is this approach secure enough for production?

The patterns shown here follow standard practices, but production deployments need additional hardening. Add rate limiting, input validation, proper secret management, and monitoring before going live. Consider a security review if your application handles sensitive user data.

Where can I get help if I run into issues?

Start with the official documentation for each tool mentioned. Stack Overflow and GitHub Issues are good next steps for specific error messages. Community forums and Discord servers for the relevant tools often have active members who can help with setup problems.

Related Articles