Erin Brockovich is stepping into a new kind of fight—one that doesn’t start at a smokestack or a contaminated well, but at the paperwork and opacity that can hide environmental consequences until they’re impossible to ignore. In recent remarks and outreach tied to her latest mission, the environmental activist has turned her attention to data centers: the fast-growing backbone of cloud computing, artificial intelligence, and the digital services that now shape everyday life. But her focus isn’t on the existence of these facilities. It’s on what communities often can’t see about them—especially when it comes to water use, energy demand, and the downstream impacts that follow once servers move in.
Data centers are frequently discussed in terms of capacity and connectivity. Investors want to know how quickly power can be delivered. Tech companies want to know latency and reliability. Local governments want jobs and tax revenue. Yet Brockovich’s argument is that the public conversation too often stops at the surface level: where a facility will be built, how big it will be, and what kind of cooling system it will use in broad strokes. What she wants—what she’s pushing for—is transparency that reaches deeper: how decisions are made, what assumptions are used, what environmental reporting is actually provided, and whether residents have meaningful access to information before harm occurs.
Her message lands at a moment when data center expansion is accelerating across many regions. The demand curve for compute is steep, and the infrastructure required to support it is increasingly visible: new substations, new transmission lines, new industrial-scale buildings designed to run continuously. But visibility doesn’t automatically translate into accountability. Brockovich’s concern is that secrecy—whether intentional or simply baked into regulatory gaps—can leave communities with little ability to evaluate tradeoffs. And when the tradeoffs involve water and energy systems that are shared by everyone, the stakes become personal.
To understand why Brockovich is targeting “secrecy,” it helps to look at how data centers typically interact with the public record. Many projects move through permitting processes that require some disclosures: environmental assessments, building plans, and sometimes water-related documentation. However, the level of detail can vary widely depending on jurisdiction, the type of cooling technology, and how reporting obligations are structured. Even when documents exist, they may be difficult for non-experts to interpret, scattered across agencies, or released only after key decisions are already locked in. In practice, residents can find themselves reacting to a facility’s presence rather than participating in the evaluation of its environmental footprint.
Brockovich’s approach emphasizes that transparency should not be treated as a courtesy. It should be treated as a prerequisite for informed consent by the people who live nearby. That means not just publishing a summary of environmental impact, but providing clear, ongoing information about operational realities—especially those that can change over time as workloads scale. A data center isn’t a static asset. It evolves. Cooling loads shift. Power draw can increase. Backup systems may be tested more frequently. Water consumption patterns can change depending on weather, efficiency upgrades, and operational strategies. If reporting is limited to the initial build phase, the public may never learn how the facility performs once it’s fully running.
This is where Brockovich’s framing becomes distinctive. She’s not merely arguing that data centers should be regulated more tightly in the abstract. She’s pointing to a specific failure mode: the gap between what communities are told during planning and what they experience during operations. When that gap persists, environmental impacts can become a surprise rather than a known risk. And because data centers are often described as “clean” compared to older industrial sources, the public may assume their environmental footprint is minimal—until water withdrawals, heat rejection, or energy-related emissions become measurable and undeniable.
Water is central to her critique. Data centers require cooling, and cooling requires water in many configurations. Some facilities rely on air cooling, others use evaporative cooling, and many use hybrid approaches. The choice affects local water demand, the potential for thermal impacts, and the way water is sourced and managed. Even when a project claims to use “efficient” systems, the question for residents is whether the efficiency holds under real operating conditions and whether the facility’s water use is compatible with local supply constraints.
Brockovich’s emphasis on transparency also reflects a broader reality: water systems are interconnected. A withdrawal from one point can influence flows elsewhere. A discharge can affect temperatures and ecosystems. A facility’s operational decisions can interact with drought conditions, seasonal variability, and existing industrial or municipal demands. If the public can’t access detailed information about how water is used and managed—especially over time—then community members can’t evaluate whether the facility is adding stress to an already strained system.
Energy is the other pillar. Data centers consume enormous amounts of electricity, and their growth can strain local grids. That strain can lead to new generation, new transmission, and new emissions—sometimes far from the facility itself. Brockovich’s point is that environmental impact isn’t confined to the physical footprint of the building. It extends to the energy supply chain. If reporting focuses only on onsite operations while ignoring the broader energy context, then communities are left with an incomplete picture.
There’s also a political dimension to secrecy. Data centers are often portrayed as essential infrastructure, which can make scrutiny feel like an obstacle to progress. But Brockovich’s stance suggests that essential infrastructure still needs to be accountable. If a facility is critical to modern life, then the public should be able to understand how it affects shared resources. Transparency isn’t anti-technology; it’s pro-trust. Without it, the relationship between operators and communities becomes transactional: build first, explain later, respond only when concerns escalate.
What makes this moment particularly ripe for Brockovich’s intervention is that data center secrecy can take multiple forms. Sometimes it’s literal—information withheld or not required. Sometimes it’s practical—data exists but isn’t accessible in a way that residents can use. Sometimes it’s structural—reporting requirements are fragmented across agencies, leaving gaps in oversight. And sometimes it’s narrative—companies emphasize certain metrics while downplaying others, shaping public perception without necessarily violating any rules.
Brockovich’s mission appears to target the combined effect of these factors. She’s calling attention to the idea that communities deserve more than assurances. They deserve clarity about the environmental details behind the build plans. That includes how water is sourced, how cooling is managed, what emissions are associated with energy use, and what monitoring occurs once the facility is operational. It also includes whether there are mechanisms for residents to receive updates and raise concerns in a timely manner.
One of the most important questions raised by her campaign is whether regulators and operators treat environmental reporting as a one-time compliance exercise or as an ongoing obligation. Many systems are designed around permitting milestones. Once a facility is approved, the focus shifts to maintaining compliance with permit conditions. But if permit conditions don’t require granular operational reporting—or if they allow flexibility that can change environmental outcomes—then the public may not learn about evolving impacts. Brockovich’s push implies that reporting should be continuous and understandable, not just periodic and technical.
That doesn’t mean every data center must publish proprietary operational details. There are legitimate reasons some information may be sensitive. But Brockovich’s argument is that environmental impacts are not proprietary. The public should be able to evaluate them. Operators can protect business secrets while still disclosing the environmental metrics that matter: water withdrawals and consumption, cooling performance indicators, waste handling practices, emissions associated with energy use where relevant, and monitoring results that show whether the facility is meeting environmental expectations.
Another angle in her messaging is the concept of community-level knowledge. Residents often learn about data center projects through zoning notices, public hearings, or local news coverage. Those channels can be overwhelmed by the sheer number of projects and the complexity of technical documents. Brockovich’s involvement signals a desire to make the process more legible. If the public can’t interpret what’s being proposed, then transparency becomes performative. The goal should be to provide information that supports real decision-making, not just formal disclosure.
Her campaign also implicitly challenges the assumption that environmental impacts are always localized and immediate. Data centers can create long-term effects through infrastructure buildout. A facility may require new power lines or upgrades to existing grid components. Those upgrades can have their own environmental footprints—land use changes, construction impacts, and emissions associated with new generation. If the environmental review for a data center doesn’t account for the full chain of infrastructure development, then the public may underestimate the true scope of the project’s impact.
This is where Brockovich’s “unique take” becomes more than a slogan. She’s effectively reframing the debate from “Where will the building go?” to “What systems will it depend on, and what will those systems do to the environment?” That shift matters because it changes what counts as relevant information. It pushes the conversation toward integrated assessment: water sourcing and discharge, energy procurement and emissions, grid impacts, and the monitoring needed to verify claims.
The story also intersects with the growing political pressure around AI and compute. As AI adoption accelerates, data centers are no longer just a background utility. They are part of the narrative of technological progress. That makes it easier for operators to argue that scrutiny should be limited or delayed. Brockovich’s response is that the environmental costs of compute cannot be treated as an externality. If society is building a new layer of digital infrastructure, then society must also build the governance structures that ensure it doesn’t quietly degrade local environments.
So what might happen next? The most immediate outcome would likely be increased scrutiny on disclosure and reporting. Brockovich’s involvement can amplify public attention, which often translates into pressure for clearer requirements. Regulators may face calls to standardize environmental reporting for data centers, including more consistent water and energy-related metrics. Operators may be pushed to provide more accessible documentation and to commit to monitoring practices that go beyond minimum compliance.
Another likely development is a shift in how communities engage with projects. Instead of focusing solely on whether a facility is “allowed,” residents may demand answers to operational questions: How much water will be used under peak demand? What