Docs show how Google's building its censored search engine for China, codenamed Dragonfly, using subsidiary 265.com to compile a list of sites China's blocking
even a censorship API. http://theintercept.com/... Ryan Gallagher / @rj_gallagher : Notably it's not just journalists Google is stonewalling about Dragonfly. I am hearing that company leadership has *still* not addressed the issue internally & managers have refused to address employee concerns. One week since the story broke, that is extraordinary. Brian Fung / @b_fung : Google is developing the blacklist for its upcoming Chinese search engine by tracking what people enter into Baidu on a site that Google owns: http://theintercept.com/... Henrik Moltke / @moltke : This is where we are: Google, who, in the past, were SO chatty & open, inviting tech journos / politicians to all kinds of blah blah events about democracy & Google are now less communicative about secret program than top US/UK spy orgs. Let that sink in: https://twitter.com/...
Context & Ripple Effects
The Intercept's document drop details the mechanics behind the censored China search engine Sergey Brin reportedly only learned of recently: subsidiary 265.com is harvesting what users type into Baidu to compile a list of sites China blocks, feeding a censorship API for the project codenamed Dragonfly. The reporting also documents an internal standoff — leadership has not addressed the project a week after it broke, and managers are refusing employee questions.
That standoff deepens across the subsequent coverage: Google took deliberate steps to keep Dragonfly quiet, including shutting some security and privacy team members out of key meetings, while search chief Ben Gomes' staff remarks appeared to contradict the company's limited-progress claims. Months later, employees were still finding code changes tied to the project, fueling suspicion that work continued in some form.
First-order effects
- Baidu users querying through Google-owned 265.com are having their searches repurposed, without their knowledge, into a blocklist for a service they never agreed to.
- Google's own workforce becomes the immediate affected party: unanswered employee concerns and excluded privacy and security teams turn an external controversy into an internal governance crisis.
Second-order effects
- The secrecy itself generates the leaks — each exclusion of oversight teams produces new sources for The Intercept, keeping Dragonfly in the news cycle on Google's least favorable terms.
- Using a wholly owned subsidiary as the data-collection layer shows other platforms how sensitive projects can be walled off from corporate accountability structures, a template regulators and rivals alike will study.
Third-order effects
- If the pattern holds, major consumer-internet companies will increasingly build state-compliant infrastructure through subsidiaries and internal silos, forcing employees, journalists, and eventually lawmakers to rely on leaks rather than disclosure for oversight.
- The episode hardens the question of whether search and AI systems operating under authoritarian content rules can be reconciled with the companies' stated values — a tension that follows any future market-reentry attempt.
The trend: Global platforms are building country-specific censorship apparatus through subsidiaries and compartmentalized teams, with internal dissent and press leaks serving as the de facto accountability mechanism.