Passer au contenu principal
OpenAI

3 août 2026

Entreprise

Apple fait fausse route

Chargement…

Apple est l’une des plus grandes entreprises de tous les temps et s’est forgé une réputation en accordant une attention obsessionnelle aux moindres détails. Cette poursuite négligente, agressive et étrangement personnelle n’est malheureusement pas à la hauteur de cette réputation.

Apple avait affirmé avoir communiqué avec OpenAI en février et que nous n’avions pas répondu. Apple reconnaît maintenant que ses avocats externes ont envoyé un courriel à la mauvaise personne après avoir confondu deux noms de famille asiatiques — et ce, seulement après que nous avons porté cette erreur à son attention. Apple avait également affirmé s’être entretenue avec notre chef du contentieux, ce qui, elle le reconnaît maintenant, n’a jamais eu lieu. Mais Apple cache encore une fois le fait qu’elle n’a jamais soulevé à ce moment-là les allégations précises formulées dans cette poursuite et qu’elle nous a en fait dit qu’elle « réglait toute question en suspens ». Nous n’avons ensuite plus eu de nouvelles pendant cinq mois, jusqu’à ce qu’Apple nous poursuive. Dans son plus récent dépôt, Apple s’efforce de présenter cette suite d’événements à son avantage, mais vous pouvez lire les courriels vous-même ici.

Apple accuse Chang Liu d’avoir accédé à des renseignements confidentiels d’Apple après avoir quitté l’entreprise, mais reconnaît seulement maintenant que des employés d’Apple l’ont contacté et lui ont demandé de les aider à trouver ces renseignements (vous pouvez lire les messages ici). Apple tente maintenant de rejeter la faute sur un « accès résiduel », mais omet aussi de préciser qu’il s’agit d’un problème courant chez Apple, causé par sa mauvaise gestion des accès aux systèmes lors du départ de membres du personnel. Concrètement, cela signifie que d’anciens employés qui essaient de faire ce qu’il faut au moment de leur départ ont toujours accès à des fichiers d’Apple, même s’ils ne le souhaitent pas ou n’en sont même pas conscients.

Apple accuse également Tang Tan d’avoir tenté d’obtenir et d’utiliser ses secrets commerciaux. Toutefois, Tang a toujours clairement indiqué à l’équipe que nous ne voulons obtenir aucun renseignement confidentiel d’autres entreprises et que nous ne devons en utiliser aucun. Tang a travaillé chez Apple pendant plus de 24 ans et était largement reconnu comme l’un des dirigeants les plus novateurs de l’entreprise.

Nous aurions aimé qu’Apple soulève ces questions auprès de nous avant d’intenter sa poursuite et nous aurions volontiers clarifié la situation avec elle. Nous avons pris au sérieux les allégations de la poursuite et proposé de collaborer avec Apple pour régler la situation. Apple tente plutôt de modifier son récit, notamment en formulant de vagues accusations à l’égard d’autres anciens employés, et continuera probablement d’employer cette tactique.

La demande d’injonction provisoire d’Apple repose à la fois sur de faux renseignements et est totalement inutile, puisque nous ne possédons aucun de ses secrets commerciaux et n’en voulons aucun. Nous préférons largement créer des produits et des technologies novateurs qui repoussent les limites.

Mise à jour du 6 août 2026 : Vous pouvez lire notre requête en rejet ici(s'ouvre dans une nouvelle fenêtre).

Mise à jour du 1er septembre 2026 : Vous pouvez lire notre opposition à la requête d’Apple en injonction provisoire ici(s'ouvre dans une nouvelle fenêtre).

Mise à jour du 14 septembre 2026 : Notre réponse au mémoire supplémentaire d’Apple se trouve ici(s'ouvre dans une nouvelle fenêtre).

Messages

Échanges iMessage entre Chang Liu (en bleu) et des employés d’Apple, dans lesquels les anciens collègues de Chang — dont la dernière journée chez Apple était le 22 janvier 2026 — lui demandent de les aider à trouver des fichiers et des renseignements utiles à leur travail chez Apple (toutes les heures sont en UTC). Remarque : les autres noms de personnes et les renseignements confidentiels d’Apple ont été caviardés.

1/22/2026 4:43:19 PM
Hey [Apple Employee #1], i had something we need to discuss when you get to office.
1/22/2026 4:43:41 PM
OK. I can talk on the phone now if you like.
1/22/2026 5:48:02 PM
I am here at the office.
1/22/2026 9:39:14 PM
Around your desk
1/22/2026 9:39:34 PM
Be there in 4.
1/22/2026 9:44:34 PM
Do you wanna meet me at the coffee machine?
1/22/2026 11:25:45 PM
I found a 64GB drive. Do you think that will work>
1/22/2026 11:26:59 PM
I think 200 ish. We start from 64. Better than nothing
1/23/2026 12:41:56 AM
Still copying
1/23/2026 5:13:02 PM
Good morning. I hope you slept well. Maybe you are still sleeping 😊 I’m back in the office and restarting the airdrop as it didn’t work. My plan is to complete the airdrop and then click the sad button in workday.
1/23/2026 5:38:25 PM
Liked “Good morning. I hope you slept well. Maybe you are still sleeping 😊 I’m back in the office and restarting the airdrop as it didn’t work. My plan is to complete the airdrop and then click the sad button in workday.”
1/23/2026 5:39:51 PM
Thanks a lot [Apple Employee #1]. Was a very hard night last night. I really appreciate all the help and work together with you.
1/23/2026 5:41:09 PM
If you have time you can also try to airdrop all other file in my apple iCloud folder.
1/23/2026 5:42:22 PM
Those are mainly shared files from other people. I found important detail notes from time to time.
1/23/2026 5:42:59 PM
All the file folders [Redacted - Apple Information] are the file I generated as my personal note.
1/23/2026 7:32:19 PM
Your file transfer is a challenge.
1/23/2026 7:33:24 PM
Carlos Org Travel Summary Chang joined the spreadsheet. I think I’m going to have to hit the workday button before I’m complete. I just got a weird message that is making me nervous (see below), so I am going to go hit the workday button now.
1/23/2026 7:34:53 PM
I don’t even think I have that file
1/23/2026 7:35:03 PM
Maybe the new Chang
1/23/2026 7:35:20 PM
Yeah. . . it could be. No need for you to worry. 😊
1/23/2026 7:35:37 PM
That new Chang has big shoes to fill.
1/23/2026 7:36:18 PM
😟 for the transfer. I think the archive and [Redacted - Apple Information] has most of file for you to dig. Otherwise team can always start from something brand new
1/27/2026 1:45:26 AM
Hey [Apple Employee #1] hope everything is fine for copy pasting. You can keep my icloud connected if you still need more time. But might want to sign off my iMessage. As there might be my new company stuff showing up in that laptop.
1/27/2026 3:06:56 AM
Oh shoot. Sorry. Let me finish up tomorrow and log everything out. I won’t look at anything else.
1/27/2026 3:08:26 AM
Hey [Apple Employee #1], that’s totally ok. I am fine with you keep my icloud signed in for files. Just imessages might get you in trouble.
1/27/2026 4:35:30 AM
Do you recall any discussions on shipping [Redacted - Apple Information]? I thought the plan was to go for [Redacted - Apple Information] because [Redacted - Apple Information] is still not proven, but I don’t remember specific details. Of course, I could ask several folks, but you are the best. Even if you don’t work here anymore 😟
1/27/2026 4:35:46 AM
. . . of course [Redacted - Apple Information] is the plan for [Redacted - Apple Information]
1/27/2026 4:39:27 AM
Hahahah no prob
1/27/2026 4:39:47 AM
The decision is for all the product shipped in [Redacted - Apple Information] from a schedule standpoint.
1/27/2026 4:39:59 AM
Hence [Redacted - Apple Information]. And [Redacted - Apple Information] for [Redacted - Apple Information]
1/27/2026 4:40:30 AM
[Redacted - Apple Information] make a [Redacted - Apple Information] because of that [Redacted - Apple Information] ramp time.
1/27/2026 4:41:06 AM
[Redacted - Apple Information] (es in March) will [Redacted - Apple Information] prototype build but too late for [Redacted - Apple Information].
1/27/2026 4:42:29 AM
Awesome: I was thinking [Redacted - Apple Information] for [Redacted - Apple Information] and [Redacted - Apple Information] for [Redacted - Apple Information]. But since [Redacted - Apple Information] was pushed back then it should get [Redacted - Apple Information] also.
1/27/2026 4:42:41 AM
I think we are aligned 😊
1/27/2026 4:46:06 AM
Actually yes also [Redacted - Apple Information]
1/27/2026 4:46:27 AM
Sorry I missed that. [Apple Employee #8 name] from Austin team is already working on that
1/27/2026 4:47:07 AM
Liked “Actually yes also [Redacted - Apple Information]”
1/27/2026 4:47:10 AM
Liked “Sorry I missed that. [Apple Employee #8 name] from Austin team is already working on that ”
1/30/2026 5:54:31 PM
Hey [Apple Employee #1]! Hope you got all the material you need. Otherwise you might need to reach out to IST for some backup if they ever has
1/30/2026 5:54:41 PM
I rrealize the folder is gone from my iCloud
1/31/2026 1:34:07 AM
I just signed out of your iCloud account. When it asked me if I wanted to keep a copy of your stuff, I said NO.
1/31/2026 2:28:08 AM
Loved “I just signed out of your iCloud account. When it asked me if I wanted to keep a copy of your stuff, I said NO.”
1/31/2026 2:28:18 AM
Thank you sir!
1/31/2026 2:29:23 AM
This startup style company is a funny and will be very hard in a couple months😁😁
2/14/2026 1:38:13 AM
How is it going over there? Did they let you off work early on a Friday so you can go bowling and drink beer?
2/14/2026 1:38:25 AM
. . . . or are they going to work you until 10pm?
2/14/2026 1:39:47 AM
Just in case you don’t have enough work, I need some help. I have a vague recollection of you talking about a [Redacted - Apple Information]. Can you give me a brief refresh of this and point me to an EE who may have some knowledge?
2/14/2026 1:41:25 AM
大笑「Just in case you don’t have enough work, I need some help. I have a vague recollection of you talking about a [Redacted - Apple Information]. Can you give me a brief refresh of this and point me to an EE who may have some knowledge?」
2/14/2026 1:41:51 AM
This place is crazy… hahahah we use Ai all over the place
2/14/2026 1:42:21 AM
I can always give you some fun side projects
2/14/2026 1:44:17 AM
I think what you referred to is [Redacted - Apple Information]. And the small [Redacted - Apple Information].
2/14/2026 1:44:41 AM
The problem is the people is also in my court now 😁😁
2/14/2026 1:45:00 AM
Plus if [Apple Employee #9] might still remember anything
2/14/2026 1:47:39 AM
Liked “I can always give you some fun side projects”
2/14/2026 1:52:30 AM
[Redacted - Apple schematic] Bummer. . . you should have filed a [Redacted - Apple Information] with the details and put that next to the [Redacted - Apple Information] on the schematic. Now you owe me a beer.
2/14/2026 1:53:43 AM
oops now it can only become a [Redacted - Apple Information] saying now we never know why 😁😁
2/14/2026 3:12:57 AM
Now when I think about it. The other smart people also just left that team. The one that might still in apple is [Apple Employee #10]
2/14/2026 3:13:12 AM
Or if you have a more specific question
3/5/2026 9:23:11 PM
chang: if I understood correctly, you said that the [REDACTED - Apple Information] powers a downstream [REDACTED - Apple Information] that then powers [REDACTED - Apple Information]. Is that right? Who should I contact about that [REDACTED - Apple Information]?
3/5/2026 9:35:19 PM
A few things you can look for. In our team box folder/[REDACTED - Apple Information]/. There should be a [REDACTED - Apple Information]. And there is a power block diagram to show the [REDACTED - Apple Information]. Or find [Apple Employee #5] to get the [REDACTED - Apple Information]. Contact is [Apple Employee #6]and [Apple Employee #7]. [REDACTED - Apple Information] need more sensitive for [REDACTED - Apple Information] than current design. Hence they need to rise [REDACTED - Apple Information]
3/5/2026 9:35:59 PM
Hi [Apple Employee #1 Name], [Apple Employee #3 Name], I can help get the conversation with [Apple Employee #6] and [Apple Employee #7] started
3/5/2026 9:37:28 PM
Hi, this is highly irregular, please remove me from this thread
3/5/2026 9:44:21 PM
Thanks Chang. [Apple Employee #2 Name] and [Apple Employee #3 Name] I put you on this thread for awareness. Let’s continue our discussion internally.
3/5/2026 9:50:48 PM
Liked “Thanks Chang. [Apple Employee #2 Name] and [Apple Employee #3 Name] I put you on this thread for awareness. Let’s continue our discussion internally.”

Correspondance par courriel

Les courriels suivants ont été échangés entre Gabriel Gross, avocat externe d’Apple, Che Chang, chef du contentieux d’OpenAI, et les conseillers juridiques internes d’Apple. Ils montrent que Gross a envoyé par erreur un courriel à Che et a affirmé à tort que les deux hommes s’étaient parlé. Gross et les conseillers juridiques internes d’Apple ont ensuite confirmé qu’il s’agissait d’une erreur, Gross précisant qu’ils « réglaient toute question en suspens ». Les allégations précises de la poursuite d’Apple n’ont jamais été soulevées et il n’y a eu aucun autre suivi avant le dépôt de la poursuite cinq mois plus tard.

From: Gabriel Gross
Date: Monday, February 23, 2026 5:53 PM
Subject: Former Apple Employees at OpenAI Retaining Non-public, Confidential, and Proprietary Information
To: <redacted> <redacted>

Dear Mr. Chang:

Please see the attached letter and let me know when you are free to discuss it.

Yours,

Gabriel Gross Partner Weil, Gotshal & Manges LLP <redacted> <redacted> <redacted> Direct <redacted> Mobile

The information contained in this email message is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by email, <redacted> and destroy the original message. Thank you.

Attachments:

  • image001.jpg (6K)
  • 2026.02.23 G. Gross letter to <redacted> Wang(101156327.1).pdf (225K)
  • Ex. A.pdf (491K)
  • Ex. B.pdf (91K)
  • Ex. C.pdf (1646K)
From: Gabriel Gross <redacted>
Date: Mon, Feb 23, 2026 at 6:06 PM
Subject: RE: Former Apple Employees at OpenAI Retaining Non-public, Confidential, and Proprietary Information
To: <redacted> <redacted>

Dear Mr. Chang:

Thank you for your phone call just now and for offering your cooperation so quickly. I will be back in touch after speaking with Apple. I realize I neglected to include the three attachments when I sent you my letter, so I am re-sending it with the attachments for your records.

Yours,

Gabe

From: Che Chang <redacted>
Date: Feb 23, 2026, at 8:04 PM
Subject: Re: Former Apple Employees at OpenAI Retaining Non-public, Confidential, and Proprietary Information
To: <redacted>

Hi [Apple in-house legal counsel] and [Apple in-house legal counsel],

This guy from Weil claims to be representing you. For some reason, he is lying about speaking with me on the phone. I don't know who he is and we have never spoken.

I don't know what the point of his lie is, but could you please confirm if he is actually representing you, and if so, whether you have other counsel you can use. I don’t think interacting through him is appropriate given this behavior.

If this isn’t the right Apple team, could you let me know who might be? Thank you.

Che

From: Gabriel Gross <redacted>
Date: Tue, Feb 24, 2026 at 11:22 AM
Subject: RE: Former Apple Employees at OpenAI Retaining Non-public, Confidential, and Proprietary Information
To: <redacted> <redacted>

Dear Mr. Chang:

I write to follow up on my email and letter from yesterday. After I emailed you around 5:53 p.m. yesterday, I inadvertently also sent you another email around 6:07 p.m. that was intended for <redacted> Wang, one of the former Apple employees at issue. After we had emailed Mr. Wang yesterday about retaining Apple information, he promptly called me and offered to cooperate with Apple in resolving any issues. I then intended to email him again, but accidentally replied to my email chain with you instead. I apologize for the confusion that likely caused.

Yours,

Gabriel Gross Partner Weil, Gotshal & Manges LLP <redacted> <redacted> <redacted> Direct <redacted> Mobile

Gabe

From: [Apple in-house legal counsel] <redacted>
Date: Wed, Feb 25, 2026 at 8:45 PM
Subject: Re: Former Apple Employees at OpenAI Retaining Non-public, Confidential, and Proprietary Information
To: Che Chang <redacted>; Cc: <redacted> <redacted>, <redacted> <redacted>, <redacted> <redacted>

Hi Che,

Wanted to make sure to get back to you. Weil is our counsel on this matter, and I believe they should have contacted you explaining the miscommunication. Please feel free to direct any additional questions their way.

Thanks,

[Apple in-house legal counsel]

Auteur

OpenAI