DoJ says courts should require Apple to decrypt data on iOS devices because software is “licensed, not sold” to customers
DOJ dismisses Apple's arguments against decrypting iOS communications — The U.S. government rejected Apple's arguments in federal court …
Context & Ripple Effects
In October 2015 the DoJ urged courts to require Apple to decrypt iOS devices on a novel legal theory: because iOS software is "licensed, not sold," customers never fully own it, so the company that controls the license can be compelled to open what it licenses. The argument matters because it targets Apple's business model itself — every iPhone ships with code Apple retains rights over.
The theory did not stay abstract: by April 2016 the government was applying it in a Brooklyn drug investigation, telling the court in writing that it still needed Apple's help to crack the phone, and Apple answered by opposing the unlock and arguing the government had not proven its assistance was actually necessary. The dispute has moved from principle to a live courtroom test of whether license control equals decryption obligation.
First-order effects
- Apple now faces direct courtroom pressure to provide decryption assistance in individual cases, with its own software licensing terms being used as the legal lever against it.
- The Brooklyn investigators' path forward depends on the court accepting or rejecting the claim that Apple's help is indispensable — Apple's necessity counter-argument directly determines whether the case proceeds.
Second-order effects
- If the licensed-not-sold framing gains traction, every vendor whose operating system is delivered under license — effectively all smartphone makers — inherits the same compelled-assistance exposure, turning encryption design choices into legal risk decisions.
- Apple's incentive shifts toward architectures where even it cannot decrypt customer data, because technical impossibility is the only clean answer to a court order premised on vendor capability.
Third-order effects
- A court precedent treating software as a revocable vendor service rather than purchased property would restructure the legal status of all consumer computing — governments could route law-enforcement demands through licensing relationships instead of legislation, keeping the encryption fight inside individual cases and out of Congress.
- The pattern points toward an industry split between vendors who retain decryption capability (and therefore compellability) and those who engineer it away, with buyers' privacy expectations reshaped accordingly — though which way courts land remains genuinely unsettled.
The trend: Governments are increasingly pressing their decryption demands through the software-licensing model itself — treating vendor control over licensed code as leverage — making encryption policy a courtroom-by-courtroom fight rather than a legislative one.