The Counterparty is a set of static files. There is nothing to sign into, no profile to build, and no analytics or advertising script on any page. This note describes every piece of client-side behaviour the site actually has, and it is short because there is not much of it.
di.theme, holding a light/dark preference. If it is absent — and nothing on this site writes it, so on this domain it normally is — the page follows your operating system's colour-scheme setting. The value never leaves your browser.
Three prices sit in the utility bar at the top of every page. They are the only dynamic thing on the site, so here is exactly how they arrive.
On page load the browser makes one same-origin request to /api/prices?ids=bitcoin,ethereum,solana. That path is a small function running on Cloudflare's edge. It carries no identifier of any kind: the only thing in the request that this site puts there is the list of coin ids, which is identical for every visitor.
The function answers from an edge cache with a 60-second lifetime, keyed on nothing but the origin and that id list. On a cache miss it calls the upstream price sources itself — CoinGecko first, and a DefiLlama endpoint as fallback if CoinGecko is unavailable — and caches the result only when it is non-empty, so a transient upstream failure does not stick. The response is plain JSON: a US-dollar price, a 24-hour change and a market cap per coin.
The practical point for you is that your browser never contacts a price provider. The upstream call is made server-side from the edge, once per minute for everyone, which is why the proxy exists at all: fetching directly from every visitor's browser got rate-limited by IP and leaked each reader's address to a third party. Requests to those upstream providers come from Cloudflare, not from you.
If the request fails or is blocked, the em-dashes in the utility bar simply stay. No price is ever baked into the HTML, and nothing else on the page depends on it.
Wire items link to the publishers that wrote them. Those links open externally and are marked nofollow noopener. Once you follow one you are on someone else's site, under their privacy policy — this masthead has no visibility into what happens there, but your browser will normally tell the destination which page you came from, as it would for any link on the web.
Each page carries a Google Search Console site-verification meta tag. It is an inert string that proves domain ownership to the search engine; it loads no script, sets no cookie and collects nothing from readers.
A distinction worth drawing. This site keeps no data about readers beyond the edge request logs described above — no mailing list, no profile, no contact form, nothing to export or delete because nothing is collected.
It does publish records about entities, and a small number of those — 61 of the 3,667 published records — describe people in their public professional capacity: founders, executives and officials named in public reporting. Those records are built from published sources, carry the citations they were verified against, and stay within what those sources state. Nothing on this site is compiled from private or non-public information.
If a published record is wrong, the remedy is the corrections process on the standards page: the underlying data is amended and every affected page regenerates. Note the limitation stated there — no corrections mailbox is published for this masthead yet, because none exists.
This page describes the site as built on 2026-07-27. It is a description of what the code does, not a statement of intent, so if the site's behaviour changes this page is expected to change with it. There is no notification list to announce that on, and this note does not pretend there is.