He handed over a passcode and his phone wiped — what really happened

“He set that up. He chose a code that would destroy everything on the device the instant it was entered.” — Allen Pace

A man named Samuel Tunick returned to Atlanta on January 24, 2025. At Hartsfield‑Jackson Customs and Border Protection pulled him into secondary inspection, asked for his Google Pixel passcode, and he gave them a code. The officer entered it and the phone ran a built‑in duress wipe instead of unlocking.

By July 2026 the Justice Department had charged Tunick under a federal statute that criminalizes destroying property to prevent lawful seizure — a charge that can carry up to five years. Tunick has pleaded not guilty and his lawyers argue the initial search was unlawful; that motion is part of the case now. But the concrete fact in the middle of the headlines is simple: a deliberate destructive action happened during a search the government was authorized to run.

Why the duress wipe is not the villain

Graphene OS — a hardened Android for Pixel devices — includes a duress code that permanently erases a device when that secondary code is entered. It exists for the explicit purpose of protecting someone who is being coerced under threat of physical harm (a mugger, an abusive partner, a violent attacker).

Blaming Graphene OS or duress wipes as if the product is a loophole for crime is the same framing security companies have seen for decades: “The tool protects everyone, including bad actors, so the tool is the problem.” That argument asks you to accept stripping protections from millions to catch the few. Allen is explicit: the tool is neutral; the judgment of the user is what matters.

“The tool was never the strategy. The judgment around the tool is the strategy.” — Allen Pace

Who is the real adversary

Don’t make the agent in front of you the enemy. The officers at the border were operating under existing policy and the border search exception — a legal area courts are still sorting out. Casting the individual agent as the adversary encourages escalation at the exact moment the law is stacked against you.

The structural problem Allen names is the ambient, warrantless commercial surveillance machine: ad bidstreams that broadcast location to hundreds of companies, data brokers stitching together a life into a “target package,” automated license‑plate systems like Flock Safety, and the growing use of geofence warrants that sweep every device in an area. Those systems create investigative dragnets that can pull innocent people into cases — the podcast cites Zachary McCoy, whose fitness app location data briefly made him a suspect in a burglary.

Google has moved its timeline storage to users’ devices (making certain geofence dragnets harder), but location still leaks from many channels. The fight that matters is at the system level: stop the mass collection and sale of everyone’s data, don’t just go after the tools people use to protect themselves.

Practical rules you can use

• Know your tools: understand exactly what a duress code, Signal, or Graphene OS does before you rely on it.

• Minimize data: generate as little exploitable data as possible in daily life so there’s less to be swept up by a geofence or ad bidstream.

• Know the scenario: the border has its own rules; when possible, travel with a sanitized device and download what you need on arrival.

• Aim your energy systemically: push local governments, courts, and platforms — that’s where rules and access change.

Allen’s closing point is crisp: Tunick made a choice and is facing the consequences; the tool and the officers are not the same thing as the surveillance systems that gather our lives. If you want to hear the full reasoning and case details, play the episode — the transcript and show notes include links Allen references.

Keep those distinctions clear, own your decisions, and spend your energy where it actually changes the rules.

For more go to OPSECPodcast.com