Apple and OpenAI Trade Secret Fight: 5 Allegations and 5 Takeaways for General Counsel

Five allegations, OpenAI’s response, a disputed email trail, and five governance takeaways for general counsel. Updated through August 2026.

Apple, OpenAI, and the Trade Secret Fight: Who’s David, Who’s Goliath?

When we look at the current landscape of AI lawsuits, the narrative is usually a classic “David versus Goliath” setup—a massive tech conglomerate dominating an individual author, a news outlet like The New York Times, or a legacy media company. But this lawsuit is completely different. There is no David here. This is a clash of two Goliaths, two of the most lucrative and highly valued companies on the planet going head-to-head.

Apple is famous for secrecy, having invested hundreds of billions of dollars and decades of effort into its product development. OpenAI is famous for speed, transforming rapidly into a commercial enterprise with a valuation that soared to $852 billion by April 2026. Apple’s new lawsuit puts those two massive corporate identities into direct conflict.

At first glance, the complaint reads like a cybersecurity thriller. An unreturned computer. A previously unknown authentication bug. An alleged post-employment download. Hardware samples allegedly brought to j ob interviews. But the most important point for general counsel is not any single dramatic allegation. It is how many ordinary corporate functions Apple says were implicated: Legal, HR, IT, cybersecurity, recruiting, procurement, supplier management, finance, and leadership.

BREAKING NEWS UPDATE, AUGUST 6, 2026:

On August 5, OpenAI, io Products, Tang Yew Tan, and Chang Liu jointly moved to dismiss Apple’s complaint under Federal Rule of Civil Procedure 12(b)(6).

Calling the case “rotten to its core,” the defendants argue that Apple has not identified protectable trade secrets with sufficient particularity, plausibly alleged misappropriation by each defendant, or shown injury or ongoing harm. They also offer a sharply different factual account of Liu’s post-employment access, OpenAI’s recruiting practices, Apple’s information-management controls, and the parties’ pre-suit communications.

Two days earlier, Apple moved for a preliminary injunction. Apple is asking the court to prohibit the defendants from accessing, acquiring, using, soliciting, or disclosing alleged Apple trade secrets; prevent the destruction or concealment of relevant evidence; require forensic imaging and inspection of potentially relevant devices and repositories; and return Apple information. Apple also requested expedited discovery.

OpenAI says its fuller response to Apple’s preliminary-injunction request is forthcoming. The next phase will include briefing on both motions, followed by an October 1 hearing before Judge Edward J. Davila.

At this stage, the court is considering whether Apple’s complaint plausibly states a claim and whether Apple has established grounds for interim relief. It has not resolved either side’s factual narrative.

The Case in 45 Seconds

• Case: Apple Inc. v. Liu, No. 5:26-cv-07078-VKD, filed July 10, 2026, in the U.S. District Court for the Northern District of California, San Jose Division. The case is assigned to Magistrate Judge Virginia K. DeMarchi.

• Defendants: Former Apple employees Chang Liu and Tang Yew Tan, OpenAI Foundation, OpenAI Group PBC, and io Products, LLC. Liu spent eight years at Apple as a senior system electrical engineer before joining OpenAI in January 2026. Tan spent 24 years at Apple, most recently as VP of Product Design for iPhone and Apple Watch, and now serves as OpenAI’s Chief Hardware Officer.

• Claims: Four trade secret misappropriation counts under the federal Defend Trade Secrets Act, one each against Liu, Tan, OpenAI, and io, plus two breach-of-contract counts against Liu and Tan.

• Statutes: Apple invokes 18 U.S.C. § 1836 and the definitions in 18 U.S.C. § 1839. The complaint’s DTSA count headings also cite 18 U.S.C. §§ 1832(a), 1836-37, and 1839.

• Relief: Injunctions, evidence preservation and return of property, actual-loss and unjust-enrichment damages, a reasonable royalty in the alternative, exemplary damages, attorneys’ fees, and a jury trial. Apple does not plead a dollar amount.

Two Sides of the Story

The comparison below places Apple’s allegations next to OpenAI’s public response and the reported email account. It does not resolve any contested fact.

The Five Most Controversial Allegations

1. The Unreturned Computer, Two Access Routes, and the Post-Employment Downloads

Apple alleges that Chang Liu did not complete its exit process or return at least one company computer before joining OpenAI. According to the complaint, he left a message saying, “I still have another computer.”

Apple says Liu then used two separate routes into its systems: a former colleague’s authenticated Apple-issued computer and a rare authentication bug that Apple says it had not previously known about. The complaint alleges that Liu reacted with “LOL” and called the access “so funny.” He then allegedly downloaded dozens of confidential hardware files containing information about unreleased products, technical specifications, engineering presentations, manufacturing, and testing.

Why counsel should care: Offboarding is not an HR checklist or an asset-return task. For sensitive roles, it is a coordinated access-control event involving devices, accounts, sessions, credentials, logs, legal obligations, evidence preservation, and escalation.

One precision point worth keeping straight: the complaint does not establish that multifactor authentication failed. It alleges a separate authentication vulnerability and the use of another employee’s authenticated device.

2. A Continuing Human Channel Back Into Apple

Apple alleges that Liu continued receiving information from a then-current Apple employee after he left. The complaint says he used her authenticated work computer, discussed projects and vendor relationships with her, directed her toward specific folders, and coached her on how to copy information while trying to “avoid trouble with the security team.”

That allegation matters because insider risk does not travel only through malware or compromised credentials. It moves through friendship, loyalty, mentoring, former-team relationships, and ordinary conversations between people who still trust each other.

Why counsel should care: A security program that watches devices but ignores relationship-based risk is incomplete. Legal, HR, security, and management need a clear way to identify high-risk departures, continuing access pathways, unusual collaboration patterns, and reports from employees who are uncomfortable with a request.

3. The OpenAI Interview “Show and Tell”

Apple alleges that Tang Yew Tan and OpenAI used interviews to obtain confidential Apple information. The complaint says candidates were directed to bring “actual parts” for “show and tell” and to present design artifacts, prototypes, technical deep dives, subsystem choices, engineering methods, and vendor information.

Hiring from a competitor is not unlawful. The complaint’s claim that more than 400 former Apple employees now work at OpenAI may be commercially significant, but the number itself does not prove wrongdoing. The legal and governance line is whether a hiring process solicits, receives, preserves, or uses information that belongs to the prior employer.

Why counsel should care: Competitive hiring needs a clean-room mindset. Recruiters and interviewers should be trained not to request prior-employer documents, samples, source files, codenames, nonpublic road maps, supplier terms, or technical details beyond the candidate’s general skill and experience.

4. An Alleged Playbook for Anticipating Apple’s Exit Controls

Apple alleges that Tan retained or obtained an internal managers’ document marked “Need to Know” describing departure-security procedures, and that OpenAI personnel shared it with incoming hires before they gave notice. Apple further alleges that recruits were advised on how to avoid triggering an immediate removal from Apple systems and how to handle exit interviews.

There can be legitimate reasons for a new employer to help an employee understand contractual obligations. Apple alleges something different: the use of inside knowledge to anticipate or defeat safeguards designed to protect confidential information.

Why counsel should care: A competitor-hire protocol should protect both companies. It should tell incoming employees what they may bring, meaning their experience, skills, and general know-how. It should also tell them what they may not bring: documents, devices, prototypes, confidential data, restricted supplier information, or proprietary methods.

5. Supplier Relationships and a Confidential Manufacturing Process

The supplier allegations may be the most commercially consequential. Apple says Tan emailed himself supplier information before leaving. It also alleges that OpenAI or io approached an Apple partner about a confidential, multi-step metal-finishing process and caused the partner to perform the process while believing Apple had authorized it.

Apple separately alleges that another longtime supplier was approached with targeted questions using internal terminology related to power and battery components.

The complaint also uses Apple’s February outreach as part of its narrative, stating that OpenAI did not respond. That assertion is now disputed, and the reported communications are addressed separately below.

Why counsel should care: Trade secret risk extends beyond source code and patentable inventions. Supplier identities, manufacturing processes, testing methods, failed experiments, component strategies, pricing, contractual arrangements, and years of integrated operational know-how can all qualify. But only if the statutory elements are met and the company can show reasonable measures to preserve secrecy.

The Email Dispute What OpenAI says is not in the Complaint

The email issue is not itself a trade secret claim. It matters because Apple used the alleged lack of a response to explain why it continued investigating and ultimately filed suit. The subsequent reporting shows that even this seemingly simple piece of the chronology is disputed.

“Apple asked OpenAI to discuss what precautions OpenAI was taking … to investigate it, and to remediate any issues. OpenAI never responded.”  Apple’s complaint, paragraph 14

That is Apple’s pleaded account. OpenAI’s reported account is different.

1. Initial outreach. NBC News reported, and 9to5Mac summarized in detail, that Apple outside counsel Gabriel S. Gross of Weil, Gotshal & Manges emailed Che Chang, OpenAI’s general counsel, with the subject “Former Apple employees at OpenAI retaining non-public, confidential, and proprietary information” and attachments supporting Apple’s concerns.

2. The 13-minute follow-up. The report says Gross emailed Chang again 13 minutes later, thanking him for a telephone call and for offering cooperation.

3. The alleged recipient confusion. According to the report, the call had actually been with another OpenAI employee, a former Apple employee identified publicly only by the surname Wang. Gross had reportedly emailed both Chang and Wang, spoken with Wang, and then replied to Chang by mistake.

4. The reaction and apology. Chang reportedly told Apple in-house lawyers that he had never spoken with Gross and asked that Gross be removed from the matter. Gross later apologized. OpenAI says it has no record of subsequent outreach from Apple’s lawyers before the complaint was filed.

What remains unknown: the complete email chain, address headers, timestamps, attachments, call records, internal forwarding history, and witness accounts are not yet in a developed public evidentiary record. AppleInsider likewise noted that the sequence cannot be reconstructed confidently without the full emails and headers. The responsible legal conclusion is not that one public account has already won. It is that the complaint, corporate statements, and press reports are competing sources that still need authentication, context, and discovery.

What the Law Actually Requires

Apple’s federal claims arise under the Defend Trade Secrets Act. Section 1836(b) allows a trade secret owner to bring a civil action when a trade secret related to interstate or foreign commerce is misappropriated.

Section 1839 does the definitional work. Information is not a trade secret merely because a company labels it confidential. The owner must show:

1. Reasonable measures to keep the information secret; and

2. Independent economic value from the information not being generally known or readily ascertainable through proper means.

Misappropriation can include improper acquisition, or unauthorized disclosure or use by someone who knew or had reason to know that the information came through improper means or a duty of secrecy.

The statute identifies theft, misrepresentation, breach or inducement of a duty, and electronic or other espionage as improper means. It excludes lawful methods such as reverse engineering and independent derivation.

The statute authorizes injunctions, actual-loss and unjust-enrichment damages, and a reasonable royalty in the alternative. For willful and malicious misappropriation, it authorizes exemplary damages of up to twice the compensatory award, along with potential attorneys’ fees.

Five Key Takeaways for General Counsel

Before turning to the recommendations, two distinctions matter. First, these takeaways are not findings about Apple’s or OpenAI’s actual controls, agreements, culture, or conduct. They are governance issues raised by disputed allegations and public accounts. Second, the email dispute adds a threshold lesson: significant communications should be carefully documented, time-stamped, recipient-checked, independently verified, and preserved before they are used in a pleading or public narrative.

1. Treat Offboarding, IPAs, and NDAs as One Control System

• Classify departures by access, role, sensitivity, destination, and active projects.

• Use role-appropriate intellectual property assignment agreements and nondisclosure agreements, and reaffirm key obligations when access changes or an exit begins.

• Terminate access and active sessions on a defined timeline, and verify device return rather than merely requesting it.

• Preserve signed agreements, amendments, acknowledgments, training records, access logs, and exit communications in a form Legal can retrieve quickly.

The practical point: Agreements define duties, but they do not retrieve a laptop, close a session, preserve a log, or create an evidentiary record. Operations must execute the promise.

2. Build a Clean-Hiring Protocol for Competitor Talent

• Use written interview instructions prohibiting prior-employer materials and confidential disclosures.

• Train hiring managers not to ask for codenames, road maps, prototypes, supplier terms, process details, or physical samples.

• Require incoming employees to certify that they returned prior-employer property and will not use restricted information.

• Quarantine unsolicited materials and route them to Legal rather than allowing a business team to inspect or retain them.

• Document independent development where the new hire will work in a sensitive competitive area.

The practical point: Employee mobility and trade secret protection are compatible, but only when the hiring process is designed to respect both.

3. Identify and Value the Actual Trade Secrets Before a Crisis

• Inventory more than patents and source code.

• Include processes, testing methods, negative know-how, supplier networks, component decisions, pricing, and confidential coordination.

• Tie each category to owners, access rules, contracts, marking practices, training, technical controls, and supplier obligations.

• Document why the information has economic value from secrecy and how competitors could benefit from it.

• Involve finance and accounting in valuation and damages readiness rather than waiting until litigation.

The practical point: A broad confidentiality label is not a litigation strategy. Counsel needs specificity, evidence of value, and proof of reasonable protection.

4. Govern the Seams – and Treat Trust as a Control Layer

• Create one insider-risk playbook across Legal, HR, IT, cybersecurity, compliance, recruiting, procurement, finance, and business leadership.

• Assign who may terminate access, contact a supplier, initiate a hold, interview an employee, notify a former employer, or brief the board.

• Give employees, candidates, interviewers, managers, and suppliers a safe way to question or report a request before they act on it.

• Train leaders to recognize that friendship, mentoring, loyalty, and former-team relationships can become risk channels even when no technical control has been breached.

• Test the playbook with realistic scenarios rather than relying on a checklist no one has practiced.

The practical point: Everyone may own a control while no one owns the handoff. Trust is often the earliest warning system an organization has.

5. Document, Time-Stamp, Double-Check, and Preserve the Record

• Preserve original emails with full headers, recipient lists, attachments, and metadata rather than relying on screenshots or reconstructed summaries.

• Document calls and meetings contemporaneously, including participants, time, substance, and follow-up responsibilities.

• Confirm full names, roles, and recipients before sending or characterizing legal communications, especially where given names and surnames may be confused.

• Keep auditable records of access changes, device return, training, policy acknowledgments, supplier authorizations, exceptions, and escalation decisions.

• Distinguish clearly among allegations, corporate statements, press reports, authenticated records, and judicial findings.

The practical point: A policy without evidence is difficult to defend, and a chronology without primary records is easy to contest.

What to Watch Next

This case is at the beginning. The defendants will have the opportunity to contest Apple’s factual narrative, the scope and ownership of the alleged secrets, the distinction between protectable information and general employee knowledge, corporate attribution, causation, and remedies.

The next important developments will include:

• The defendants’ formal responses and any counter-narrative supported by filed evidence;

• Any request for preliminary injunctive relief;

• The level of specificity with which Apple must identify its trade secrets;

• Discovery into interview practices, supplier communications, and independent development;

• The complete pre-suit email record, including headers, attachments, call records, and witness testimony; and

• Evidence concerning what OpenAI or io requested, received, knew, used, or independently developed.

It is far too early to predict whether the dispute will end through settlement, a pleading-stage ruling, summary judgment, or trial. The competing accounts already visible in the public record suggest that discovery into documents, metadata, and witness testimony may matter.

For general counsel, the immediate lesson does not require a verdict. Apple’s complaint is one side of the story. OpenAI’s public response and the reported email chronology are another. The question is whether your organization would catch the handoff – and whether it could reconstruct what happened with reliable records if the sequence were later disputed.

IMAGE CREDIT:

Editorial illustrations created by Lili Kazemi with MidJourney. Not affiliated with or endorsed by Apple or OpenAI.

Sources and Further Reading

• Complaint: Apple Inc. v. Liu, No. 5:26-cv-07078-VKD, Document 1

• CourtListener docket: Apple Inc. v. Liu

• TechCrunch: “OpenAI pushes back on Apple trade secret lawsuit”

• NBC News: report on the pre-suit email dispute

• 9to5Mac: “How an email mistake derailed talks between Apple and OpenAI ahead of the lawsuit”

• AppleInsider: “OpenAI blames email mixup for why it didn’t respond to Apple trade theft claims”

• 18 U.S.C. § 1836

• 18 U.S.C. § 1839