threatdeck
Live 13:15 UTC ·

TrustLast updated 2026-11-10

Privacy

ThreatDeck has no accounts, no ads and no tracking cookies. Most of the site works without sending us anything about you. When you use a feature that needs storage (alerts, fleet view, API keys, business enquiries, the email newsletter), we keep only what that feature needs, and we store tokens and IP addresses only as hashes.

ThreatDeck is operated independently. Questions or requests: hello@threatdeck.net.

What stays in your browser

Your Following list, saved stories, playbook checklists, learning progress and quiz scores, coverage notes, theme, the time of your last visit and the manage tokens for your alert channel and fleet are kept in your browser's local storage. They are not sent to us. The exceptions are things you do on purpose: a share link with ?stack= puts your Following list in the URL, and a feature you use sends its token to the API.

ThreatDeck sets no cookies of its own. Fonts and scripts are served from threatdeck.net.

What we store when you use a feature

FeatureWhat is storedHow long
Team alerts The incoming webhook URL (needed to deliver; the API only ever shows it shortened), channel name, follow keys, delivery mode and importance, status, last delivery error, ids of recently delivered stories, a linked fleet (if you link one), timestamps. The manage token is stored only as a SHA-256 hash. A hash of the creating IP address (see below). Until you delete the channel. A channel whose webhook stops working (HTTP 404/410, or 5 failures in a row) is disabled but kept until deleted.
Fleet view Fleet name; admin and upload tokens as SHA-256 hashes only. Per machine: a hash of the random machine id the CLI generates, an optional label you choose, OS family, CLI version, AI tool slugs and versions, MCP client, transport, package id and public remote host, and finding counts by rule. Never paths, usernames, hostnames, server names, commands, arguments, environment or header values, config contents or transcripts: the server rejects any other field. A hash of the creating IP address. Until you delete the fleet (this deletes every machine). A machine that has not uploaded for 30 days drops off the dashboard and is deleted the next time the fleet uploads or its dashboard is opened.
API keys Optional key name, plan, creation time, the UTC date the key was last used, revocation time. The key itself only as a SHA-256 hash. A hash of the creating IP address. Until you revoke the key. A revoked key's record is kept so the key keeps being rejected.
Business enquiries Your email address, and what you choose to tell us: company, team size, AI tools in use, use case. Which page you wrote from, the time you sent it, a hash of your IP address. Until you ask us to delete it, or we no longer need it to answer your enquiry. Used only to reply to you; it does not subscribe you to the newsletter.
Daily deck email Your email address and subscription status, in Listmonk on the operator's server. Double opt-in: nothing is sent until you confirm. Until you unsubscribe (link in every email) or ask us to delete it.
Abuse limits A hash of your IP address as the key for rate limits on the API and MCP server, and in a log of create attempts (alerts, fleets, API keys, business enquiries). Rate-limit counters last about a minute. Create-attempt entries are deleted after about 25 hours.

About hashed IP addresses

Where this page says "a hash of your IP address", we store the first 128 bits of a SHA-256 hash of the address with a fixed prefix, never the address itself. That is pseudonymous, not anonymous: we cannot read the address back, but someone holding the database could test guesses. We use it only to limit abuse.

What we process but do not keep

  • Requests. Cloudflare serves the site and API, so it sees your IP address, user agent and the URL you request. Cloudflare may keep operational logs under its own policy, and Cloudflare Workers Logs (which we use for debugging) keep request metadata for API calls, such as URL and method, for a few days. Our own log lines contain errors and alert delivery counts, not IP addresses.
  • Analytics. If enabled, we use Cloudflare Web Analytics: a cookie-free script that counts page views without identifying visitors. Nothing else measures you.
  • Anti-bot check. The newsletter form may use Cloudflare Turnstile, which checks your browser before the sign-up is sent.
  • Publisher images. Story pages can show an image from the original publisher. Your browser loads it straight from the publisher, which then sees your IP address; we send no referrer.
  • Scanner. threatdeck scan runs locally. Without --upload it sends only plain lookups (tool slug and version, MCP package id, public remote endpoint, GitHub repo name) with no machine id; --offline sends nothing. Details on /scan/ and /fleet/.

Who processes data for us

ProviderWhat forVisitor data involved
CloudflareHosting (Workers, static assets), database (D1), rate limiting, backups (R2), Turnstile, Web Analytics if enabledEverything in the table above; requests
The operator's serverNews pipeline, newsletter (Listmonk on Postgres)Newsletter email addresses
Email delivery provider (SMTP relay)Sending newsletter and confirmation emailsNewsletter email addresses
AnthropicSummarising and classifying public news articlesNone: only public article text is sent
Slack, Microsoft, DiscordDelivering alerts to the webhook you gave usStory titles, one-liners and links, sent to your own channel

Public sources (CISA, NVD, GitHub, OSV.dev, the MCP registry, publisher feeds) are read by the pipeline; no visitor data is sent to them.

Backups

The operator's database (pipeline data and newsletter subscribers) is backed up daily to Cloudflare R2; the last 30 backups are kept. Cloudflare D1 keeps its own point-in-time recovery history, so a deleted row can remain recoverable for up to 30 days.

Your choices

  • Delete an alert channel on /alerts/ with its manage token.
  • Delete a fleet or single machines on /fleet/ with the admin token.
  • Revoke an API key on /developers/.
  • Unsubscribe from the newsletter with the link in any email.
  • Ask for a copy or deletion of a business enquiry or newsletter entry by email from that address: hello@threatdeck.net.

Because there are no accounts, we can only find a record you can point to: an email address, or a token. We cannot recover lost tokens.

ThreatDeck does not sell or rent data, does not show ads and does not share data with anyone not listed above, unless the law requires it.

Changes

When what we collect changes, this page changes first, with a new date at the top.

Following

Follow the vendors, products, AI tools, techniques and actors you care about. Matching stories, CVEs and exploited bugs are marked, a Following tab appears in the feed, and returning visits show what changed. Saved only in this browser.

Presets

Get updates

A personal RSS feed of new stories on everything you follow. Paste it into any feed reader, Slack or Teams RSS app.