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:
- Your Slack workspace id and Slack user id.
- Your Slack user token, encrypted with AES-256-GCM and a fresh random IV. Each encrypted token names the key version that sealed it. The keys are Cloudflare Worker secrets, never in KV or in git. When the key is rotated, your token is re-encrypted with the new one on your next update.
- A SHA-256 hash of the plugin key issued to you. The key itself stays on your machine; we cannot read it back.
- When you connected.
- A marker named by that hash, holding nothing else, that you had a successful update recently. Your first successful update each week sets it again, so it expires about a month (29 to 35 days) after your last successful update. It is normally deleted with your record.
- One marker for each ISO week in which you had a successful update, named by the week and that hash and holding nothing else. Each expires after 16 weeks. Disconnecting does not delete them: they then name a key that no longer exists and hold no data.
- A marker that expires after 60 seconds, so your status changes at most once a minute.
In a Cloudflare Durable Object (Pairing), one per pairing code, while you connect:
- The pairing session's state and poll timing, when it started, the city and country Cloudflare places your terminal's request in (nothing finer), a hash of the code your terminal holds, a count of failed attempts on it (form tokens our page never issued), from Slack's approval the name of your Slack workspace, and, until your terminal collects it, your new plugin key, encrypted. It is deleted when the code expires, 15 minutes after it was issued.
In a Cloudflare Durable Object (Stats), one for the whole service, counts and nothing else:
- Weekly counters, per ISO week: pairing codes issued, codes confirmed on the pairing page, approvals and refusals in Slack, and keys collected by a terminal, each counted as it happens.
- Counted from the KV markers above, at most every 10 minutes: connections with at least one successful update that week, and connections with a successful update in about the last month (29 to 35 days). A finished week's number is kept here when the week ends.
- Whole numbers only, each per ISO week (plus the running total and the time they were counted): no id, no key, no IP address. Anyone can read them at api.burnstatus.uk/stats.
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
- Set your Slack status, up to 100 characters plus an emoji, with users.profile.set. The one permission we ask Slack for is users.profile:write. We never read messages, channels or other people's profiles.
- Every status we set expires 3 hours after the update that set it: if no newer update arrives, Slack clears it.
- Your Slack token never leaves the API: not to the plugin, not to this site, not to anyone.
- Count, as above, how many people connect and use BurnStatus, and publish those totals at api.burnstatus.uk/stats.
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
- Your KV record: until you disconnect, remove BurnStatus in Slack, Slack reports the token no longer works, or the key version it was encrypted with is retired. Connecting again replaces it. The weekly markers named by its hash are not deleted with it: they stay until they expire, naming a key that no longer exists and holding no data.
- The once-a-minute marker: 60 seconds.
- A pairing session: until its code expires, 15 minutes after it was issued.
- The weekly counters: for as long as the service runs. They hold nothing about you.
- The recent-update marker: about a month (29 to 35 days) after your last successful update; normally deleted with your record before that. The weekly markers: 16 weeks each, whether or not you disconnect.
- Error logs: at most 7 days (3 days on the Workers Free plan), as Cloudflare keeps them.
How to disconnect
- 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.
- 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.
- 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.