
Erin Brockovich’s New Target: The Data Center Playbook of Secrecy
Erin Brockovich is doing what she has always done best: turning quiet local harm into a national conversation. Her new campaign against data center secrecy is less an anti-tech crusade than a blunt critique of how infrastructure gets forced onto communities before anyone has a real chance to weigh in.
The pattern she describes is hard to ignore. Residents say projects are being proposed with NDAs, thin disclosure, and officials who either cannot speak or do not bother to explain what is coming. Brockovich says her map is collecting thousands of community submissions, and that the most common complaint is not just noise, water, or utility bills—it is transparency.
<> That is the real story here: data centers are not simply being built at scale, they are being governed at scale, and local communities are often the last to know./>
That matters because data centers are no longer niche industrial boxes on the edge of town. They are now core AI infrastructure, which means they pull on everything a community depends on: power grids, water systems, roads, and public trust. When those projects arrive through back channels, the backlash is predictable. People do not just object to the footprint; they object to the feeling that the decision already happened without them.
Brockovich’s framing is especially effective because she avoids the easy, lazy critique. She is not arguing that every data center should be blocked. She is arguing that the process is broken. That is a much harder claim for developers to dismiss, because it lands squarely in the territory of governance, not ideology.
A few signals explain why this issue is escalating so quickly:
- Nearly 4,000 submissions arrived after Brockovich’s call for reports, suggesting the concern is widespread, not anecdotal.
- Local complaints often center on higher electric bills and water stress, which are politically explosive because they feel immediate and personal.
- Some communities are already moving to pause, restrict, or block projects, which means the issue is becoming a permitting risk, not just a PR problem.
For developers, the lesson is uncomfortable but obvious: secrecy is now a liability. The old playbook—quiet site selection, minimal disclosure, and technical jargon when questions come up—looks increasingly brittle in an era when residents can compare notes instantly and organize just as fast.
The bigger implication is that AI expansion is colliding with a basic democratic expectation: if a project will reshape utility bills, water access, or local land use, people want to know before the deal is done. If the industry keeps treating community engagement as a box-checking exercise, Brockovich-style backlash will keep filling the vacuum.
In other words, this is not just a data center story. It is a warning shot for the entire AI buildout: if the infrastructure is opaque, the resistance will be loud.
Developers who want fewer fights will need more than better messaging. They will need real disclosure, earlier conversations, and less NDA-shaped decision-making.
That may sound inconvenient. It is also the cost of building in public.
