Back
India's Legal Framework Fails to Govern Data Center Water Use as AI Boom Strains Resources
India is racing to become the world's digital backbone, with tech giants pouring billions into hyperscale data centers across the country. Yet beneath this surge of investment lies an unaddressed crisis: the water these facilities consume is draining aquifers and municipal supplies in regions already facing extreme scarcity. The legal framework—designed for an era before AI—has no binding rules to control this runoff. Experts warn that without urgent intervention, the country's water tables will collapse under the weight of its own ambition.
The scale of the problem is staggering. A 2026 white paper from the estimates that India's data centers consumed roughly 150 billion liters in 2025—a number expected to more than double by 2030. A single 100-megawatt hyperscale facility can gulp up to 2 million liters daily, enough to meet the annual needs of thousands of households. Meanwhile, , the government's own policy commission, has declared the country's water emergency the worst in its history, with nearly 600 million people under high to extreme stress and demand projected to outstrip supply by 2030. This is not a footnote; it is a structural collision.
A Booming Sector, A Thirsty Reality
The recent wave of investment is staggering. In , Microsoft CEO Satya Nadella stood beside Prime Minister Narendra Modi to pledge $17.5 billion for data centers across India—the company's largest commitment in Asia. Google followed with a $15 billion gigawatt-scale campus near Visakhapatnam built with the Adani Group, and Amazon raised its own India investment by $35 billion. To seal the welcome, the union budget extended a tax holiday to foreign cloud firms until 2047. New Delhi's message is unmistakable: India is open for business.
But the announcements conveniently omit water. Data centers cluster in precisely the regions facing the most severe water stress: Mumbai, Chennai, Hyderabad, Bengaluru, and the Delhi capital area. counts 50 Indian facilities already in "extremely high" water-stress zones, while finds more than half of national capacity in stressed regions. projects that 60-80% of Indian data centers will face high water stress this decade. The geography of AI is colliding with the hydrology of a nation running dry.
The Physics of Cooling
The problem begins with physics. Servers generate immense heat; if not cooled properly, they fail. The dominant fix—evaporative cooling—sheds heat into the air as vapor, water that never returns to the local watershed. AI data centers are even worse: the chips that train large language models run far hotter than ordinary cloud hardware, making the facilities not just more numerous but thirstier per square meter. Water use climbs faster than capacity.
Crucially, data centers do not inherently need fresh water. Their cooling systems require water of controlled quality, not necessarily drinking water. Treated effluent can serve, and closed-loop systems that seal the coolant circuit use a fraction of what open towers consume. The alternatives exist, but the incentive to use them does not. Absent regulatory pressure, operators default to the cheapest reliable source—municipal supply or, where the mains fail, groundwater. This default is a choice of policy, not physics.
A Legal Vacuum
India has built an elaborate machinery for attracting data centers and almost none for governing their thirst. Half a dozen states dangle stamp-duty waivers, power subsidies, and single-window clearances; Tamil Nadu's policy even lists guaranteed water supply as a perk. Yet there is no binding rule on how much water a data center may draw, or whence. There is no sector-specific water-impact assessment, no mandatory disclosure of withdrawals by source, no bar on extraction in blocks the has already declared overexploited, and no default duty to use treated wastewater where it exists. Of fifteen state data-center policies, only five mention sustainability at all, and the language is aspiration, not obligation.
The instrument that might have filled the gap has been neutered. Under India's
, data centers are typically waved through as "building and construction"—a category that requires neither a public hearing nor a full impact study. The
and the
were never written for the hydrological footprint of dense computing, and they have not been amended to fit it. As the authors of the analysis put it:
"The legal toolbox is not empty; none of the tools has been pointed at this problem."
Constitutional Imperative
The silence cannot outrun a constitutional question. has read a into the under , and the forbid the state from alienating common water for private gain without justification or safeguards. When a district's driest block acquires a gigawatt data center, approved in days and without consultation, the question is no longer administrative. It becomes a clash of : whose claim on a scarce resource comes first, and who made that decision, and how?
The Visakhapatnam example is instructive. In , the state environmental authority cleared two data-center parks—of 1,000 and 697 megawatts—within days of application and without a public hearing. Its own minutes recorded appraisal for solid, liquid, and air pollution alone; operational water use went undisclosed. Scientists and the have since asked the regulator to suspend and review the approvals. This is not an isolated case; it is the pattern.
Learning From Global Precedents
India is not the first country to face this tension. Singapore, the Netherlands, and Ireland each froze new data-center development as strain on power, land, and water mounted. When Ireland lifted its in , it swapped prohibition for a condition: large new facilities must bring their own dispatchable power and feed the grid when asked. The principle—that those who benefit from a shared resource should help sustain it—transfers directly to water.
Big Tech's own promises reveal what is possible. Google has pledged to be "water-positive" by 2030, backing $500 million in water infrastructure and 165 replenishment projects across 97 watersheds. Microsoft has unveiled a closed-loop design that all but eliminates evaporative cooling, saving some 125 million liters annually per site. These are real commitments, made precisely where investor scrutiny, disclosure rules, and local anger compel them. In India, where none of those forces yet binds for water, the incentives point the other way.
A Call for Governance
The case here is not against investment. India needs the computing power and sovereign data infrastructure these campuses bring, which underpin public services, financial inclusion, and health platforms. The case is that investment without governance is a wager placed with a public resource—the water that households, farmers, and future generations will also need.
A coherent framework is within reach without a single new statute; it needs political will, not parliamentary time. The essentials are plain: a dedicated impact-assessment category for large data centers, with a mandatory water audit, public consultation, and enforceable sourcing conditions; annual disclosure of consumption by source, which the market regulator's sustainability-reporting regime could readily absorb; a ban on fresh groundwater in critical blocks; treated wastewater as the default where supply allows; siting guidance keyed to water stress; and closed-loop cooling required rather than suggested for hyperscale. None of this tells hyperscalers they are unwelcome. It tells them, in advance, the terms of welcome.
The Hidden Subsidy
Economists have a phrase for what is otherwise at stake: the hidden subsidy. When a hyperscale campus draws on a municipal system in a city that rations water each summer, the true cost—the household left dry, the farmer chasing a falling aquifer—never enters the operator's accounts. It is borne by the commons, and by those without the standing or means to object. India ranks 120th of 122 countries for water quality, some 200,000 of its citizens die each year for want of safe water, and its total demand is set to double its supply in the very decade its data centers double theirs. To build the AI economy on those terms is not a neutral transaction. It is a choice, made by the state in the name of development, about whose claim on a scarce resource comes first.
India should build the infrastructure its future demands. But it should build in the open knowledge that fresh water is not a subsidy to be quietly folded into the cost base of the digital economy. The window for governing well is still ajar, and the siting decisions taken now will set the water footprint of Indian AI for 20 years. Governing them is not an obstacle to that future. It is the condition of its lasting at all.
