Sources detail the measures Google took to keep Dragonfly under wraps, including shutting out some members of the security and privacy teams from key meetings
including to most Google employees — and resigned in protest after a month of internally fighting for clarification,” writes Jack Poulson. http://theintercept.com/... Ryan Gallagher / @rj_gallagher : I spoke again today to the four sources quoted in the story, all of whom worked on Dragonfly, & one of whom had a leading role on the privacy side. They stand firmly behind their accounts. Maybe you should talk to your colleagues, Heather. http://twitter.com/... Ryan Gallagher / @rj_gallagher : This is a key point - Zunger said similar to me. He was more concerned about the surveillance than the censorship, because he believed the former would result in more tangible harms for Chinese people - interrogation, detention, jail, even death in an extreme case. https://twitter.com/... Jeremy Ashkenas / @jashkenas : Impressive Intercept story on how internal concerns about Project Dragonfly were overruled at Google: https://theintercept.com/... It's important to remember that Dragonfly isn't just a censored search engine. That's (relatively) small potatoes. It's all about the mass surveillance. Ryan Gallagher / @rj_gallagher : NEW: Google executives shut out privacy & security teams from key meetings on China censored search project & did not address human rights concerns that were repeatedly raised internally dating back nearly two years: http://theintercept.com/... #Dragonfly Liz Fong-Jones / @lizthegrey : This article changed my mind about whether the leak of Dragonfly and all this trouble could have been averted by someone internally whistleblowing to me and us sticking to internal activism. Execs knew it was dubious. They didn't care. http://twitter.com/... Richard Nieva / @richardjnieva : Google's response to @rj_gallagher's Dragonfly story pic.twitter.com/XqGxjXwkzv Caesar Sengupta / @caesars : This was not my experience of working on Dragonfly. 1) There was no sidelining of privacy and security 2) Scott or our business teams do not run the privacy or product processes 3) Scott is a person of very high integrity. https://twitter.com/... Liz Fong-Jones / @lizthegrey : As usual, I do not speak for my employer, nor do I vouch for the authenticity of any of this. However, I do want to say that @yonatanzunger has been my counterpart on the other side of the negotiating table dozens of times, and I believe his ethical backbone is ironclad. http://twitter.com/... Ryan Gallagher / @rj_gallagher : Every new product or service that Google develops must be reviewed by legal, privacy, & security teams, who try to identify potential issues or problems. But with Dragonfly, the normal procedure was not followed: Company execs appeared intent on watering down the privacy review. Alex Stamos / @alexstamos : I am a big fan of the Google security team, including a number of people who did incredible work during the 2008-2009 Aurora attacks. I'm not surprised that they have been cut out of the loop. https://t.co/caV1RKvLtz Brandon Downey / @bdowney : This is the most jaw dropping of the Dragonfly stories. 1. Sundar lied (both to the public and Google). 2. The guy in charge of the project tried to trample on privacy (and probably security) reviews. 3. They KNEW this was a bad idea, so they hid it internally and externally. https://twitter.com/... @toorsdenote : As a Xoogler, I want to point out that Google's corporate culture (with some notable exceptions) is that everyone in the company can see everyone else's code, design docs, assigned bugs, postmortems, etc. That makes this level of secrecy about Dragonfly especially shocking. http://twitter.com/... Ryan Gallagher / @rj_gallagher : Zunger said that in early 2017 he pointed out to executives managing Dragonfly that Chinese people could be at risk of interrogation or detention if they were found to have used Google to seek out information banned by the government. Ryan Gallagher / @rj_gallagher : “They [leadership] were determined to prevent leaks about Dragonfly from spreading through the company,” said a current Google employee with knowledge of the project. “Their biggest fear was that internal opposition would slow our operations.” Ryan Gallagher / @rj_gallagher : But Scott Beaumont, Google's head of operations in China & one of the key architects of Dragonfly, did not view Zunger's concerns as significant enough to merit a change of course, according to four sources. @mcmillen : This details reported here are —pardon my lingo — “big yikes” if true. Yonatan at Google was an effective leader of large engineering projects: known for having both the ear of upper management, and the willingness & desire to listen to employee concerns; and to bridge that gap. Ryan Gallagher / @rj_gallagher : Some of those working on Dragonfly believed that Beaumont may have misrepresented Brin's position in an attempt to reassure them that the effort was fully supported at the highest levels of the company, when that may not have been the truth. Ryan Gallagher / @rj_gallagher : When Dragonfly leaked, Beaumont fumed, sources said. “His ideal circumstance was that most people would find out about this project the day it launched.” He told colleagues he feared the leaks may have scuppered the prospect of Google launching the platform in the short term. Ryan Gallagher / @rj_gallagher : “The [Dragonfly] project, as it was then specified, was not something I could sign off on in good conscience,” Zunger told me. Ryan Gallagher / @rj_gallagher : Once you read my new story & the details about how Google execs shut out the privacy team on Dragonfly, revisit what Google's privacy chief told Congress in Sept: “I'm not clear on the contours of what is in scope or out of the scope of that project.” https://www.cnbc.com/... Ryan Gallagher / @rj_gallagher : The Dragonfly teams were instructed, however, that they were not permitted to discuss the issue directly with Brin or other members of Google's senior leadership team. Beaumont wanted all communication with top leadership to be directed through him. Ryan Gallagher / @rj_gallagher : Important to remember, none of this would be happening without the whistleblowers who took big risks to leak info on Dragonfly a few months ago. It'd still be secret without them. https://theintercept.com/... Ryan Gallagher / @rj_gallagher : When we revealed Dragonfly back in August, many people inside & outside of Google were stunned b/c they didn't understand how Brin could have reversed his strongly held position on censorship — particularly given that censorship & survellance have worsened in China since 2010. @mcmillen : I am not vouching for the truth of anything in this article, and not speaking on behalf of my employer — but I have trusted and respected @yonatanzunger for many years, and am glad he came forward to speak out about his involvement with Dragonfly. http://twitter.com/... Julia Carrie Wong / @juliacarriew : Google's own privacy team “concluded that Google would be expected to function in China as part of the ruling Communist Party's authoritarian system of policing and surveillance” http://theintercept.com/... Ryan Gallagher / @rj_gallagher : I spoke to @YonatanZunger, who was until last year a 14-year veteran of Google & one of the leading engineers at the company. He was among a small group who had been asked to work on Dragonfly — he was tasked with producing a privacy review of the China search engine. Ryan Gallagher / @rj_gallagher : Beaumont “wanted the privacy review [of Dragonfly] to be pro forma and thought it should defer entirely to his views of what the product ought to be. He did not feel that the security, privacy, and legal teams should be able to question his product decisions,” Zunger said. Mark Bergen / @mhbergen : “Two sources working on Dragonfly believed that Beaumont may have misrepresented Brin's position in an attempt to reassure the employees..."New Intercept story comes out swinging at Google's China chief. http://theintercept.com/...
Context & Ripple Effects
The Intercept's Dragonfly reporting has escalated across 2018: August documents showed the censored search engine built on subsidiary 265.com compiling a list of sites China blocks, and reports suggested Sergey Brin only recently learned how far along the project was. An October transcript of search chief Ben Gomes addressing staff appeared to contradict Google's official line of limited progress.
This story shifts the arc from what Dragonfly does to how Google governed it: sources say privacy and security teams were shut out of key meetings, communications to senior leaders including Brin were routed through Scott Beaumont, who sought to make the privacy review pro forma, and Yonatan Zunger resigned in protest after internal disputes over the surveillance implications.
First-order effects
- Google's internal privacy review is publicly contested: whistleblower accounts of sidelined teams collide directly with Caesar Sengupta's denial that privacy and security were cut out of Dragonfly decisions.
- The project is costing Google people, not just reputation — Zunger's protest exit and Jack Poulson's month of internally fighting for clarification before resigning turn a product dispute into visible departures from the privacy side.
Second-order effects
- Compartmentalization is raising the cost of denial: by March, employees citing recent code changes believed Dragonfly was still being worked on, undercutting any claim the project had been shelved.
- Gomes's October remarks already showed executives' public framing diverging from internal reality; today's sourcing hardens that gap into a credibility problem with Google's own workforce, making every future Dragonfly statement subject to leak-driven fact-checking.
Third-order effects
- If the pattern holds, state-sensitive projects get governed through a narrow executive channel with pro forma ethics review — a structure where compliance and privacy functions are informed of decisions rather than consulted on them.
- Employee whistleblowing to the press becomes the de facto oversight mechanism for projects whose internal review channels have been closed, a governance model that trades short-term secrecy for recurring public exposure.
The trend: State-facing tech projects are increasingly run through executive side-channels that bypass internal review, leaving whistleblowers and press leaks as the main accountability mechanism.