Know Your Enemy: The Border Phone Wipe and the Adversary We Actually Fight
1Transcript1 turns · 19 min
A man handed his phone passcode to a federal agent, and the phone erased itself. He set that up. He chose a code that would destroy everything on the device the instant it was entered, and he handed it over during a search that the agent was legally authorized to run. The phone wiped, and now he is being charged with a federal crime. Let me say the part a lot of media coverage is dancing around. This is not a story about a victim. It is a story about a decision, and that decision has consequences. Today, we talk about what actually happened, why the privacy tool involved is not the villain, and how to think clearly about who the real adversary is. I am Alan Pace, and this is the OPSEC Podcast. Let me lay out the facts, because the details here matter. The man's name is Samuel Tunick. He's an American citizen and an activist out of Atlanta, Georgia. On January 24th, 2025, he flew home from the Dominican Republic and landed at Hartsfield-Jackson Airport. Customs and Border Protection pulled him into secondary inspection, took his Google Pixel phone, and asked for the passcode. He gave them a code, and the officer entered it, and instead of unlocking the device, the phone wiped itself completely. That phone was running Graphene OS, a hardened version of Android that installs on Pixel devices. Graphene OS offers a duress pin function. You set a secondary code, and if that code is entered, the phone does not unlock. It instantly and permanently wipes the device beyond recovery. The feature was added for a specific scenario. Someone physically compelled to hand over their phone under duress. In 2026, the Justice Department's charges became public. Tunick was charged under a federal statute that criminalizes destroying property to prevent its lawful seizure. It carries up to a five-year federal prison sentence. Legal and security experts say that this is the first known case in the United States of a person being federally charged over data destroyed by a duress password. And here's the update. Tunick has pled not guilty, and his lawyers have filed a dismissal for the case, arguing that initial search and seizure at the border were themselves unlawful. So the fight now is partly about whether the border search was valid in the first place. The case is not finished, and the court will decide the specifics. but strip away the framing and the core is simple. A destructive action was taken during a search the government was authorized to run, and that is what the charge is about. Here is the law as it stands, stated plainly and without any spin or opinion of it. The border search exception gives agents broad authority to inspect electronic devices at the border at a much lower bar than they would need anywhere else in the country. Courts are still sorting out exactly how far that reaches for funds, and in Tunick's motion, to dismiss is aimed right at that question. Whatever a court ultimately decides, the agents in the room were operating inside the authority of the law currently given to them. Here's where I part ways with a lot of the coverage that we see in the media. A good deal of it wants to make Tunick a martyr, a privacy hero caught in the
2Episode notes
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