OpenAI's answer to Apple: "You built that access yourselves"

On August 5, 2026, a document landed on the electronic docket of the U.S. District Court for the Northern District of California in San Jose. Case No. 5:26-cv-07078-EJD, docket entry 59. The title: Defendants' Motion to Dismiss Apple Inc.'s Complaint. Two law firms signed it — Quinn Emanuel Urquhart & Sullivan's Andrew H. Schapiro for OpenAI Foundation, OpenAI Group PBC, io Products and Tang Yew Tan, and Kwun Bhansali Lazarus's Kate Lazarus for Chang Liu, who is represented separately.

The tone is set in the opening line. "Apple built its reputation by paying close attention to the smallest details. This lawsuit does the opposite." Then the filing takes a phrase straight out of Apple's own July complaint — Apple wrote that OpenAI's hardware business is "rotten to its core" — and returns it to sender: Apple's complaint is, "to borrow its own phrase," rotten to its core. If you expected the flat, hedged register of federal motion practice, this is not that.

Here's the part that matters, though, and it isn't the rhetoric. OpenAI has put Apple's own IT policy at the center of its defense. The argument runs like this: the "unauthorized access" Apple is calling theft was not engineered by OpenAI employees. It was produced by Apple encouraging staff to use personal iCloud accounts for company work, and then failing to cleanly manage access across its systems when those people left. A footnote in the motion states the point bluntly — that intermingling company information with employees' personal information, in an account the company does not even control, "further demonstrates that Apple has failed to allege reasonable measures."

In a trade secrets case, that is a shot at the joint, not the armor. Under the federal Defend Trade Secrets Act, a plaintiff has to plausibly allege three things: that it owns a sufficiently identified, protectable trade secret; that a defendant misappropriated it; and that the misappropriation caused injury. Baked into the first element is the requirement that the owner took reasonable measures to keep the information secret. OpenAI is trying to knock out that requirement using Apple's internal practices as the exhibit. It is an unusual posture — the plaintiff's own security housekeeping becoming the defendant's best weapon.

One structural note before going further. This is a Rule 12(b)(6) motion, which means OpenAI is not yet contesting the evidence. It is arguing that even if every fact in Apple's complaint is taken as true, the claims still fail as a matter of law. The motion says so explicitly: the other facts showing Apple's claims are meritless "will be shown in Defendants' forthcoming response to Apple's motion for preliminary injunction." So this filing is the opening move, not the fight. The evidentiary brawl is scheduled for mid-August.

Apple, five defendants, and Judge Davila

The cast list first. Apple filed the complaint on July 10, 2026, in the San Jose Division of the Northern District of California. It was initially assigned to Magistrate Judge Virginia K. DeMarchi and now sits with District Judge Edward J. Davila — which is why the early filings carry the suffix -VKD and the recent ones read -EJD.

There are five defendants: two individuals and three entities. Chang Liu spent eight years at Apple as a senior system electrical engineer and resigned on January 22, 2026, to join OpenAI. Tang Yew Tan spent twenty-four years at Apple, most recently as Vice President of Product Design for iPhone and Apple Watch; he is now OpenAI's Chief Hardware Officer. The corporate defendants are OpenAI Foundation (formerly OpenAI, Inc.), OpenAI Group PBC, and io Products LLC (formerly io Products, Inc.).

io Products being on that list is the skeleton of the whole dispute. io was co-founded by Sir Jonathan Paul Ive, Scott Cannon, Evans Hankey, and Tang Yew Tan — a founding team drawn largely from Apple's hardware and design leadership. OpenAI announced its acquisition of io in May 2025 in an all-stock deal valued at roughly $6.5 billion, and io's staff folded into OpenAI's hardware effort. So Apple is not litigating against an unfamiliar rival. It is litigating against a company staffed by the people who used to build iPhones down the hall.

One number sets the temperature. In paragraph 53 of the complaint, Apple states that "over four hundred former Apple employees" now work at OpenAI. OpenAI's motion cites the same paragraph and reframes it: since io's founding, "hundreds of Apple designers and engineers have chosen to leave their jobs at Apple to join OpenAI's effort to design a new family of devices for the AI era." Same headcount, two completely different stories — organized poaching versus ordinary California labor mobility.

The legal rosters tell you nobody is treating this as a nuisance case. Apple retained Weil, Gotshal & Manges (Gabriel S. Gross, Christopher W. Henry, Rachel L. Weiner Cohen) alongside Desmarais LLP (John M. Desmarais). OpenAI has Quinn Emanuel's Schapiro, Patrick D. Curran, Jodie W. Cheng, David Eiseman and Yehuda Goor, with Liu separately represented. Both sides are paying for top-shelf trade secrets counsel.

And there's the awkward business context. Apple and OpenAI are suing each other while remaining commercial partners: ChatGPT is integrated into Apple Intelligence, and Apple's complaint includes a footnote clarifying that the written agreement governing that integration "is not at issue here." Meanwhile, in January 2026 Apple announced that Google's Gemini would power its rebuilt Siri, in a deal reported at roughly $1 billion a year. When OpenAI's motion closes by referencing Apple's "failures to integrate AI into its products," it is aiming at exactly that triangle — and it also explains why Apple is defending hardware secrets this hard. When a company has outsourced its frontier AI layer to a partner, hardware is the differentiation it has left.

What the motion actually argues — four pillars

The filing runs 34 pages including the cover, tables and authorities, with the argument itself carrying through page 25. (Several outlets described it as a 31-page motion; the docketed PDF is 34 pages.) The structure is clean: Apple's first through fourth claims under the DTSA fail element by element, and the fifth and sixth claims for breach of contract lose their jurisdictional footing once the federal claims go.

Pillar one: identification. OpenAI argues that what Apple listed in paragraph 40 of the complaint is not a set of trade secrets but a set of buckets. The five categories are "Hardware Engineering and Product Design," "Manufacturing Design, Industrial Design, and Process Engineering," "Component Technologies," "Proprietary Testing, Validation, and Development Methodologies," and "Global Supply Chain Operations, Supplier Relationships, and Proprietary Business Operations." The motion calls that "a laundry list of generic categories that could encompass any and all information relating to development of any hardware product," and leans on the Ninth Circuit's 2025 Quintara Biosciences decision, which requires a trade secret plaintiff to identify a secret with sufficient particularity rather than "simply rely upon catchall phrases or identify categories of trade secrets."

Then comes the sharpest counterpunch in the brief: Apple already won on this exact argument, from the other side of the table. In Masimo Corp. v. Apple Inc., Apple persuaded a court that listing "some examples of what is within the broad" categories asserted did not narrow an otherwise sweeping claim, and the complaint was dismissed. OpenAI quotes that ruling and applies it to the example lists Apple appended after the word "includes" in each of its own five categories. Turning an opponent's prior victory into the instrument of its defeat is an old move, and it lands.

Pillar two: reasonable measures. This is where the iCloud argument lives, and OpenAI pairs it with specifics. By Apple's own description in the complaint, when an employee left for OpenAI, Apple would "walk them out" and "promptly remove them from the company rather than giving them a standard two weeks." In Liu's case that walkout was so hasty that — again per Apple's complaint — an "authentication bug" left his access to Apple's cloud storage intact. OpenAI then adds text-message evidence: Apple employees, including Liu's own former manager, kept logging into Liu's personal iCloud account after his departure, downloading files from it and asking him about its contents. One message quoted in the filing, sent more than a month after Liu had left, reads: "Just in case you don't have enough work, I need some help." OpenAI's framing is that Apple's abbreviated offboarding left that Apple employee no other route to the information.

Pillar three: no misappropriation. The "show and tell" allegations that made Apple's complaint go viral get reinterpreted here. Apple alleged that Tan directed candidates still working at Apple to bring "Actual parts" to interviews, and that one candidate replied he "didn't even know we could take those from the office." OpenAI's response is a list of things Apple did not plead: it did not identify the part, did not identify what protected information was embodied in it, did not explain why it wasn't readily ascertainable through proper means, did not allege any candidate actually displayed it, and did not allege Tan ever received, examined, retained or used it. The motion further says the messages surrounding the ones Apple quoted show the recipient understood Tan to be referring to parts from a publicly shipped product. Then OpenAI drops a citation that does a lot of work: a June 15, 2026 ruling holding that asking a recruiting candidate about the "technical aspects" of a project for a prior employer does not state a claim for misappropriation. The case is x.AI Corp. v. OpenAI, Inc. — a suit OpenAI won two months ago in this same district.

Pillar four: injury and jurisdiction. OpenAI argues Apple never alleges it lost a sale, a supplier, a customer, or an employee it wanted to keep; that any product was delayed, degraded or made more expensive; or that any identified secret lost measurable value. It then uses Apple's own words against the injury theory: Apple pleads that it "immediately took steps to ensure Mr. Liu's access was terminated" and that it "quickly fixed" the authentication bug. The motion's conclusion on this point is one sentence long — "An injury that Apple alleges it has already cured is not a plausible basis for the damages or the injunctive relief it seeks." Finally, with the federal claims gone, OpenAI says the state-law contract claims against Liu and Tan lack independent jurisdiction because there is no diversity of citizenship, so the court should decline supplemental jurisdiction. The relief requested is dismissal of the entire complaint with prejudice — no second bite.

There's also a pre-suit sideshow embedded in the motion. Apple's complaint says it wrote to OpenAI in February 2026 and got no response. OpenAI's version: Apple's outside counsel emailed the wrong person after confusing two Asian last names — the filing describes correspondence "addressed to a Mr. Wang" being sent to OpenAI's General Counsel, Che Chang — OpenAI immediately flagged the error, Apple apologized and its lawyers said they were "resolving any issues," and then five months of silence before the suit. That narrative first appeared publicly in OpenAI's August 3 post, "Apple is getting this wrong," which published emails and iMessages; the motion moves it into the court record.

Item Detail
Case / number Apple Inc. v. Liu / 5:26-cv-07078-EJD
Court N.D. Cal., San Jose Division
Judge Edward J. Davila (initially assigned to Magistrate Judge Virginia K. DeMarchi)
Complaint filed July 10, 2026
Defendants Chang Liu, Tang Yew Tan, OpenAI Foundation, OpenAI Group PBC, io Products LLC
Claims Claims 1–4: DTSA misappropriation / Claims 5–6: breach of contract (Liu, Tan)
Apple's injunction motion Filed August 3, 2026 (Dkt. 38, 29-page redacted version)
OpenAI's motion to dismiss Filed August 5, 2026 (Dkt. 59, 34 pages; 25 pages of argument)
Hearing October 1, 2026, 9:00 a.m., Courtroom 4, 5th Floor
Deadline What is due
August 17, 2026 Defendants' opposition to the preliminary injunction
August 19, 2026 Apple's opposition to the motion to dismiss
August 24, 2026 Apple's reply on the injunction
August 26, 2026 Defendants' reply on the motion to dismiss
October 1, 2026 Combined hearing before Judge Davila

What each side is actually playing for

Apple is playing for time and for deterrence. The time argument is written into the injunction motion in plain language: OpenAI "is racing to bring its first hardware products to market," has "long claimed that it wants to launch a hardware product[,] with some rumors being that it wants to launch its own phone," and every day without an injunction lets OpenAI embed knowledge of Apple's information into its development work in ways that "cannot be unwound after the fact." The relief Apple asks for is aggressive: bar access, use or disclosure of its trade secrets; bar soliciting such information from Apple employees and trusted partners; bar destruction of evidence; and order defendants to produce full forensic images of devices, cloud repositories, mailboxes and messaging platforms for inspection by Apple's counsel or a forensic vendor. That last item is a request to open a rival company's drives.

The deterrence play is the 400 number. Apple is not really trying to punish two engineers. It is signaling to the hardware staff who remain what happens if they walk. On August 3 Apple named Yu-Ting "Alyssa" Peng in addition to Liu and Tan, and referenced eleven further former employees identified in its outside counsel's July 10 letter to OpenAI's general counsel — including, Apple says, someone who in the hours before an OpenAI interview began screenshotting and downloading material about the confidential project Tan asked about. Putting an expanding investigation into public filings is itself an HR instrument.

OpenAI is playing for schedule freedom and for the legitimacy of its hiring funnel. Chief Global Affairs Officer Chris Lehane confirmed at Davos in January 2026 that the company intends to unveil its first consumer device in the second half of 2026, and TechCrunch reported the same month that OpenAI aims to ship in 2026, possibly with an earbud-style product. Drop a broad injunction and a forensic inspection order on top of that calendar and you get real pressure on engineering and supplier negotiations. That's why the motion contains the line "OpenAI is building something entirely new and different from anything at Apple." Read it as a legal position rather than product marketing: if the device is not derivative of Apple's, there is no reason to need Apple's secrets.

The individual defendants have overlapping but not identical interests. Liu hired his own firm, and his defense rides on the narrative that Apple's employees asked for help first and the access was requested and authorized by Apple. Tan's defense is that he is a 24-year industry veteran who "repeatedly instructed recruits and his team not to bring or disclose former employers' confidential information" — a point OpenAI also made in its public post, saying Tan "has always been clear with the team that we do not want, and must not use, any confidential information from other companies." For the companies this is a product timeline. For the two men it is a career.

The quiet beneficiary is Google. While Apple and OpenAI publish each other's security lapses and recruiting scripts into the federal record, Google already holds the model contract for Siri and the next wave of Apple Intelligence, announced in January 2026 at a reported $1 billion a year. OpenAI's jab about Apple's AI integration failures is aimed straight at that fact.

Precedent — one clean win, one settlement, one boomerang

The closest comparison is x.AI Corp. v. OpenAI. Elon Musk's xAI alleged that former engineer Xuechen Li carried trade secrets to OpenAI and that OpenAI induced it. OpenAI won outright. Judge Rita Lin in the Northern District of California dismissed the first complaint in February 2026, and on June 15, 2026 dismissed the amended complaint with prejudice, saying further amendment would be futile. Lin found xAI had not shown OpenAI induced Li to disclose secrets or that OpenAI employees knew confidential information had been disclosed, and noted that asking job candidates about prior work is a routine part of hiring and does not by itself imply wrongdoing. That is why OpenAI cites the ruling twice in the Apple motion: same district, same defendant, adjacent fact pattern, already tested.

The counter-example is Apple v. Rivos. Apple sued the RISC-V chip startup and several former employees in May 2022; Rivos had hired more than 40 Apple engineers. It never reached a verdict. In February 2024 the parties told the court they had signed an agreement resolving the case, with terms including forensic examination of Rivos's systems and recovery of Apple confidential information. Apple got no damages award, but it got to walk through the other company's storage and take its material back. Look at what Apple is demanding from OpenAI now — forensic images, inspection, return of materials — and the resemblance to the Rivos settlement structure is hard to miss. Apple's practical objective may be a cleanup, not a check.

The third case is the boomerang. In Masimo Corp. v. Apple Inc., the medical device maker accused Apple of hiring away its people to take blood-oxygen sensing secrets, and in October 2020 a California federal court dismissed the complaint for failing to identify the secrets with enough particularity. Apple's winning argument then was that categories followed by examples do not narrow an "impermissibly vague and unbounded description." That argument is now being fired back at Apple on pages 7 and 8 of OpenAI's brief.

Put the three together and a pattern shows up. At the 12(b)(6) stage, trade secret plaintiffs most often lose not because there's no evidence of taking, but because they can't write down precisely what was taken. And plaintiffs' real-world wins tend to come from settlements and forensic access rather than judgments. So the thing to watch on October 1 isn't a binary win or loss — it's whether Davila grants partial dismissal with leave to amend, dismisses without prejudice, or goes all the way to the with-prejudice dismissal OpenAI is asking for.

Apple's counter-moves

Apple's job by August 19 is to survive the identification attack. Practically, that means narrowing paragraph 40's five categories or restating the secrets at the level of specific files and projects. Which creates Apple's dilemma: identifying a secret with particularity means describing its outline in a public document, and Apple hates having unreleased product detail sit in a court file. You can see the tension in the docket already — the injunction motion exists in both a sealed version and a redacted public one, and most of the supporting exhibits are under seal. Specificity and secrecy eat each other.

The second counter is factual reframing. OpenAI's defense depends on "Apple asked first, and the access was authorized." Apple will push back with the unreturned company laptop, the use of a former colleague's Apple-issued machine, access to shared network folders through the authentication bug, and the messages the complaint quotes — "LOL," "so funny," "I still have another computer." That's the strength of Apple's case: an authorized favor and cheerfully downloading dozens of files over several weeks are not the same event. OpenAI's counter-strength is the gap it identified — Apple never alleges Liu disclosed a file to OpenAI or used one in OpenAI's hardware work.

The third counter is amendment. Even a partial dismissal usually comes with leave to amend, and Apple's August 3 filing naming Peng plus eleven additional former employees reads as a preview of a broader second complaint. For Apple this is less a single brief and more a rolling investigation that keeps getting appended to the record.

OpenAI's counter-play has two tracks. In court, the August 17 injunction opposition is where it contests the facts directly, and the motion promises exactly that — expect more sealed messages and emails. Out of court, it is running a publicity campaign, which is genuinely unusual for a corporate defendant. The standard script is "we don't comment on pending litigation." OpenAI instead published receipts on August 3 and highlighted Apple's pre-suit procedural stumbles. That carries risk: documents released voluntarily can be read back to you later, and judges do not always enjoy being briefed through the press.

Finally, the venue matters. California treats non-compete agreements as essentially void, so Apple cannot tell engineers not to leave; it has to route through trade secrets law and its intellectual property agreements. When OpenAI's motion says California law and policy "not only permit but encourage such employee mobility, which has been credited with powering the tech revolution that has made companies based in this state the envy of the world," that isn't flourish — it's a frame that has worked repeatedly in this district. In another state, the calculus would look different.

So what actually changes

For individual engineers, this case is a very concrete checklist. First, stop mixing work into personal cloud accounts. In this dispute the iCloud intermingling was used to weaken Apple's position, but for an individual it cuts the other way: if company files sit in your personal account after you leave, mere possession becomes the starting point of a dispute. Second, the ex-colleague "can you find this for me?" request looks like a favor and behaves like a liability. OpenAI could use those requests as defense evidence only because the texts existed; without a record, identical conduct reads as unauthorized access. Third, if an interview asks you to bring parts, CAD artifacts or prototypes from your current employer, you are already in the hazard zone. The candidate who said he "didn't even know we could take those from the office" is now quoted in a federal filing.

For security and HR leaders, this is an offboarding audit template. Apple runs one of the most respected corporate security organizations in tech, and still ended up with a departed employee's cloud access alive because an immediate-walkout practice collided with an authentication bug — a fact recorded in Apple's own complaint and repurposed by the other side as proof that reasonable measures were lacking. The lesson is that half of a trade secrets case is won before the incident, in documentation. Access-revocation logs, device-return confirmations, signed confidentiality reminders, and an enforced policy against using personal accounts for work. Without those four, you can be entirely in the right and still have nothing to hold up in court.

For investors, keep this in proportion. The motion to dismiss by itself does not move OpenAI's hardware schedule or Apple's earnings. The financially meaningful variable is how far the injunction goes on October 1. A broad prohibition plus a forensic inspection order puts real pressure on OpenAI's second-half 2026 device reveal; a dismissal leaves Apple with almost no legal lever against hardware talent outflow. And judging by Rivos, a negotiated resolution somewhere in between is entirely plausible. Note also that the two companies remain tied together by the ChatGPT–Apple Intelligence agreement. Litigating against your product partner is uncomfortable for both sides, and that discomfort is itself a settlement pressure.

For everyday users, nothing changes directly. Indirectly, how much OpenAI's first device and Apple's next hardware end up resembling each other is marginally shaped by this outcome. The bigger signal is where AI industry conflict has migrated. For three years the AI courtroom fight was about training data and copyright. What frontier labs and Big Tech are now suing each other over is people and hardware know-how. As model capabilities converge, this case is an unintentional readout on which resources are still scarce.

🥄 Three Things You're Probably Wondering

— So what does this mean for me? Directly, nothing. Indirectly, if you keep work material in a personal cloud account, now is a good moment to clean it up. In this case the blending of personal iCloud and work data turned into a liability for both sides.

— Why is this happening now? OpenAI has publicly committed to unveiling its first consumer device in the second half of 2026, and Apple moved for a preliminary injunction on August 3 to get restrictions in place before that. OpenAI's motion to dismiss two days later puts both matters in front of Judge Davila on the same October 1 date — an attempt to end the case early rather than fight it through discovery.

— Is OpenAI likely to win this? It has favorable material. Two months ago the same district dismissed xAI's structurally similar claims with prejudice, and OpenAI cites that ruling directly. But Apple's complaint contains harder specifics — an unreturned laptop, dozens of downloaded files over several weeks — so the fact patterns aren't identical. Partial dismissal with leave to amend is the most common path from here, and calling a winner this early would be premature.

Sources

Numbers are as of announcement and may change.