What happened
Apple filed suit against OpenAI in federal court in Northern California on Friday, accusing the AI company of stealing trade secrets to build its upcoming consumer hardware.
The complaint alleges the taking happened "at every level" — that OpenAI's hardware chief, a former Apple vice president, directed job candidates still employed at Apple to bring confidential material, including actual hardware parts, to interviews; that departing employees were coached on evading Apple's exit security; and that one employee left with an Apple laptop.
Two years ago these companies announced a landmark partnership. Now the biggest company in consumer hardware says the biggest company in AI built its device business on stolen work.
The backdrop: OpenAI bought former Apple design chief Jony Ive's startup for $6.4 billion last year and has been hiring Apple's silicon, on-device AI, and hardware teams ever since.
The detail almost everyone will miss
The headlines will frame this as a clash of titans over gadgets. Look instead at the mechanism Apple describes: the alleged extraction channel wasn't hacking or espionage — it was the hiring process itself.
Interviews as intelligence-gathering. Offer letters as acquisition of what the candidate knows. If the allegations hold, the most valuable data transfer in tech last year happened one resignation at a time.
Talent movement is data movement. Every person who leaves a company carries some of how it works — and the law only draws the line at what they carry deliberately.
Apple — a company famous for internal secrecy, badge-gated buildings, and compartmentalized teams — is alleging in court that none of it was enough.
Why this matters if you run a business
You are not Apple, and no one is suing you over a headset. But the mechanic in this lawsuit operates at every scale, and AI has raised the stakes on it.
A year ago, a departing employee took a client list and their own experience. Today, more of your operation lives in systems people can carry: the prompt library that runs your proposals, the agent configurations that run your workflows, the shared AI accounts with a year of your business context inside them.
If a company that locks down prototypes behind badge readers couldn't control what walked out the door, your offboarding checklist deserves more respect than it's getting.
One caution: these are allegations in a complaint, not findings. OpenAI hasn't had its say in court. Read it as a description of risk, not a verdict — the risk is real either way.
What to do about it
Three moves, none of which require a legal department:
- Make offboarding a same-day security event. The day someone gives notice: access revoked or scoped down, devices accounted for, shared passwords and API keys rotated. Not at the end of their two weeks — the day it starts.
- Inventory where your operating knowledge actually lives. List the prompts, agent setups, SOPs, and AI accounts your business runs on — and make sure each one belongs to a company account you control, not someone's personal login.
- Put confidentiality in writing before it matters. Anyone who touches your systems — employee or contractor — should have signed confidentiality and IP-assignment terms. The paper won't stop a bad actor, but it decides who wins afterward.
Apple's problem is that knowledge walks. Yours is the same problem at a smaller scale — and unlike Apple, you can fix most of it in an afternoon.