The Three Doors That Close Before a Community Can Say No

When Origin Energy proposed building a data center at Australia's Eraring coal-fired power station, the mayor of Lake Macquarie saw a straightforward proposition. The region had hosted a power plant for decades. The transmission lines were already there. He called it a "great outcome" for a community facing the coal plant's eventual closure. ^[1]

Origin is currently undertaking a preliminary feasibility assessment to determine the viability of collocating data centres beside our fleet of generating and storage assets. — Origin Energy

The same logic is unfolding across Europe, where the utility Uniper has identified 10 former fossil-fuel sites — in the UK, Germany, Sweden, and the Netherlands — as ready-made homes for AI data centers, their grid connections and industrial footprints already in place. ^[2] These are the communities where consent was given long ago, when the power plant first went up. Nobody needs to hide anything, because the industrial bargain was already struck. They are the control group — and they show, by contrast, what is missing everywhere else. Where communities do not already host heavy industry, the AI buildout has produced something more systematic: a three-stage pattern of information suppression that closes doors in sequence, each stage shutting off a different route to public knowledge. The pattern is not a coordinated conspiracy — it varies by jurisdiction and developer — but it is consistent enough across at least five U.S. states and the European Union to describe as a strategy, and in at least one case the evidence of deliberate intent is written in the paper trail. Stage one closes the door before construction. Developers and local officials use nondisclosure agreements and code names to keep proposed facilities secret. In Minnesota, Hermantown officials labeled a 1.8-million-square-foot data center "light industrial" in environmental review documents and referred to it internally as "Project Loon," concealing its true nature from residents for more than a year. ^[3] The nonprofit MCEA, which sued over the deception, called it among the most extreme examples of keeping the public in the dark that it had seen — and noted it was the fifth such lawsuit in Minnesota in two months. ^[3] In Rosemount, Meta used the code name "Project Bigfoot." ^[4] In Wisconsin, at least five communities signed NDAs with developers; in Beloit, an agreement with Cambrin LLC kept "Project Corn Maze" secret for over a year. ^[5] State Senator Erin Maye Quade of Minnesota introduced legislation to ban the practice, arguing it stripped communities of their right to be involved in decisions about their own land. ^[4] The code names and NDAs serve a specific function: they prevent opposition from organizing before cement is poured. By the time a project becomes visible, the land is already zoned, the tax abatements are already negotiated, and the window for public input has largely closed. Stage two closes the door during construction, at the environmental permit stage. Here the mechanism is less intuitive but equally effective: developers classify massive facilities as "minor sources" of pollution to avoid the rigorous review that a "major source" designation would trigger. Under the Clean Air Act, a major source is any facility that emits more than 100 tons per year of a regulated pollutant — a threshold that triggers detailed modeling, public comment periods, and enforceable emission limits. A minor source faces none of that. Meta's Hyperion data center in Louisiana includes 44 natural gas boilers and multiple diesel generators, a configuration the Sierra Club argues would almost certainly exceed the 100-ton threshold. Yet Louisiana's Department of Environmental Quality classified it as a minor source. The Sierra Club is now challenging that classification, arguing the facility was improperly permitted. ^[6] The EPA added a second layer to this stage in May 2026, proposing a rule that would allow data center developers to begin site preparation — clearing vegetation, excavating land, pouring cement pads — before receiving air emission permits. ^[7] The rule's practical effect is to create sunk costs: once foundations are in the ground, it becomes politically difficult for regulators to reject a permit based on air quality concerns, because the developer can point to the millions already spent. Stage three closes the door after the facility opens, and it is the most explicit. In 2024, Louisiana passed a law prohibiting residents from using their own community monitoring results to allege regulatory violations. ^[8] Near Meta's Hyperion campus, residents found brown, disinfectant-smelling tap water and dust plumes from construction, but the data they collected cannot be used to challenge the facility. The Louisiana Bucket Brigade, a community environmental group, put the logic plainly.

A criminal does not want you to put in crime cameras. And that's exactly what we're seeing from industry in the state of Louisiana. — Louisiana Bucket Brigade

The same instinct traveled to Brussels. In April 2026, the European Commission adopted a confidentiality clause that classifies data center water consumption and energy efficiency as "commercially sensitive" information, shielding it from public disclosure. ^[9] The language was not written by regulators. It was drafted almost verbatim from lobbying proposals submitted by Microsoft and the trade group DigitalEurope. ^[9]

We are taking further steps to increase openness, while protecting confidential business information. — Microsoft

The result is that only 36% of eligible EU data centers report the required environmental data, and the public cannot access facility-level impacts. ^[9] A Microsoft spokesperson defended the company's position by arguing that transparency should not come at the cost of security or intellectual property. ^[9] This is the clearest evidence of deliberate intent in the entire pattern: a legislative text that traveled from a corporate lobbying document into binding regulation, with the effect of preventing communities from knowing what a data center consumes or emits. The three stages are sequential by design. Stage one prevents opposition from forming. Stage two prevents regulators from scrutinizing. Stage three prevents communities from challenging what has already been built. Each stage assumes the previous one succeeded — a facility that was never kept secret does not need a misclassified permit, and a facility whose permit was properly reviewed is harder to shield from post-construction monitoring. Communities have not been passive. Nebraska passed a law requiring data centers to disclose water and power consumption after Google self-reported consuming 732 million gallons in 2025. ^[10] Wisconsin's state Senate approved a ban on local-government NDAs with data center developers. ^[5] Florida's SB 484 grants local governments authority to reject projects and protect residents from grid-upgrade costs. ^[11] But each of these victories came reactively — after facilities were already consuming resources, after NDAs had already kept projects secret, after the legal framework had already been built around the assumption that communities would not push back. And that framework is formidable. In Shalersville, Ohio, a township trustee who tried to permanently ban data centers delivered a warning drawn from experience.

you will lose in court — Ron Kotkowski

The consent-based infrastructure map is not being drawn by where communities say yes. It is being drawn by where communities cannot know enough to say no — and by the time they learn, the doors have already closed behind them.