The editorial argues that Tunick is not accused of any underlying offense — the deletion itself is the crime — which pushes the border search exception into new territory by treating a phone's contents as evidence the government is entitled to before articulating any crime. It frames the asymmetry as the core problem: no warrant needed to look, but a felony if you don't preserve.
The NYT filing surfaced by the HN submission documents that federal prosecutors are pursuing felony obstruction solely for the act of wiping a device during secondary inspection, with no smuggling, terrorism, or underlying charge attached. The reporting frames this as a novel and aggressive legal theory not previously tested against US citizens.
Commenters surfaced the analogy that this is the digital equivalent of being charged with obstruction for shredding documents a cop wanted to read on your kitchen table — except at the border, no warrant is required to demand the look in the first place. The thread frames the case as a live threat to anyone who travels with a laptop, because the traveler retains fewer Fourth Amendment protections than they would at home.
The editorial notes that for the last decade, security-minded lawyers and EFF have advised that CBP can compel unlocking but cannot criminally charge travelers for exercising their limited retained rights. The Tunick charge directly undermines that guidance, signaling that the practical playbook travelers have relied on may no longer hold.
On August 21, the New York Times reported that federal prosecutors have charged Samuel Tunick, a US citizen, with felony obstruction after he deleted data from his phone during a secondary inspection at a US port of entry. According to the filing, Tunick wiped content from the device while Customs and Border Protection officers were preparing to search it. He is not accused of smuggling, terrorism, or any underlying offense — the charge is the deletion itself.
The legal theory is aggressive. CBP has long claimed the authority to search electronic devices at the border under the border search exception to the Fourth Amendment, and the courts have mostly gone along, splitting only on whether "forensic" searches require reasonable suspicion. But the government has traditionally treated non-cooperation — refusing a passcode, wiping a device, using a burner — as grounds to seize the hardware, deny entry to non-citizens, or delay the traveler for hours. Charging a US citizen with a felony for the act of deletion pushes the doctrine into new territory: it treats your phone's contents as evidence the government is entitled to before it has articulated any crime.
The HN thread (766 points at time of writing) surfaced the obvious analogy: this is the digital equivalent of being charged with obstruction for shredding documents that a cop, without a warrant, wanted to read on your kitchen table. The difference is that at the border, the warrant requirement doesn't apply. That asymmetry — no warrant needed to look, but a felony if you don't preserve — is what makes the case a live one for anyone who travels with a laptop.
For most of the last decade, the practical advice from security-minded lawyers and EFF has been consistent: at the border, CBP can compel you to unlock, but they cannot compel you to remember a password, and they cannot charge you criminally for exercising the limited rights you retain. The Tunick charge, if it sticks, erodes that guidance. It creates a new category of border offense — anti-forensic behavior — that doesn't require the government to prove there was anything incriminating on the device in the first place.
That is a meaningful shift for the working developer. The people most likely to travel with devices containing sensitive data are not criminals; they are employees under NDA, contractors with client source code on their laptops, journalists with sources, security researchers with exploit code, and doctors and lawyers with privileged records. All of them have legal and contractual obligations to *not* hand that data to a third party — including, arguably, the US government at a border kiosk. The Tunick theory puts those professionals in an impossible position: comply and breach your NDA or your client's privilege; refuse or wipe and face a felony.
The community reaction has clustered around three responses. The civil-liberties camp argues the charge is unconstitutional on its face and will be tossed at the motion-to-dismiss stage; obstruction statutes require a nexus to a specific proceeding, and a warrantless suspicionless border search is not one. The practical-security camp points out that even if Tunick wins, the process is the punishment — he will spend a year and six figures fighting a case that most travelers would plead down. And the operational camp, which is where most engineers land, treats the ruling of the case as almost secondary to the operational reality: whatever the courts eventually decide, the border is now a place where deleting your own data can get you arrested, so plan accordingly.
It is also worth noting what CBP already does at scale. The most recent published figures show CBP conducted north of 40,000 device searches per year, up roughly 6x from a decade ago, with the overwhelming majority hitting US citizens and green-card holders returning home. Cloud sync being what it is, a "basic" search of an unlocked phone routinely pulls down full mail histories, Slack workspaces, GitHub tokens, and password manager vaults. The Tunick case is not an exotic scenario; it is what happens when the existing volume meets a prosecutor willing to test a new charge.
If you cross a US border with a device that touches production or client data, the guidance from corporate security teams is about to get louder, and it will look roughly like this:
Carry a travel device, not your daily driver. A clean laptop with a fresh OS, no cached credentials, no SSH keys, and no local repos. Re-provision from your MDM on arrival. This has been Google, Meta, and most FAANG-adjacent policy for years; expect it to become the default at any company with an active general counsel by Q4.
Push secrets out of the device before you travel, not at the border. The Tunick charge specifically punishes deletion *at* the crossing; it says nothing about the state of a device you carried across in that state to begin with. Rotate tokens, sign out of sessions, and remove local repos *before* you check in for your flight. If a CBP officer asks why your laptop is empty, "it's a travel machine, I work from the cloud" is a boring, true, and non-obstructive answer.
Assume full-disk encryption is table stakes but not a shield. FileVault and BitLocker protect a powered-off device from a lost-and-found scenario. They do not protect an unlocked device you just handed to an officer. The meaningful boundary is what is *on* the device when it crosses, not whether the disk is encrypted.
Update your incident-response runbook. If an employee's device is seized or imaged at a border, treat it as a credential-compromise event: rotate every token that touched that laptop, invalidate refresh tokens, and audit access logs for the seizure window. Do this even if the employee "cooperated fully" — especially then.
The Tunick case will probably take a year to reach a ruling that matters, and it may well be dismissed. But the signal has already been sent to line officers at every port of entry, and to every prosecutor with a device-search case that used to feel unwinnable. Regardless of how the case resolves, the operational answer for developers is the same one Snowden-era security folks have been quietly giving for a decade: the device you carry across a border should contain nothing you would not hand to a stranger, because functionally, that is what you are doing. The Tunick charge just made that advice harder to laugh off.
And this is why companies in the EU have a business travel rule to take a freshly wiped laptop on international trips, not just a locked one with a "distress code".
For exactly the border search scenario, I wish smartphones could be imaged and restored as easily as PCs. Imagine booting the phone from a flash drive, making an encrypted image of the phone on said drive, and writing a fresh OS before reaching the border.There's no deception required to protec
I read a pretty compelling argument by a lawyer that we're looking at this the wrong way. (I Am Not A Lawyer)Their point was that if the law is knocking on your door to legally search your house, and you have records of your criminal empire printed out in boxes in your attic, or just non-illega
The decoy passcode feature should boot into a separate partition that looks like a normal phone setup, and during that time quietly erase the user's actual data. They would never have known if it worked like this.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
From Universal Declaration of Human Rights (UDHR) accepted by the United Nations General Assembly on 10 December 1948-------- Article 12No one shall be subjected to arbitrary interference with his privacy, family, home or correspondence, nor to attacks upon his honour and reputation. Everyone has th