BurnStatus

Privacy

What BurnStatus receives, what it stores, and how to erase it.

What leaves your machine

Four numbers: your 5-hour and weekly usage percent, and when each resets. The plugin sends them to the BurnStatus API after your replies in Claude Code. It never sends prompts, code, file names or conversations.

The API turns the two percentages into your status text and keeps none of the four numbers. Until you connect, the plugin sends nothing at all.

What we store

In Cloudflare KV, one record per connected Slack user:

In a Cloudflare Durable Object (Pairing), one per pairing code, while you connect:

In a Cloudflare Durable Object (Stats), one for the whole service, counts and nothing else:

On the pairing and Slack sign-in paths, and when anyone reads /stats, our code hands your IP address to Cloudflare's rate limiter as its counter key (20 requests a minute). Our code does not store or log it.

The API sets two kinds of cookie, each a random value that ties a step to your browser. bs_pair is set when the pairing page opens and expires after 15 minutes. bs_state_ followed by the pairing code is set when you press Connect Slack, one per code; it expires when that code does, at most 15 minutes after the code was issued, and is cleared when Slack sends you back to the API. This site sets no cookies.

What we do with it

Who processes it

Cloudflare hosts this site and the API and holds everything listed above. Slack receives your status. There is no analytics processor: no analytics service, no advertising, no third-party script, no tracking cookie.

The API's Workers Logs keep no per-request entries, only what our code writes: the name and message of an error, never a token, a key or your limits.

How long we keep it

How to disconnect

  1. Run /burnstatus:disconnect. The API clears your Slack status, revokes the token with Slack (auth.revoke) and deletes your record. It still revokes and deletes if clearing fails. Your recent-update marker goes with the record; the weekly markers stay until they expire (16 weeks), naming a key that no longer exists and holding no data.
  2. Or remove BurnStatus in Slack, under Apps. When Slack notifies us (app_uninstalled or tokens_revoked), your record is deleted; if it does not, the record goes on your next update, when Slack refuses the token. Either way the token no longer works, so your last status stays until it expires, at most 3 hours after the update that set it, or until you clear it yourself.
  3. To pause instead, run /burnstatus:off. The connection stays and your status clears by itself within 3 hours of the last update.

Contact

Questions about your data, or a request to see or erase it: support@burnstatus.uk. You do not need to write to us to erase it: disconnecting deletes your record and everything in it. Only the weekly markers stay until they expire, and they name a key that no longer exists and hold no data.