daylight · privacy

Privacy, and what we count

Daylight measures federal sites for how they watch the public. It would be incoherent to quietly do the same thing here. So this is the entire account of what Daylight records about your visit — stated as a commitment, then shown live from the actual data below.

the pledge

No cookies. Daylight sets none. There is no consent banner because there is nothing to consent to.
No third parties. No Google Analytics, no Meta pixel, no external fonts or CDNs phoning home. The page's own Content-Security-Policy (connect-src 'self') forbids it from talking to anyone but this server — the disguised-first-party trick Floodlight flags on .gov pages, switched off here.
No IP addresses or user-agents. They are never written to a log or a database. The table below has no column that could hold one.
No fingerprint, no cross-site id. Nothing here can follow you to another site — or even recognize you between two visits to this one.
Do Not Track is honored. If your browser sends the DNT signal, this page records nothing at all — not even the aggregate count.

daylight, by its own measure

cleandaylight.watch, against Floodlight’s own checks

Third-party trackers0
Session replaynone
Analytics disguised as first-partynone
Cookies set0
Third-party network requests0
External fonts / CDNsself-hosted
Published privacy noticethis page

Verify it yourself: open dev tools › Network on any Daylight page, or read the response’s content-security-policy header. These are structural facts, not promises — the same checks Floodlight runs on federal pages, pointed at us.

what we count · live

The same lens, on .gov →

2,030visits · all time0referred by .gov871feed / API pullscounting since 2026-07-05 · aggregate only

most-visited pages

/1,455
/other405
/domain/:name73
/change/:id30
/registry10
/ledger9
/lookout8
/privacy8
/methods6
/watchlist6
/changelog5
/corrections4

where visitors come from

Direct / bookmarks342 · 17%
Referred by .gov0 · 0%
Search engines92 · 5%
Other sites1,596 · 79%

federal .gov referrers

Which government pages link here and send a click — read from the referrer, never from anyone’s IP or network. This cannot and does not tell us where a visitor is, or whether they browse from a government network; only which public .gov pages point to Daylight. A .gov with a strict referrer policy sends nothing, so this undercounts rather than over-claims.

No federal .gov page has linked to Daylight yet.

When one does — say an agency's privacy page cites a Floodlight scorecard — the referring domain appears here, by public apex. It is the one host we keep, because it is already public and newsworthy.

what we retain

This is the whole table. Every count above — page views, feed pulls, and API reads alike — is a sum over rows shaped exactly like this: a date, which page, a coarse referrer class, and a tally.

analytics_hits
  day        2026-07-03      UTC date
  path       /floodlight     which page — a route pattern, never a raw value
  ref_kind   gov             direct · gov · search · other
  ref_host   epa.gov         the .gov apex — kept only for federal referrers
  count      14              how many times

There is no row anywhere else that records your visit, and no column here — or in any other table — for an IP address, a user-agent, a cookie, or a session id. They are not dropped from this page; they were never collected. The referrer host is stored only when it is a public federal .gov domain, so a reporter can see which agencies link here — never a private or personal referrer.

Daylight runs on one small always-on server. If you want to help keep it lit, you can leave a tip — no tracking attached to that, either.