Privacy

This site is static HTML on a Cloudflare Worker. It sets no cookie, runs no analytics, and loads no third-party tracking script. The only personal data it ever handles is an email address you type into the newsletter form yourself.

Last verified: 2026-08-25

The short version

• No cookies are set by this site, for any purpose, including so-called essential ones. There is nothing to consent to and no banner to dismiss.
• No analytics product runs here. Not Google Analytics, not Plausible, not Fathom, not a self-hosted equivalent. We do not measure you.
• No advertising network, no retargeting pixel, no social embed, no comment widget, no chat widget, no A/B testing script.
• No account exists, so there is no profile, no password, and no login to breach.
• No wallet connection is ever requested. HoodTape will never ask for a private key, a seed phrase, or a signature.
• Your browser does load one font stylesheet from Google Fonts. That is the only request this site makes to a third party, and it is described below.

The newsletter form

The form on the home page sends one field to /subscribe on this same domain. That field is your email address. Nothing else is collected from the form, because nothing else is in it: there is no name field, no country field, no interest checkbox, and no hidden field.

The server stores three values against a subscription: the address, in lower case; the timestamp of the signup; and a short source label recording which page the form was on. The address is used as the storage key, so signing up twice overwrites the first record rather than creating a duplicate.

We do not enrich that address. We do not look it up in a data broker, we do not append a name or a company to it, and we do not check it against any other list. It is one string in one store.

Outgoing email carries no open-tracking pixel and no click-tracking redirect. If you click a link in the nightly tape, that click goes straight to the destination and we never learn about it. This costs us the ability to report an open rate, which we consider a reasonable price.

Unsubscribing and removal

Every message includes an unsubscribe link. Using it removes the record rather than flagging it as inactive, so the address is gone rather than retained in a suppression list. You can also write to us and ask for removal without having received a message first, and we will delete any matching record and confirm it.

If you want to know what we hold for a given address, ask from that address and we will tell you. In practice the answer will be the three values listed above, or nothing at all.

Server logs

This site runs on Cloudflare's network. Cloudflare processes requests on our behalf and, like any host or content delivery network, handles standard connection metadata such as IP address, request path, user agent, and response status in order to serve and protect the site. That processing is inherent to serving a web page over the internet; it is not an analytics choice we made, and we do not build profiles from it.

We enable Cloudflare's Worker observability so that we can see errors and diagnose a broken deployment. Those logs are operational, short-lived, and not used to study visitors. We do not export them, join them to anything, or sell them.

The web font

The stylesheet loads IBM Plex Sans from Google Fonts. That means your browser makes a request to fonts.googleapis.com and to fonts.gstatic.com, which is visible to Google in the ordinary way a font request is. We name it here because it is the single third-party request the site makes, and a privacy page that quietly omitted it would not be worth reading. Every element of the design has a real system font fallback, so blocking those hosts changes the typeface and breaks nothing.

Outbound links

Links to third-party tools go directly to those tools. There is no intermediate redirect on our side, so we do not learn which links you follow. Where a link is a referral link, that is declared in a public file, /refs.js, which you may read at any time; the substitution happens in your browser and sends no request to us. Once you arrive at a third-party site, that site's own privacy policy applies and ours stops. Many of the trading tools listed on this site do track their visitors extensively. That is their choice and it is outside our control, which is one more reason to read what we wrote about their custody models before you use them.

On-chain data

Our indexer reads the public Robinhood Chain ledger. Blockchain addresses and transactions are public by construction, and we do not attempt to attach a name, an email, an IP address, or any other real-world identity to an address. Wallet statistics published on this site are derived from public chain data only. We never combine chain data with subscriber data, and the two live in separate systems that do not talk to each other.

Children

This site is not directed at children and we do not knowingly collect data from anyone under the age required for consent in their jurisdiction.

Changes

If what we store or send changes, this page changes in the same release, and the last-verified date at the top moves. We do not make privacy changes quietly. The practical test is simple: if the Worker code or the client script starts handling something new, this page is wrong until it is updated, and that is treated as a defect.

For the wider question of how we choose what to publish and how referral relationships are handled, see the about page.