DCW
PROPOSAL WATCH FIRST: HELP TRACK NDAS, PUBLIC MONEY, WATER, POWER, AND LOCAL RECORD REQUESTS

Proposal watch and public-records tracker

Data Center Watch

1,418 proposal-watch1,145 proposed28 NDA leads7,362 mapped records930 approximate leads
HighProposed

Project Blue

Pima County / Tucson, Arizona

Local reporting says Pima County was bound by an NDA tied to the Amazon-backed campus, leaving some elected officials and the public without key impact details before a land-sale vote.

Amazon Web Services / Beale InfrastructureConfirmed NDASource category: public agency / civic recordData attached
Data coverageVerified fields are source-backed or moderator-reviewed.
NDA / secrecyVerifiedConfirmed NDA
Public moneySource leadPublic land-sale and economic-development negotiations were central to the local dispute.
WaterSource leadWater and energy details were reported as concealed during review.
PowerSource leadDeveloper sought a special utility arrangement after city annexation stalled.
Submit missing sourceReview source leads
Scale

290-acre campus proposal

Water

Water and energy details were reported as concealed during review.

Power

Developer sought a special utility arrangement after city annexation stalled.

Public money

Public land-sale and economic-development negotiations were central to the local dispute.

Reporting

Tucson SpotlightSecrecy around Project Blue prompts calls for NDA limitsPublic CitizenThe Secret Data Center Buildout
Confirmed NDA or major secrecy dispute Requested NDA or reported secrecy Reference / monitorAll proposed sitesReport FOIA requestSubmit a correction
24 resultsSearch by ZIP, city, county, state, operator, or project name
Methodology

Public-source starter tracker: 7,362 tracked records today, including 902 auto-promoted IM3/OSM baseline records and 1,313 FracTracker-derived records, plus 1,349 ATLAS North America location leads and 796 PeeringDB facility leads. This version also places 2,898 ATLAS backlog rows at city-level approximate coordinates when the city could be matched against an existing coordinate-backed North America record; unmatched backlog rows remain off-map until they can be placed responsibly. Public claims are separated as confirmed records, leads, submitted requests, or unresolved gaps.