Apple sues OpenAI, accuses ex-employees of stealing trade secrets

What did Apple actually accuse OpenAI of?

Apple filed a federal lawsuit in California on 10 July 2026 against OpenAI and two former Apple employees, alleging a coordinated scheme to steal trade secrets. The named individuals are Chang Liu, an eight year Apple senior systems electrical engineer, and Tang Yew Tan, Apple's former VP of product design for iPhone and Apple Watch, now OpenAI's Chief Hardware Officer.

Apple claims Liu failed to return a company issued laptop after leaving for OpenAI and used it to download confidential technical documents, including unannounced product specs and engineering presentations. Apple also alleges OpenAI coached departing staff on how to get past its internal security and offboarding checks. Apple wants a preliminary injunction to stop use of its trade secrets and force their return.

Why is this happening now?

Tensions built up since OpenAI moved into hardware in 2025 by acquiring former Apple designer Jony Ive's startup io for around £5 billion. Apple's filing states that more than 400 former Apple employees now work at OpenAI, which gives some sense of the scale of movement between the two firms.

That number matters. A single disgruntled leaver is one thing. Four hundred alumni inside a direct competitor's hardware division is a structural talent pipeline, and it is exactly the kind of pattern that makes trade secret claims hard to prove but easy to fear.

Why should a UK small business owner care about an Apple v OpenAI lawsuit?

Because the underlying problem, an ex-employee walking off with company property and confidential data, is not an Apple sized problem. It is a small business problem, and you have far weaker defences than Apple does. In the UK, 75% of employees admit to stealing from an employer at some point, and trade secret or IP theft such as client lists, pricing, or proprietary processes is some of the hardest insider theft for small firms to detect.

Apple has legal teams, device management software, and forensic IT to build a case. Most local businesses have none of that. If a former employee leaves with your customer list, your supplier pricing, or your booking system login, you likely will not even know until a competitor starts undercutting you.

What data are small businesses actually exposed on?

The three most common gaps we see: shared logins for booking platforms, customer contact lists exported to personal devices, and no written policy on returning equipment or revoking access when someone leaves. None of these need a lawyer to fix.

• Shared logins: if staff share one password for your booking system, Google Business Profile, or social accounts, you cannot see who did what or switch someone off individually.
• Exported customer data: spreadsheets, CSV exports, or WhatsApp broadcast lists that live outside your core system leave with whoever downloaded them.
• No offboarding checklist: revoking access, retrieving devices, and changing passwords should happen on someone's last day, not whenever you get round to it.

What should a small business actually do about this?

Give every staff member their own login, put a one page confidentiality and device return clause in your contracts, and revoke access the same day someone leaves. This takes an afternoon to set up and costs nothing beyond your time.

1. Use individual logins for your Google Business Profile, booking system, and any customer database, so access can be switched off per person.
2. Add a short written clause to employment contracts covering confidentiality, customer data, and return of equipment on leaving.
3. Keep a simple offboarding checklist: change shared passwords, remove app access, collect devices, all on the last working day.
4. Avoid storing customer data in personal spreadsheets or exports that live outside your main system.

Is this connected to the wider trend of businesses renting their online presence?

Yes, and it is the same underlying issue. When you rent your infrastructure, whether that is a booking platform, a staff member's personal device, or a third party directory listing, you do not control what happens to your data when the relationship ends. Apple's case is about an employee relationship ending badly. Most small businesses have the same exposure with platform relationships ending badly.

We have seen this with a nail salon that was paying Fresha roughly £1,800 a month in commission before moving to its own booking system at £35 a month, a saving of around £21,000 a year, and full ownership of its customer data rather than data sitting inside someone else's platform. Owning your booking system, your website, and your customer records means no one, whether a departing employee or a platform provider, can take your customer relationships with them.

Braynex Services' view

This case is a reminder that data ownership is not just a big tech problem. Every local business holds customer information, pricing, and processes that are worth protecting, and most have no system in place to do it. You do not need Apple's legal budget. You need individual logins, a written policy, and a same day offboarding habit.

If you are not sure who has access to your booking system, your Google Business Profile, or your customer list right now, that is worth finding out before it becomes a problem rather than after. Book a free audit at braynexservices.com and we will check where your data actually lives and who can reach it.