UK government forced to disclose secret Apple backdoor order
- ID
- 48317
- Status
- summarized
- Published
- 19 Nov 2026, 11:32 PM
- Fetched
- 20 Nov 2026, 1:19 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/11/19/u-k-government-forced-to-disclose-secret-apple-backdoor-order/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 5.5
- Created
- 20 Nov 2026, 1:20 AM
- Tags
- Audience
- developerssaas_founders
What happened
The U.K.'s Investigatory Powers Tribunal ruled on Thursday 19 Nov 2026 that the Home Office must confirm it issued a secret 'technical capabilities notice' ordering Apple to hand over encrypted customer data, rejecting the government's claim that disclosure would damage national security. The order, first reported a year earlier, initially demanded a backdoor to customer data worldwide; it was later narrowed to British nationals' data stored in Apple's encrypted cloud, and Apple has challenged that narrowed version too. Apple refused the original demand and instead disabled its Advanced Data Protection end-to-end encryption feature for U.K. iCloud users; rights group Liberty International brought the challenge on behalf of two individuals, and a further hearing on what order details can be published is still pending.
Why it matters
Apple's response — turning off Advanced Data Protection for an entire country rather than comply — is the concrete precedent: an end-to-end encryption claim in your product can be switched off for a jurisdiction by an order you are legally barred from mentioning. If you sell to U.K. users or market 'we can't read your data', decide now what your fallback is (region-scoped feature flags, published transparency commitments) rather than discovering it after a notice lands.
Discussion angle
If a secret order can force a backdoor covering users outside the requesting country, does hosting encrypted data in a single jurisdiction still work for a small SaaS — or is per-region key custody now a product requirement rather than a compliance nicety?