Masley Challenges Data Center Water Use Claims

Data center numbers don’t add up, Masley says.

On a recent Lawfare podcast, Andy Masley argues that industry claims about data center water use, land use, electricity rates, and local community impacts are often misleading. He frames the debate around scaling laws that govern how much power and water these facilities actually require as compute demand grows, and why surface-level claims can obscure the real sources of pressure on grids, communities, and ecosystems. The conversation places a spotlight on how data centers expand and where the bottlenecks and tradeoffs really lie for operators, regulators, and nearby residents.

Masley’s core contention is that words like “efficient” and “low impact” tend to overlook crucial context. He emphasizes that efficiency gains in one area do not automatically translate into lower overall footprints when demand expands. For example, even if a cooling system becomes more energy efficient, the total energy draw can still rise as digital services scale. That dynamic matters for policymakers who worry about electricity prices, local grid stress, and the reliability of supply for both consumers and industrial users. It also matters for communities negotiating siting outcomes, water rights, and long term infrastructure investments. The episode maps out why blanket assurances about water or land impacts risk misinforming stakeholders who must plan around climate variability, drought, and regional water baselines.

A key thread is geography. Water use is not monolithic; it depends on climate, cooling technology, and plant design. In water-scarce regions, direct cooling flows raise concerns about rivers, aquifers, and municipal supplies. In cooler climates, air or dry cooling can reduce water dependence but may introduce other tradeoffs, such as higher capital costs or different maintenance needs. Masley argues that these nuances deserve transparent, apples-to-apples disclosures rather than sweeping, globally averaged statements. Without standardized metrics and verifiable data, he says, communities and regulators risk basing decisions on anecdotes instead of evidence.

For compliance officers and tech leaders, the discussion signals where the regulatory weather may shift next. The push for credible, comparable data on footprints suggests a future where disclosures become part of procurement and permitting pipelines. Industry watchers should watch for moves toward standardized reporting of water use, energy intensity, and land impact broken out by climate zone and cooling method. And while this podcast does not declare new rules, it frames a policy-relevant question: how can regulators ensure that data center claims are verifiable at a granular level, so that communities understand what sits next to their neighborhoods and utility bills?

From a practitioner’s standpoint, several takeaways emerge. First, the relationship between cooling choices and water or energy footprints is highly context dependent; a one size fits all narrative is misleading. Second, siting decisions carry meaningful regulatory and community risk, because water rights, infrastructure access, and grid interconnection are the real levers for cost and reliability. Third, disclosures must evolve beyond headline numbers toward standardized, auditable metrics that reflect regional realities and cooling technologies. Fourth, as demand for compute grows, industry and regulators will increasingly test the tradeoffs between efficiency, cost, reliability, and environmental impact, pressing operators to balance scale with community stewardship. The ongoing dialogue signals that the next phase of data center policy will hinge on credible data, transparent accounting, and accountable governance rather than rhetoric alone.

In short, Masley’s critique reframes the debate from absolutes to data driven tradeoffs. The takeaway for executives is simple: quantify your footprint with credible metrics, prepare for stricter, standardized disclosures, and align siting and cooling strategies with transparent, verifiable data. The discussion remains a reminder that as digital infrastructure scales, truth in reporting becomes as important as performance claims.