Apple sued OpenAI on July 10 for stealing its hardware secrets. On August 3, OpenAI’s answer arrived, and its central defense was not “we never took anything.” It was closer to an accusation of its own: Apple never took away the access.
That reframing is the part of this fight worth paying attention to. The headlines are chasing the theater, and there is plenty of it. Redacted iMessage logs. An outside lawyer who emailed the wrong person. A response from OpenAI that calls the suit “careless, aggressive, and oddly personal.” But underneath the drama sits a claim that should make every IT and security leader uncomfortable, because it is the claim most likely to be true in your own organization: former employees kept reaching internal files not because anyone conspired to steal them, but because nobody revoked their permissions.
What Apple actually filed
The original complaint, filed July 10 in the U.S. District Court for the Northern District of California, is a trade-secret suit built around two people. Tang Tan spent roughly 24 years at Apple as a vice president of product design, running hardware for the iPhone and Apple Watch, before leaving in 2024 for Jony Ive’s io. He is now OpenAI’s chief hardware officer. Chang Liu is a systems electrical engineer who spent eight years at Apple and left in January 2026 to join OpenAI.
Apple’s version is that OpenAI hired more than 400 of its former employees and encouraged some of them to carry Apple knowledge out the door: project code names dropped in recruiting conversations, coaching on how to evade Apple’s exit-security procedures, and, in Liu’s case, confidential files reached after he had already left. The suit asks for a preliminary injunction barring access to or use of Apple’s trade secrets, plus orders to preserve evidence. Behind all of it is the device Apple is most afraid of, the screenless, agent-first hardware OpenAI is building with Ive to compete with the iPhone. I wrote in July that the real fight was over that device, not the code. OpenAI’s response makes that even harder to argue against.
The chat logs OpenAI chose to publish
OpenAI did not respond with a general denial this time. It responded with receipts, in a public post titled “Apple is getting this wrong.” The company published a long set of redacted messages between Chang Liu and Apple employees, all dated after his last day on January 22, 2026.
On January 27, five days after Liu left, an Apple employee messaged him for a technical assessment, adding “you are the best. Even if you don’t work here anymore.” On February 14, the same person asked him for schematics information. On March 5, Liu was added to a group chat where he pointed Apple staff toward internal folders and contacts, then removed himself and called the situation “highly irregular.” OpenAI’s framing is blunt: the confidential information Apple says its former engineer improperly touched was information Apple’s own current employees kept asking him to help them find.
On Tang Tan, OpenAI’s line is that he set the rule the other way. According to its response, Tan told the hardware team from the start that “we do not want, and must not use, any confidential” information from Apple. OpenAI says it rejected Apple’s demand to inspect its devices and run forensic analysis, and summed up its position in one sentence: “We do not have, nor want, any of their trade secrets.”
The residual-access argument is the real story
Strip away the personalities and OpenAI’s strongest move is a single phrase: residual access. Its argument is that former Apple staff could still reach internal files after leaving because Apple does not always remove system permissions when someone walks out, and that this is a housekeeping failure, not a heist.
That argument lands because anyone who has run offboarding knows how often it is true. In more than twenty years running IT operations at a Saskatchewan telecom, the single most common security gap I saw was not a clever intrusion. It was an account that should have been dead and was not. A contractor whose VPN certificate outlived the contract. A shared drive permission granted for one project and never pulled. A departing engineer whose laptop was collected but whose cloud tokens kept working because the identity provider and the file store were never wired to the same offboarding switch. Deprovisioning is boring, it spans a dozen disconnected systems, and it is almost always somebody’s second priority. So it slips.
Apple’s complaint says Liu discovered a bug that let him reach Apple’s cloud storage after leaving. Read that as a practitioner and it is not a story about a thief. It is a story about an access-control boundary that failed open. If a departed employee can authenticate to your file store, the interesting question is not why he did, it is why he still could. Trade-secret law will spend months arguing over intent. Access governance does not care about intent at all. A permission is either revoked or it is not.
The uncomfortable lesson for enterprises watching this is that your trade-secret protection is only as good as your offboarding runbook, and most offboarding runbooks are worse than the ones the people writing them believe they have. The controls that matter here are unglamorous: identity that federates so that killing one account kills all access, automated deprovisioning triggered by the HR system rather than by a ticket someone remembers to file, periodic access reviews that flag credentials with no active owner, and short-lived tokens instead of ones that live until someone notices. None of that would make a headline. All of it would have made this lawsuit weaker.
An email that undercut the plaintiff
The detail doing the most damage to Apple’s credibility is smaller and stranger. Apple told the court it contacted OpenAI back in February 2026 about former employees holding confidential information and got no response for months. OpenAI’s evidence suggests the opposite happened.
Apple’s outside counsel, Gabriel Gross, sent an email to OpenAI general counsel Che Chang thanking him for a phone call and offering to cooperate. Chang replied that no such call had ever taken place. Gross later admitted the message was meant for a different former Apple employee whose surname was Wang, and had been sent to Chang by mistake. OpenAI’s characterization, that Apple confused two Asian surnames, is pointed, but the procedural problem is real: a filing that claims OpenAI went silent is contradicted by the plaintiff’s own lawyer thanking OpenAI for a conversation that the plaintiff now says was with someone else entirely. Roughly five months then passed between that muddled February contact and the July filing. That is not the timeline of a company racing to stop an active leak.
Why Apple is really fighting
A trade-secret suit is what a company files when it is losing on the terrain that actually matters and needs the losing to slow down. Apple is losing on two fronts here, and neither is code.
The first is talent. More than 400 former Apple employees now work at OpenAI, and the hardware brain trust behind the iPhone’s physical design, Tan among them, is now building the device meant to replace it. That is not a poaching incident. That is a migration, and it belongs to the same talent realignment reshaping every frontier lab. The second is distribution. Apple spent 2026 rebuilding Siri on Google’s Gemini and opening the iPhone to Claude and ChatGPT, an admission that it could not ship a competitive assistant on its own. A company confident in its next device does not usually sue the startup building a rival one. It ships.
There is also timing to consider. OpenAI is moving toward a public offering after its trillion-dollar S-1, and a hardware program is central to the platform story it wants investors to buy. A trade-secret cloud over that program is worth something to a competitor regardless of whether the underlying claim ever wins in court. Litigation does not have to prevail to be useful. It only has to hang around.
What to take from it
Watch the case for the law and you will get a long, slow fight over what Tang Tan said in recruiting meetings and what Chang Liu could and could not reach. Watch it as an operator and the takeaway arrived the day OpenAI published its response. The company being sued for taking secrets answered by pointing at the plaintiff’s own access controls, and the answer was plausible enough to reframe the story.
That should send you to your own offboarding process, not to a courtroom. Pull a list of accounts belonging to people who left in the last year and check what they can still touch. If the honest answer is “I am not sure,” you have the same exposure Apple is now litigating in public, minus the lawyers. The secrets that leak are rarely the ones someone schemes to steal. They are the ones sitting behind a door that a departure was supposed to lock and never did.