Your email is used for one thing

The short version

• Your email address is used to send you the newsletter. Nothing else.
• It is never sold, rented, or shared for anyone else’s marketing.
• There are no analytics, no tracking pixels, and no advertising cookies.
• You can leave in one click, and your address is then unusable for sending.
• You can have your record deleted outright by asking.

Reading the site

You can read every post, course and weekly issue without giving anything at all. There is no signup wall and no account.

The site sets no cookies, runs no analytics, and stores nothing in your browser. There is no Google Analytics, no Meta pixel, no session tracking, and no third-party advertising script anywhere on the site. Search runs entirely in your own browser — what you type into it is never sent anywhere.

Cloudflare, which hosts the site, keeps standard server request logs as any host does. Nothing in this application reads or records your IP address.

If you subscribe

Subscribing is the only point at which the site asks you for anything. Here is everything stored, and why each piece exists:

Your email address

It is the thing the newsletter is sent to. Nothing else about you is asked for, and there is no name field, no company field, and no profile.

Whether you confirmed

Signup is double opt-in. Until you click the link in the confirmation email your address is marked pending and receives nothing further.

Two random tokens

One confirms the subscription, one unsubscribes it. They exist so those links work without you ever needing an account or a password.

Which page you signed up from

A single word such as "landing" or "post" — enough to know which parts of the site people find worth subscribing from. It is not a browsing history.

Timestamps

When you subscribed, confirmed, and unsubscribed. Also a short-lived counter of recent signup attempts, which is what stops somebody spamming confirmation emails at an address that is not theirs.

Which issues were sent to you

A delivery log, so an interrupted send can resume without emailing you the same issue twice.

That is the complete list. There is no open rate tracking, no click tracking, and no pixel in the emails — which means nobody here knows whether you opened an issue, and that is fine.

What it is never used for

• Selling, renting, or trading the list. It has never happened and will not.
• Sponsored or advertising email. The newsletter carries neither.
• Any mail other than the weekly roundup and the one confirmation message.
• Building an advertising or behavioural profile.
• Enriching your address against other data sources.

Who else sees it

Only what is structurally necessary, and only these:

CloudflareHosting and database

The site runs on Cloudflare Workers and the subscriber list lives in Cloudflare D1. Standard request logs are handled by Cloudflare under their own terms.

ResendEmail delivery

Receives your address for the sole purpose of delivering the message. They are the postal service, not a marketing partner.

GitHubComments only

Comment threads are GitHub Discussions embedded via giscus. That embed loads only when you open a page carrying it, and commenting requires a GitHub account governed by GitHub’s own privacy policy. Reading a page never sends anything to GitHub about you.

Leaving

Every email carries a one-click unsubscribe link in its footer, and theList-Unsubscribe header so your mail client can offer its own button. Both work without logging in and without a confirmation step designed to talk you out of it.

Unsubscribing marks your record so that nothing further can be sent to it. If you would rather the row were deleted entirely, emailhello@threatnotes.org from the subscribed address and it will be removed. You do not have to give a reason.

How long it is kept

A confirmed address is kept while you are subscribed. An unsubscribed record is kept only so the same address is not accidentally re-added by a stale form, and is deleted on request. An address that never completes double opt-in stops being useful once its confirmation link is stale and is periodically cleared out.

If something goes wrong

If subscriber data were ever exposed, it would be disclosed here and by email to everyone affected, with what happened and when — not buried in a changelog. A security publication that handled its own incident quietly would not be worth reading.

Found a security problem with this site? Please report it tohello@threatnotes.org. Good-faith reports are welcome and will not be met with legal threats.

Changes to this policy

Material changes will be dated at the top of this page. If a change ever affected how your email address is used, it would be announced in the newsletter rather than made quietly — that is the whole point of the first sentence on this page.

Contact

Questions about any of this: hello@threatnotes.org.