2026년 8월 3일

Apple은 잘못 판단하고 있습니다

로딩 중...

Apple은 역사상 가장 위대한 기업 중 하나로, 사소한 부분까지 집요하게 신경 쓰는 기업이라는 명성을 쌓아 왔습니다. 하지만 부주의하고 공격적이며 이상할 정도로 개인적인 이번 소송은 안타깝게도 그 명성에 걸맞지 않습니다.

Apple은 지난 2월 OpenAI에 연락했지만 답변을 받지 못했다고 주장했습니다. 그러나 저희가 이 사실을 지적하고 나서야, Apple은 외부 변호인들이 아시아계 성씨 두 개를 혼동해 엉뚱한 사람에게 이메일을 보냈다고 인정했습니다. Apple은 저희 법무총괄과 논의했다고도 주장했지만, 이제는 그런 논의가 전혀 없었다고 인정했습니다. 그러면서도 당시 이번 소송의 구체적인 주장을 전혀 제기하지 않았고, 오히려 저희에게 “모든 문제를 해결하고 있다”고 말했다는 사실은 또다시 숨기고 있습니다. 그 후 5개월 동안 아무런 연락도 없다가 갑자기 소송을 제기했습니다. Apple은 최근 제출한 서면에서 이러한 일련의 사건을 자신들에게 유리하게 포장하려 애쓰지만, 이메일은 여기⁠에서 직접 확인하실 수 있습니다.

Apple은 창 리우가 퇴사 후 Apple의 기밀 정보에 접근했다고 비난하면서도, Apple 직원들이 그에게 연락해 해당 정보를 찾는 일을 도와달라고 요청했다는 사실은 이제야 인정했습니다. 관련 메시지는 여기⁠에서 확인하실 수 있습니다. Apple은 이제 “잔여 접근 권한” 탓으로 돌리려 하지만, 직원이 퇴사할 때 시스템 접근 권한을 제대로 관리하지 않아 Apple에서 흔히 발생하는 문제라는 사실도 밝히지 않고 있습니다. 실제로는 퇴사하면서 올바르게 처신하려는 전직 직원조차 원하지도, 심지어 존재를 인지하지도 못한 Apple 파일에 계속 접근할 수 있다는 뜻입니다.

Apple은 탕 탄이 자사의 영업비밀을 입수해 이용하려 했다고도 비난합니다. 그러나 탕은 다른 회사의 기밀 정보를 원하지 않으며 절대로 사용해서는 안 된다는 점을 팀에 항상 분명히 밝혀 왔습니다. 탕은 24년 넘게 Apple에 헌신했으며, 회사에서 가장 혁신적인 리더 중 한 명으로 널리 알려져 있었습니다.

Apple이 소송을 제기하기 전에 이런 문제를 저희에게 알렸다면 좋았을 것입니다. 그랬다면 저희는 기꺼이 모든 내용을 설명했을 것입니다. 저희는 소송에서 제기된 주장을 심각하게 받아들였으며, 문제 해결을 위해 Apple과 협력하겠다고 제안했습니다. 그러나 Apple은 다른 전직 직원들에 대한 모호한 비난까지 동원해 주장을 바꾸려 하고 있으며, 앞으로도 이런 방식을 반복할 가능성이 큽니다.

Apple의 가처분 명령 신청은 허위 정보에 근거했을 뿐 아니라 전혀 불필요합니다. 저희는 Apple의 영업비밀을 보유하고 있지도, 원하지도 않기 때문입니다. 저희는 기술의 경계를 넓히는 혁신적인 제품과 기술을 만드는 데 훨씬 더 관심이 있습니다.

2026년 8월 6일 업데이트: 저희의 소송 기각 신청서는 여기⁠(새 창에서 열기)에서 확인하실 수 있습니다.

2026년 9월 1일 업데이트: Apple의 가처분 명령 신청에 대한 저희의 반대 의견서는 여기⁠(새 창에서 열기)에서 확인하실 수 있습니다.

2026년 9월 14일 업데이트: Apple의 보충 서면에 대한 저희의 답변은 여기⁠(새 창에서 열기)에서 확인하실 수 있습니다.

메시지

창 리우(파란색)와 Apple 직원들이 주고받은 iMessage입니다. 2026년 1월 22일이 Apple에서의 마지막 근무일이었던 창에게 전 직장 동료들이 Apple 업무에 필요한 파일과 정보를 찾도록 도와달라고 요청하고 있습니다(시간은 모두 UTC 기준). 참고: 다른 개인의 이름과 Apple의 기밀 정보는 가렸습니다.

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.”

이메일 서신

다음은 Apple의 외부 법률대리인 가브리엘 그로스, OpenAI의 법무총괄 체 창, Apple의 사내 법무 담당자들이 주고받은 이메일입니다. 이 이메일을 보면 그로스가 실수로 체에게 이메일을 보내고 두 사람이 대화했다고 잘못 주장했음을 알 수 있습니다. 이후 그로스와 Apple의 사내 법무 담당자는 모두 이것이 실수였다고 확인했으며, 그로스는 “모든 문제를 해결하고 있다”고 밝혔습니다. Apple 소송의 구체적인 주장은 전혀 제기되지 않았고, 5개월 뒤 소송이 제기될 때까지 추가 연락도 없었습니다.

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]