Published in News

Leaked email shows that Cook is cracking down on leakers

by on23 September 2021

Release the hounds - there shall be no leaking here

Apple CEO Tim Cook has warned employees about leaking company information and says he is cracking down on leakers.  Unfortunately his email was leaked and provided much mirth to the non-Apple press.  

Cook’s email was addressed to the “team” who he apparently just connected with at a global employee meeting on Friday which also, ironically, covered the matter of privacy.

“I'm writing today because I've heard from so many of you were incredibly frustrated to see the contents of the meeting leak to reporters. This comes after a product launch in which most of the details of our announcements were also leaked to the press.”

We are not sure how many staff members really got on the blower to complain to Cook that the meeting details had been leaked. But Cook seems certain that his phone was red hot with angry staffers so we will take his word for it.

Cook admits he “shared their frustration” as these opportunities to connect as a team are really important.

He said that such teamwork only happens if that content  stays within Apple. So in the spirit of improving teamwork, Cook said Apple was “doing everything in our power to identify those who leaked”, hunt them down like dogs and crucify them as a warning to other leakers.  

“We do not tolerate disclosures of confidential information, whether it's product IP or the details of a confidential meeting. We know that the leakers constitute a small number of people. We also know that people who leak confidential information do not belong here”, said Cook.

We know that Cook’s definition of a leaker is anyone who tells the authorities that management are harassing women or discusses their salaries so this is a pretty wide remit.

Apparently all this cracking down on leaders will enable Apple to get back to “the work we do to leave the world a better place”.

Last modified on 23 September 2021
Rate this item
(2 votes)

Read more about: