Know Your Enemy: The Border Phone Wipe and the Adversary We Actually Fight

Summary: Samuel Tunick triggered a GrapheneOS duress wipe on his Google Pixel during a warrantless but lawful CBP border search. He's now charged with destroying property to prevent lawful seizure. This episode rejects two easy narratives. First, that Tunick is a victim: he made a deliberate choice with foreseeable consequences, and agents operated within their authority. Second, that the privacy tool is the villain: GrapheneOS, like Signal, is legitimate infrastructure. Blaming encryption for occasionally protecting a bad actor is an old deflection. Key Points: Accountability, not victimhood - Tunick configured a feature designed to destroy data, knew what it did, and triggered it during an authorized search. That was a choice. The tool is never the strategy - A duress wipe defends against thieves, stalkers, or abusers. Triggered during a lawful search, the same feature becomes evidence destruction. Tools aren't the bad guys - Blaming the OS is the same trick: a tool that protects everyone sometimes protects a bad actor, therefore the tool is the threat. It's deflection. The fix they want removes protection from all of us. Law enforcement isn't the enemy - Treating the agent as a personal adversary leads to emotional, losing decisions where the law is most stacked against you. The real enemy is warrantless mass collection - Ad bidstream, data brokers, Big Tech retention, and license plate reader dragnets like Flock collect on everyone with no warrant because it's built into commerce. The real risk is getting swept into someone else's investigation - Geofence warrants order providers to hand over every device in an area during a window, sweeping up bystanders. Aim your OPSEC at the machine, not the badge and not your tools - Keep the tools, respect them, and deny the collection machine your data in daily life. Fight the system where it's vulnerable: local contracts, the courts, and your platform choices. Not Legal Advice: This episode discusses criminal cases and legal risk for general education. It is not legal advice, and Allen is not a lawyer. If you're ever in a situation like this, consult a licensed attorney.** Sources: - [US accuses American of wiping his phone with a duress password during a border search (TechCrunch)](https://techcrunch.com/2026/07/24/us-accuses-american-of-allegedly-wiping-his-phone-using-a-duress-password-during-border-search/) - [A man gave border agents his passcode. It wiped everything. Now he faces federal charges (Decrypt)](https://decrypt.co/374394/border-agents-phone-duress-passcode-grapheneos) - [Google tracked his bike ride past a burglarized home and made him a suspect (NBC News)](https://www.nbcnews.com/news/us-news/google-tracked-his-bike-ride-past-burglarized-home-made-him-n1151761) - [Google changes Location History to limit geofence warrants (The Register)](https://www.theregister.com/2023/12/15/google_location_history_geofence/) - [Get the Flock Out campaign (ACLU)](https://www.aclu.org/campaigns-initiatives/get-the-flock-out) - [Why some cities are ditching their Flock license plate readers (NPR)](https://www.npr.org/2026/02/17/nx-s1-5612825/flock-contracts-canceled-immigration-survillance-concerns) - [Digital privacy at the US border (EFF)](https://www.eff.org/issues/border-searches) Call To Action: Two things this week. First, examine the tools you rely on. For each one, ask not just what it protects you from, but when could it become a liability. Second, aim at the machine. Pick one source of ambient collection and cut it: reset your mobile ad ID, add DNS-level blocking, or find out whether your town runs Flock cameras and show up to the contract vote. For more visit OPSECPodcast.com. Your privacy and your security is your responsibility.