Two data center water stories are often collapsed into one alarming sentence: Amazon paid $20.5 million over nitrate pollution, and a California project wants 750,000 gallons a day from the Colorado River.
Both deserve scrutiny. Their legal meanings are different.
In northeast Oregon, Amazon Data Services agreed to a proposed $20.5 million class settlement resolving allegations that wastewater associated with its data center operations contributed to nitrate contamination. Amazon denied the allegations; settlement is not an admission of liability.
In California's Imperial Valley, a developer is actively litigating after the Imperial Irrigation District denied a request for roughly 750,000 gallons per day. Other plaintiffs are challenging environmental review and project approval. Those complaints are not final judgments.
This is a reality-check tracker of what has been alleged, settled, denied, and decided.
The legal scorecard
Matter
Water issue
Legal posture as of July 26, 2026
What can be said
Northeast Oregon Amazon settlement
Alleged contribution of data center wastewater to regional nitrate contamination
Proposed $20.5M class settlement; Amazon denies wrongdoing
Money and remediation/support terms can be described; liability was not adjudicated
IVCM v. Imperial Irrigation District
Access to about 750,000 gallons/day, roughly 260M gallons/year
Active developer lawsuit after district denial
Water was requested and denied; entitlement remains disputed
Whether the county adequately reviewed a massive campus
Active litigation by local government and/or challengers
Approval is contested; complaint does not equal invalidation
Sierra Club challenge
Environmental review, water, energy, and related impacts
Active suit
Claims exist; merits and remedies remain undecided
The first discipline is tense. Say “alleged” for unresolved factual claims, “agreed to settle” for a settlement, “denied” for an agency decision, and “the court held” only after a ruling.
Oregon: what the $20.5 million settlement means
Residents in the Lower Umatilla Basin have lived with severe nitrate contamination concerns for years. The class allegations connected Amazon Data Services wastewater practices to the problem. The proposed settlement creates monetary and programmatic relief while avoiding the cost and uncertainty of trial.
A responsible summary contains four clauses:
Plaintiffs alleged that Amazon-related wastewater contributed to nitrate contamination.
Amazon agreed to a proposed $20.5 million settlement.
Amazon denied the allegations and did not admit liability.
Settlement terms and court approval—not a liability verdict—define the outcome.
Leaving out clause three converts a settlement into a judicial finding. Leading only with clause three erases the fact that a company paid substantial money to resolve the claims. Both distortions are common.
The broader significance is that data center water risk extends beyond withdrawal. Discharge and waste management can create exposure even when a facility's cooling demand looks moderate. Permits should cover what enters a system, what leaves it, where it goes, and how it is monitored.
Imperial Valley: 750,000 gallons per day is a request, not current use
The proposed IVCM campus in Imperial County sits in a region where Colorado River allocations, agriculture, heat, and environmental justice make every large request politically significant. Reporting places the requested supply around 750,000 gallons per day—about 260 million gallons annually.
The Imperial Irrigation District denied access. The developer then sued seeking a path to the water. That sequence establishes a concrete resource conflict: request, denial, litigation.
It does not establish that the project is currently consuming that volume, that the developer has a legal entitlement, or that the district's position will survive review. The docket, injunctions, and final orders determine those questions.
Separate cases challenge whether county approvals received adequate environmental review. A city and environmental organizations have raised concerns involving water, energy, air, and cumulative impacts. Again, an active suit can delay financing and construction without yet overturning a permit.
Withdrawal, consumption, and discharge are different
Water numbers become misleading when these terms are mixed.
Withdrawal
Water taken from a utility, river, aquifer, or recycled-water system. Some may return to the source or enter wastewater treatment.
Consumption
Water not immediately returned to the original watershed, often because it evaporates in cooling. This is generally the more important scarcity measure.
Discharge
Water released after use. Its temperature, salinity, chemicals, and disposal path matter. A low-consumption design can still create a discharge issue.
Indirect water
Power generation can consume water away from the data center. A facility reporting only on-site water may omit a material part of the footprint; adding direct and indirect estimates without consistent boundaries can also double-count.
Viral estimates translate annual corporate water into bottles per prompt. They can communicate scale, but they cannot answer whether one proposed facility threatens one community.
The local result changes with:
air versus evaporative cooling;
outside temperature and humidity;
model training versus inference;
server utilization;
potable, recycled, brackish, or groundwater source;
seasonal and peak operation;
the power grid's water intensity;
wastewater treatment and reuse.
The right unit for a permit is a range by month and operating condition, with an enforceable peak. The right unit for an AI product is water per accepted task with the measurement boundary disclosed. Neither is a universal constant.
A permit checklist communities can use
1. Source
Name the utility, watershed, aquifer, reclaimed-water system, and legal entitlement. “Non-potable where available” is not a supply plan.
2. Peak and annual volume
Publish maximum daily demand, expected annual withdrawal, expected consumption, and drought-year operation. An annual average can hide the hottest day.
3. Cooling configuration
Identify air cooling, direct-to-chip liquid cooling, cooling towers, hybrid modes, and the temperature at which water use changes.
4. Discharge pathway
Identify wastewater composition, pretreatment, receiving system, monitoring wells, and responsibility if contaminants exceed limits.
5. Expansion
Tie water review to the full buildout, not only the first building. A campus approved in phases can multiply demand without repeating public scrutiny.
6. Enforcement
Specify meter access, reporting frequency, penalties, stop-work triggers, and who can inspect. Voluntary goals are not permit limits.
7. Alternatives
Compare recycled water, dry cooling, a smaller campus, seasonal load management, and a different site. State the energy penalty of dry cooling rather than pretending trade-offs do not exist.
What companies should disclose
Annual sustainability reports are too aggregated for local accountability. A hyperscaler can reduce global water intensity while a single campus worsens scarcity in a vulnerable basin.
Publish site-level:
withdrawal and consumption by source;
monthly peak and drought performance;
wastewater and permit exceedances;
projected versus actual values;
cooling mode and water quality;
community payments and infrastructure commitments;
the methodology for indirect water.
If security concerns prevent exact operational detail, companies can report audited ranges and regulatory filings. The absence of perfect precision is not a reason for no disclosure.
What these cases may change
The Oregon settlement signals that waste pathways can create material legal exposure even when causation is contested. The Imperial Valley cases test whether agencies and developers can secure extraordinary water in an already contested basin and whether project-wide environmental review was adequate.
Future projects will likely respond with recycled-water commitments, dry or hybrid cooling, indemnities, monitoring, and more careful environmental records. Lenders may demand water-risk diligence much like interconnection diligence.
Community opposition also affects timing. Our data center backlash map distinguishes a lawsuit that merely exists from one that has produced an injunction or final block.
A reality-check framework for future headlines
When you see “data center sued over water,” ask:
Who sued whom?
Is the dispute about withdrawal, discharge, review, contract rights, or contamination?
What volume was requested, permitted, and actually used?
Has a judge issued an injunction or final judgment?
Did the defendant admit liability in a settlement?
What remedy is requested—money, new review, permit cancellation, or water access?
What is the reporting date?
This framework avoids both minimization and hype. A complaint may reveal a serious risk before trial. A settlement can impose real cost without proving every allegation. A permit denial can stop access today while an appeal continues.
Verdict
Amazon paid $20.5 million to resolve Oregon nitrate claims. True, subject to settlement approval and terms.
A court found Amazon caused the contamination. False; the settlement is not that finding, and Amazon denies wrongdoing.
The Imperial Valley project is using 750,000 gallons every day. Unsupported; that figure describes the requested scale at issue.
Water access and environmental review are being litigated. True.
These are merely protests. False. They involve formal settlement, agency denial, and court actions—though several merits remain undecided.
Data center water accountability improves when everyone uses exact verbs. The cases are consequential enough without turning allegations into judgments or requests into consumption.
What would change this scorecard
The Oregon entry should be updated when the court grants or denies final settlement approval, when claims-administration terms change, or when required programs report results. Those events do not retroactively create a liability verdict; they clarify how the negotiated resolution operates.
The Imperial Valley entries should change only with docket evidence: an injunction, merits ruling, dismissal, settlement, permit remand, or final water agreement. A developer press release or opponent statement can be logged as a position but should not move the legal-status column alone.
For both regions, environmental monitoring deserves a separate evidence track. Court posture answers who may proceed and under what remedy. Meter readings, sampling methods, permit reports, and enforcement records answer what happened to water. Keeping those tracks distinct prevents legal wins from being mistaken for scientific proof and prevents unresolved liability from erasing measured environmental conditions.
That separation is the foundation of a trustworthy running tracker: exact verb, exact document, exact date, and no inference beyond what the source supports.
This article is an editorial summary, not legal advice. Lawsuits, proposed settlements, approvals, and water requests can change after publication. Allegations are not findings, settlements are not necessarily admissions, and reported project demand is not the same as metered consumption.
