17JUN

Virginia forces water draw into daylight

2 min read

10:13UTC

A new Virginia law will make water utilities report data-centre use separately from 2027, landing as Google fights to keep one Botetourt County site's draw sealed after a court forced its release.

← Back to Virginia taxes the backup, not the draw Jump to analysis ↓

IndustryDeveloping

Key takeaway

Virginia will make utilities publish data-centre water draw, closing the gap voluntary disclosure leaves open.

A new Virginia law, reported on 25 June and prospective to 2027, will require waterworks to break out data-centre sales from household and industrial customers, ending the aggregation that has hidden site-level draw.⁠¹ A utility that today reports one lumped figure will have to name what its data centres take.

The mandate lands on an awkward record. Google markets itself as the only hyperscaler that publishes per-site water figures, yet its Botetourt County subsidiary spent months fighting a freedom-of-information request for that exact site data, needing a November 2025 court order to release it.⁠² A Google director had argued in an affidavit that the numbers could let rivals infer the campus's size and design. The figures a judge finally prised loose, a draw rising from 2 to 8 million gallons a day, 7 to 30 times the utility's largest existing customer, never appeared in Google's own sustainability report.

The company had earlier answered the water question on its own terms, pledging $17m in replenishment as its Dalles, Oregon site faced a steep rate rise. That is the gap the law closes. Voluntary disclosure lets an operator choose the framing, the baseline and the offset; a statutory per-class report does not. Google's Botetourt fight shows what a company will do to keep a single site's number sealed even while branding itself the transparent one, which is why the 2027 mandate matters more than any pledge.

Deep Analysis

In plain English

Starting in 2027, Virginia's water companies will have to say exactly how much water data centres are using, separately from homes and factories. Right now that number gets lumped in with everyone else's, so nobody outside the company can see one site's actual draw. The law arrives just as Google has been fighting in court to keep exactly that kind of number secret for one of its Virginia sites, even though the company publishes its own water figures elsewhere, on its own terms, whenever it chooses.

Deep Analysis

Root Causes

The disclosure gap exists because water utilities have historically billed data centres inside an aggregated industrial-customer class, so no single invoice ever isolated one campus's draw; Virginia's law is a billing-classification fix, not a new water right or a discharge limit, which is why it took a legislative change rather than a permit condition to close it.

Google's Botetourt objection rested on a specific competitive-harm theory, that a precise gallons-per-day figure lets rivals infer a campus's size and cooling architecture, a concern its own voluntary aggregate reporting was structured specifically to avoid triggering.

What could happen next?

Consequence
Utility-level reporting from 2027 will let Virginia regulators and journalists compare data-centre water draw across sites for the first time, ending the aggregation that let voluntary corporate figures go unchecked.
Precedent
Other water-stressed states can adopt the same utility-reporting mechanism without waiting for a hyperscaler to volunteer site-level data.

Source Landscape

This story draws on neutral-leaning sources

Primary parallel: Microsoft's Racine, Wisconsin development agreement carried a non-disclosure clause covering community-impact data that only broke when Milwaukee Riverkeeper sued for the records, releasing a figure of 8 million gallons a year for the site's first phase; Google's Botetourt fight follows the identical pattern, litigation as the only route past a corporate non-disclosure posture.

Counter-parallel: Amazon has published no comparable electricity figures at all for any US site, so Virginia's new law, which binds water utilities rather than the operators directly, may prove the more durable transparency mechanism precisely because it does not depend on any single hyperscaler agreeing to disclose.

Consensus view: Lawrence Berkeley National Laboratory's (LBNL) national data-centre water-use research treats utility-verified, site-level reporting as the only reliable way to reconcile corporate sustainability claims against actual local draw, since self-reported aggregate figures let a company choose its own baseline and boundary.

Counter-view: Google's own sustainability reporting frames per-site publication as insufficient on its own, arguing a bare gallons-per-day figure without local hydrological context invites exactly the competitive-harm objection it raised in its Botetourt affidavit; the company presents its Oregon-style replenishment pledges as the more actionable disclosure.

Key tension: Whether mandatory utility-level reporting from 2027 forces the comparability Google's voluntary figures don't provide, or whether operators simply route disputed sites through the same competitive-harm objection that already took a court order to overcome once.

Sources:VPM·Roanoke Rambler

Mentions:Virginia →Google →Boone County →Milwaukee Riverkeeper →Racine →Lawrence →Oregon →Wisconsin →Microsoft →Amazon →

First Reported In

Update #9 · US data-centre backlash becomes law

VPM· 7 Jul 2026

Read original →

Causes and effects

Caused by

Google prices its water ahead of rules

Extends Google's water-transparency posture from the Dalles pledge to the Botetourt disclosure fight.

Occurred 3 Jun 2026

Read story →

This Event

Virginia forces water draw into daylight

Statutory per-class reporting removes the aggregation that lets operators publish flattering company-wide figures while site-level draw stays hidden.

Different Perspectives

Chilean data-centre developers

Seven projects, one linked to Google, asked SEA this month for rulings that they fall outside full environmental review; four declared diesel-storage volumes just under the review-triggering tonnage, mirroring the mechanism Alto Jahuel used in July. The clustering suggests the threshold is being engineered, not sized to need.

An Coimisiun Pleanala

Ireland's planning appeals body refused the €1.5bn Killala data centre on 17 September, overturning Mayo County Council's 2025 grant for lack of a fixed grid-connection agreement and no corporate renewable power-purchase agreement. The ruling makes matched-power evidence, not planning consent alone, the deciding factor.

Housing Assembly and Foxglove

The two groups' 6 August appeal, filed through the Legal Resources Centre, kept Cape Town's approval of Equinix's data centre suspended through this window over missing water, emissions, noise and diesel-generator data. Deputy Mayor Eddie Andrews confirmed on 20-21 September that the suspension holds.

Brazil (President Lula, signing Redata)

Lula signed Lei 15.504 on 15 September, creating the Redata tax programme and keeping the Senate's water cap with no veto, while Aneel authorised Scala's AI City to join the national grid from January 2028. Brazil is recruiting capacity other markets are now turning away.

Aragon regional government (Eva Valle)

Aragon's economy chief Eva Valle said on 11 September that Spain's draft decree, requiring 80% hourly-matched renewables via a 10-year power-purchase agreement, is unmeetable by any project and threatens Blackstone, Azora and Microsoft builds already under way. Aragon holds 3,600 MW of granted grid access against 108 MW built.

Texas Governor Greg Abbott

Abbott ordered TCEQ on 21 September to halt every pending data-centre permit until projects pay their own way and complete ERCOT and Texas Water Development Board audits. Texas built the country's most permissive data-centre market; freezing it signals even that market has hit its grid limit.