Data Center Record.
Privacy

What this site knows about you.

Data Center Record is a public record of data center development. It is not a record of its readers. This page says what the site collects, why, and which companies handle it.

Effective September 17, 2026. Last updated October 20, 2026. Every change to this page is listed in its change history on the methodology page.

In short

  • You can read every page without an account, and the site's own code sets no cookie.
  • Two analytics services count visits: Google Analytics and Ahrefs Web Analytics. Neither records a replay of your visit or what you type, and the site shows no ads.
  • In the European Economic Area, the United Kingdom, Switzerland and Quebec, and anywhere the site cannot tell where you are, neither loads until you choose Accept. Everywhere else they load with the page, and you can turn them off.
  • If your browser sends Global Privacy Control, the record honors it: Ahrefs never loads and Google Analytics stores nothing in your browser.
  • You can change your choice at any time with the Privacy choices link at the foot of every page.
  • What you type into search or a ZIP code lookup, or into any form, is kept out of the analytics.
  • The site also uses Cloudflare Web Analytics (opens in a new tab), which sets no cookies and collects no personal data.
  • The site runs on Cloudflare, and Cloudflare's Turnstile checks that a form is sent by a person.
  • What you type into a form is stored for 12 months and read by a person. A newsletter address is deleted 30 days after you unsubscribe, and any address is deleted on request within 30 days.
  • Contributions go through Stripe on Stripe's own pages. The record never sees a full card number.
  • The record takes no money from data center developers, operators or advocacy groups, carries no ads, and does not sell visitor data to anyone.

Reading the site

The pages are static files. Reading them needs no account and no login, and there is nothing to sign up for except the newsletter. The site's own code stores two things in your browser: whether you chose Reader or Researcher view, and your choice about visit counts once you make one. Neither leaves your browser and neither is a cookie.

A record page with a map loads aerial imagery from a United States Geological Survey server, so that server receives the request for the map tiles the way any server receives a request for an image.

The detail

The view choice is stored under the key dcr-mode in localStorage by a script in the page layout. The visit counts choice is stored under dcr-consent in localStorage as the version, yes or no, and the date it was made; it is asked again after twelve months. If your browser does not allow the site to store it, the site asks again on your next visit and, in the regions that need a yes first, loads nothing until then. The fonts are served from this site, not from a font service. The imagery is the USGS National Map orthoimagery tile service, requested by your browser only on a record page with a located site. The county, city and state maps use boundary files served from this site and no outside tile server.

Analytics

Two analytics services count visits, so the record can see which pages are read and where readers arrive from, which is how it decides what to build next. Each is a script written and run by the company named, and each reports a visit to that company under that company's own privacy policy.

  • Google Analytics (GA4), by Google, counts visits and page views, and the events it measures by default, such as scrolling to the foot of a page or following a link to another site. It is set up for counting only: Google signals and ad personalization are turned off, every advertising signal is refused, and it is not linked to any advertising account. Google's privacy policy (opens in a new tab).
  • Ahrefs Web Analytics, by Ahrefs, counts visits and page views without cookies. Ahrefs's privacy policy (opens in a new tab).

When they load. In the European Economic Area, the United Kingdom, Switzerland and the Canadian province of Quebec, a small bar at the foot of the page asks first, with Accept and Reject side by side, and neither service loads until you choose Accept. If the site cannot tell where you are, it treats you the same way. Everywhere else both load with the page, there is no bar, and you can turn them off at any time.

Global Privacy Control. If your browser sends the Global Privacy Control signal, the record treats it as your choice not to be counted, with no prompt. Ahrefs does not load. Outside the regions above, Google Analytics loads in a mode that stores nothing in your browser and sets no cookie, and sends Google only a page view with no identifier; inside them, nothing loads at all. The record publishes its support for the signal at /.well-known/gpc.json.

What you type stays out. Search terms, ZIP codes and anything typed into a lookup box or a form are never sent to either service. The search results page takes the term out of its own address before either service loads, and Google Analytics is given each page's address without anything after a question mark.

Cookies. Google Analytics may set cookies of its own once you accept, or where it loads without a prompt; Ahrefs Web Analytics sets none. What each sets is on the vendor's own page: Google Analytics cookies (opens in a new tab) and Ahrefs Web Analytics (opens in a new tab), which states it works without cookies. A browser setting or extension that blocks either script does not break any page, because no page depends on them.

The site does not record sessions or draw heatmaps.

The detail

One script in the head of the page layout is the only code on the site that loads either service. Before anything else it sets Google's Consent Mode defaults to denied for ad storage, ad user data, ad personalization and analytics storage. It then reads a stored choice, if there is one, and otherwise asks the site's own server where the visit comes from: the server reads the country and region Cloudflare already attaches to the request and the Sec-GPC header, answers yes or no, and the record's own code keeps none of it. If the answer does not come within a second and a half, the visitor is treated as one who must be asked. Only then does the script load what those answers allow.

Google Analytics runs as the standard gtag script with property G-3CT7PDEJYK and this configuration: allow_google_signals false, allow_ad_personalization_signals false, the page address and the referring address without their query strings, and analytics_storage granted only where the rules above allow it. Ahrefs runs as its standard script with the site's data key, after the first touch, key, pointer or scroll, or three and a half seconds after the page loads. A build check fails the site build when any page loads either service any other way. Nothing else from these companies is loaded, and the record's own database holds no analytics data.

Your choices

The Privacy choices link at the foot of every page opens one setting, Count my visits, which you can turn on or off at any time, wherever you are. Turning it on takes effect at once. Turning it off stops Google Analytics at once and Ahrefs from the next page you open. The choice is kept in your browser, under the name dcr-consent; it is not a cookie, the record never sees it, and it is asked again after twelve months.

Without JavaScript, neither service loads at all.

Hosting and the bot check

The site is served by Cloudflare. Cloudflare handles every request to deliver and protect the site, and keeps short term logs of those requests under its own privacy policy (opens in a new tab). The forms on this site use Cloudflare Turnstile, which checks that a form is being sent by a person rather than a script. Turnstile is a script from Cloudflare that runs on the tip, contact and newsletter forms and nowhere else.

The detail

The site is a Cloudflare Worker serving static files; the Worker itself handles only the form and newsletter endpoints and a few redirects. When a form is submitted, the Worker sends the Turnstile token and the sending address to Cloudflare's verification endpoint before anything is stored, and rejects the submission if the check fails. Cloudflare's Workers Logs is on for the site Worker; its log lines carry a submission id and an error code when something fails, never the message or the sender, and Cloudflare keeps them under its own policy. The forms run on the record's own Turnstile key.

Tips, corrections and the contact form

When you send a tip, a correction, a report of a change on a page, or a message through the contact form, the record stores what you typed: the message, the page or project it is about, a link if you gave one, and your name and email address if you gave them. Both are optional. An address is used only to ask you a follow up question about what you sent.

Each message is stored in the record's database for 12 months and then deleted, and is forwarded by email to the editor. Messages are read by a person. They are not published, and a tip is never itself a source: what enters the record is the document the tip points to.

The detail

The Worker stores each submission as one row in the form_submissions table: the kind (tips, corrections, contact, report a change), the fields typed, the page it came from, the email address if given, the delivery state and the time. The table is not readable by the site or by the public. A weekly job deletes every row older than 12 months. The email forward goes through Resend to the record's own address, with your address as the reply address when you gave one. Nothing about the sending device is stored beyond what the Turnstile check needs.

The newsletter and local alerts

Signing up stores your email address and the track you chose, the Weekly Record or the full change log. Nothing is sent until you open the confirmation link, and every issue carries a one tap unsubscribe link. The list is not shared with anyone and is not sold. The newsletter is sent through Resend (opens in a new tab), an email delivery service, which handles the sending on the record's behalf.

A local alert works the same way. Asking for alerts on a project, a county or a city stores your email address, the project or place, and which of the three alerts you picked (a data center proposed, opening, or closing or cancelled). Nothing is sent until you open the confirmation link. Then one email goes out on a day the record shows such a change in the place or within 25 miles of it, and each carries a one tap link that stops it. The box can also sign you up for the Weekly Record in the same step, with its own confirmation link.

Unsubscribing stops every message at once, and the address is deleted 30 days after the unsubscribe. Any address is deleted on request within 30 days: write to contact@datacenterrecord.org.

The detail

A signup is one row in the subscribers table: the address, the track, a status (pending, confirmed, unsubscribed), a confirmation token, an unsubscribe token, the time of each step, and the word site as the source. The confirmation link and the unsubscribe link carry those random tokens and nothing else. Each issue carries the List-Unsubscribe headers that let a mail client unsubscribe in one tap. An unsubscribe marks the row unsubscribed at once and the weekly retention job deletes it 30 days later. Every message carries the publisher's mailing address in its footer, and no message can send until that address is set.

An alert is one row in the follows table: the address, the project or place, the alerts picked, the distance it reaches (25 miles), a status, a confirmation token, an unsubscribe token and the time of each step. The record's console reads the day's changes in stage from its own log once a day and sends one message per row through Resend; each message sent is one row in mail_sends (the address, what it carried and whether it was delivered), kept so no message goes twice. An unsubscribed alert is deleted 30 days later by the same weekly job. No model or analytics service reads any of it.

Contributions

A contribution is made through a Stripe payment link, on a page Stripe (opens in a new tab) runs. Stripe handles the payment; the record never sees a full card number. The email address you give Stripe is used only for your receipt. Payment records are kept as long as tax law requires. Contributions are not tax deductible. Supporters are never named unless they ask to be, and no total or count of contributions is published.

The record takes no money from data center developers, operators, tenants or landlords, from utilities or power producers, from their trade associations or lobbyists, or from any advocacy group on any side of a project. The full funding rule and the ownership disclosure are on their own pages.

What the record does not do

  • It does not sell, rent or share visitor data with anyone.
  • It carries no advertising and no sponsored placement.
  • It has no user accounts and keeps no profile of a reader.
  • It does not add an address to the newsletter from any form; only the signup box and the alerts box, when you tick it, do that, and only after confirmation.

If you are named in the record

The record publishes public statements by named officials, executives and speakers, each with its date and source, as said. If a statement or a fact about you is wrong, write to corrections@datacenterrecord.org with the source that shows the correct information. Corrections are published, dated, on the corrections log.

For readers outside the United States

The record is run from the United States, and the companies named on this page may process what they receive in the United States. Readers in the European Economic Area, the United Kingdom, Switzerland and Quebec are asked before any visit is counted, as described above. Requests about your information, including access and deletion, go to contact@datacenterrecord.org.

Who to ask

Data Center Record is owned and operated by Colton Digital Consulting LLC. Questions about this page, and requests to have your message or your newsletter address removed from the record's store, go to the address below. A removal is done within 30 days.

Email: contact@datacenterrecord.org. Mailing address: Data Center Record, PO Box 1564, Corvallis, OR 97333.

Researcher view · basis and source tier on every row · docket and Census GEOIDs · citation and export tools

Commercial and bulk data