Terms of Use

These Terms of Use cover the Burnstate app for Mac and its widgets, the website burnstate.dev and the burn report pages on it (together, the “Services”). They are an agreement between you and the operator of the part you use (“Burnstate”, “we”, “us”):

• The Setapp edition, the website and the waitlist: Yozhef Serhiiovych Hisem, an individual based in Chop, Zakarpattia Oblast, Ukraine.
• The direct edition and the Mac App Store edition: Serhii Khvala, an individual based in Chortkiv, Ternopil Oblast, Ukraine.

By installing or using the Services, you agree to these Terms and to our Privacy Policy. If you don’t agree, please don’t use the Services.

You must be at least 18, or 13 to 17 with a parent or guardian’s permission. If you use Burnstate for a company, you confirm that you can accept these Terms on its behalf.

Getting Burnstate. Burnstate comes in three editions: the direct edition from burnstate.dev, the Setapp edition and the Mac App Store edition. Burnstate has no account of its own.

• Direct: you download the direct edition from burnstate.dev and buy its license through Creem, once or as a subscription. Creem’s merchant of record, Armitage Labs OÜ (registry code 16977866, Rotermanni 14, Tallinn 10111, Estonia), sells you the license, charges you, renews a subscription, collects tax and issues your receipt and invoice in its own name, under the Creem Buyer Terms. Section 3 covers the license itself.
• Setapp: Setapp, operated by MacPaw Way Ltd., handles your subscription, payments, trials and refunds under the Setapp Terms of Use.
• Mac App Store: Apple handles your purchase, payment and refunds under the Apple Media Services Terms and Conditions. Your license to the app is Apple’s Licensed Application End User License Agreement, and these Terms apply alongside it. Apple isn’t a party to these Terms and isn’t responsible for the app or its support.

Connecting a provider. You choose which providers to connect in the app, and you can pause or disconnect each one at any time. When you connect a provider, Burnstate uses the sign-in that provider’s own tool already keeps on your Mac. If there isn’t one, you sign in through Burnstate:

• Claude: Claude Code’s login, from the macOS Keychain or ~/.claude/.credentials.json. The sign in button runs Claude Code’s own login, or opens the Claude app if Claude Code isn’t installed. If Claude Code’s login is missing, expired or rate limited, Burnstate reads your limits from claude.ai with the claude.ai session in the Claude app or your browser. The Mac App Store edition uses only Claude Code’s existing login, so sign in with Claude Code in your terminal first
• Codex: the Codex CLI’s ChatGPT login, in ~/.codex/auth.json. Without it, you sign in to ChatGPT through Burnstate by entering the code it shows at auth.openai.com
• Cursor: the Cursor app’s login, from its local database. Without it, you sign in on cursor.com in your browser
• Vercel AI Gateway: the Vercel CLI’s login and current team. Without it, you paste an AI Gateway API key, which Burnstate checks once before saving it
• Setapp AI, in the Setapp edition: your credit balance, through the Setapp app

Burnstate uses these sign-ins only to ask each provider for your usage. It doesn’t change your password, plan or billing. It never refreshes or rewrites a login that belongs to Claude Code, the Codex CLI, the Cursor app or the Vercel CLI. When Claude Code’s token expires, the direct and Setapp editions briefly run Claude Code so it renews its own login, as described below. When the Codex CLI’s, the Cursor app’s or the Vercel CLI’s login expires, sign in again in that tool or in Burnstate.

Burnstate keeps the sign-ins you make through it, and the API key you paste, in its own items in the macOS Keychain. It renews those sign-ins itself, uses them instead of a tool’s login when you have both, and deletes them when you disconnect the provider.

Provider terms. Your use of those accounts is governed by each provider’s own terms. Burnstate is not affiliated with or endorsed by Anthropic, OpenAI, Anysphere or Vercel. Some of the interfaces Burnstate reads and signs in with aren’t documented public APIs, so a provider can change or close them at any time, and a provider may stop showing data in Burnstate without notice.

This section applies only to the direct edition. Setapp and Apple license the other two editions.

Your license. The direct edition needs a license key from the first time you open it. You can buy a license once and keep it for good, or subscribe to one by the month or by the year. Either way it gives you a personal license to use the direct edition. Creem emails you the license key and a link to its customer portal.

Subscriptions. A subscription renews at the end of each month or year, at the price shown when you subscribed, until you cancel. Creem charges the payment method you gave at checkout. You can cancel at any time in Creem’s customer portal, which Settings › License opens. After you cancel, you aren’t charged again and your key keeps working until the end of the period you paid for. Then it stops. If a renewal payment fails, Creem tries again. If it still hasn’t gone through a few days after the period ended, Burnstate locks until it does. Your key stays on your Mac, and Burnstate unlocks by itself once the payment goes through. If we change the price of your subscription, we’ll email you before the renewal it applies to, so you can cancel first.

Your license size. Licenses come for 1, 2 or 3 Macs, each a separate purchase or subscription. You can activate your key on as many Macs as your license covers, if you own or control them. To free a seat, deactivate the key on a Mac in Settings › License. Don’t share your key, publish it or resell it.

License checks. The direct edition checks your key with burnstate.dev when you activate it, about once a day while it’s activated, and when you deactivate it. Our Privacy Policy explains what it sends. If the check can’t reach us, Burnstate keeps working and tries again later. A subscription’s key works without the check until a few days after the period you paid for.

Revoking a key. We can revoke a key that was refunded, charged back or shared. Burnstate then asks for a new key on every Mac that used it.

Refunds. If Burnstate isn’t right for you, email support@burnstate.dev with your order number within 14 days of buying a one-time license, or within 14 days of the first payment of a subscription, and we’ll refund you. Creem processes the refund, and the refunded key stops working. Renewal payments aren’t refunded, unless the law where you live requires it. To avoid a renewal, cancel before it.

Right of withdrawal. If you’re a consumer in the EU or UK, you normally have 14 days to withdraw from a purchase or a new subscription. By starting the download and activating a key, you ask for immediate delivery of the digital content and acknowledge that you lose that right of withdrawal. This doesn’t affect the refund we offer above.

Reads local logs. Burnstate reads the session logs Claude Code and Codex keep on your Mac, in ~/.claude (and any other Claude Code config folder) and ~/.codex, to count tokens, estimate cost and list your sessions. It doesn’t change them.

Three editions. The direct and Setapp editions do everything below. The Mac App Store edition runs inside the macOS App Sandbox and reads your home folder only after you allow it in the macOS open panel. It doesn’t run Claude Code, read your claude.ai session, or check and update your coding tools, so those three paragraphs apply to the direct and Setapp editions only.

Runs Claude Code to sign in and renew its login. When you sign in to Claude Code, Burnstate runs claude auth login --claudeai in a hidden terminal, and you finish in your browser. When Claude Code’s token has expired, Burnstate starts Claude Code in a hidden terminal for up to 10 seconds and types /status, so Claude Code renews its own login. That run uses a temporary folder and skips your settings, hooks and MCP servers. The first time, Burnstate answers Claude Code’s prompt to trust that folder. Burnstate does this at most once every 30 minutes.

Reads your claude.ai session. If Claude Code has no working login, Burnstate looks for the claude.ai session cookie in the Claude app, then in your browsers, and uses it only to read your limits from claude.ai. Reading a browser’s cookies can show a macOS Keychain prompt. Burnstate lets that prompt appear only when you connect, sign in or refresh, never in the background.

Adds a hook to Claude Code. Each time it starts, Burnstate makes sure one hook, for Claude Code’s PermissionRequest event, is in the settings.json of every Claude Code config folder it finds. The hook hands Claude Code’s permission prompts and questions to Burnstate over a local connection on your Mac, protected by a token unique to your install, so you can answer them from a card. Your terminal keeps its own prompt, and whichever you answer first wins. If Burnstate isn’t running, the hook does nothing and Claude Code works as before.

Rewrites settings.json when it adds the hook. Your settings are kept, but the file is saved again with its own formatting and its keys in alphabetical order. A file that already has the hook is left untouched, and so is one Burnstate can’t read.

Answers one prompt at a time. An answer from a card applies only to that one request. Burnstate never adds “always allow” rules or changes your Claude Code permission settings.

Checks and updates your coding tools. To tell you when Claude Code or Codex has a new version, Burnstate runs each tool’s --version and reads the PATH from your login shell to find it. When you tap update, it runs that tool’s own updater, such as npm, pnpm, bun, Homebrew or the tool’s built-in one, with your user rights.

Opens at login only if you ask. Burnstate adds itself to your login items only when you turn that on, and you can turn it off in its settings or in macOS.

Moves transcripts to the Trash when you ask. Archiving a session only hides it in Burnstate. Deleting one moves its transcript files to the macOS Trash.

Your decisions. Allowing a command, an edit or a tool call from a card is the same as allowing it in the terminal. You are responsible for what you approve, for what Claude Code then does on your Mac, and for the tool updates and deletions you start.

Limits and balances come from each provider, about every five minutes, and are shown as the provider reports them. They can lag behind the provider’s own dashboard.

Tokens and cost for Claude Code and Codex are computed from your local logs at published per-token API prices. Cost shows what the work would cost at API list prices, not what you were billed. Subscriptions aren’t billed per token. Cursor’s cost is taken as Cursor reports it.

Pace and forecasts, such as when you’d run out at your current pace, are projections, not promises.

Don’t rely on Burnstate as your only record for billing, budgets or decisions where a wrong number would cost you. Your provider’s own dashboard is the source of truth.

A burn report is built on your Mac and opened as a burnstate.dev link with the numbers packed after the #. Anyone you give the link to can see the report, and so can any app you paste it into. Share only what you’re happy to show.

You choose the handle in a report’s link, and we don’t verify it or the numbers. Don’t use a handle to pose as someone else, and don’t present a report you edited as someone’s real usage.

Burnstate can answer a few questions with AI: how to spend less on your AI tools, what’s new in Claude Code and Codex, and a summary of a coding session. It asks only when you tap for an answer or, if you turn on summaries of ended sessions, when a session ends.

In the Setapp edition, answers come from Setapp AI, operated by MacPaw Way Ltd., and spend your Setapp AI credits. Setapp passes each question to the model you pick in settings, from Anthropic or OpenAI, under Setapp’s terms. On Macs that support it, you can pick Apple Intelligence instead, which answers on your Mac.

In the direct edition, answers come from Claude Code by default. Burnstate runs your own Claude Code on your Mac with the model you pick in settings (Haiku, Sonnet or Opus), without tools and without saving a session. Each question goes to Anthropic through Claude Code’s login, under Anthropic’s terms, and counts against your Claude plan or is billed to you like any other Claude Code use. On Macs that support it, you can pick Apple Intelligence instead, which answers on your Mac.

The Mac App Store edition answers only with Apple Intelligence on your Mac, and offers how to spend less and session summaries.

AI answers can be wrong or out of date. Check them before you act on them, especially advice about plans and money. They aren’t financial, legal or other professional advice.

Don’t use Burnstate to:

• break the law or the terms of Anthropic, OpenAI, Cursor, Vercel, Setapp or Creem;
• get around a provider’s limits, or share or resell access to an account;
• reverse engineer, modify or redistribute the app, or get around Setapp’s or Apple’s licensing;
• get around the direct edition’s license check, or share, publish or resell a license key;
• spread scams, malware or deceptive content through burn report links.

If you break these rules, we may suspend your access to the Services, together with Setapp where needed. Where we reasonably can, we’ll tell you why first. To dispute our decision, write to support@burnstate.dev.

Our property. The Burnstate app, website, brand, design and software belong to us or our licensors. We give you a personal, revocable, non-exclusive, non-transferable license to use the app on Macs you own or control, in line with these Terms and your direct license, your Setapp subscription or the Mac App Store’s Usage Rules.

Third-party services. Burnstate works with services we don’t control: Anthropic, OpenAI, Anysphere, Vercel, Setapp, Apple, Creem, GitHub and the npm registry. Their terms apply to your use of them. We aren’t responsible for their availability, for changes to their interfaces, or for what they do with your accounts.

Changes to the Services. We’re a small team, and Burnstate keeps changing, often because a provider changed something. We may add, change or remove features and providers.

Ending the agreement. You can stop using Burnstate at any time by quitting and removing the app. Removing the app doesn’t cancel a direct subscription: cancel it in Creem’s customer portal. Setapp manages your Setapp subscription, and Apple your Mac App Store purchase. We may end your access if you break these Terms, if the law requires it, or if we shut down the Services. If we shut down the Services, you can keep using the version of the direct edition you have. We may revoke a direct license key that was refunded, charged back or shared, as Section 3 describes. Sections 5, 10 and 11 survive termination.

No warranties. The Services are provided “as is” and “as available”. To the extent the law allows, we make no warranties of any kind, including merchantability, fitness for a particular purpose, non-infringement, accuracy of usage numbers and estimates, and uninterrupted or error-free operation.

Limits on our liability. To the extent the law allows, we aren’t liable for indirect, incidental, special or consequential damages. That includes lost profits, data or work, running out of a limit or paying for extra usage, actions you approve from a card, tool updates you start, and actions a provider takes on your account. Our total liability for all claims about the Services is limited to the greater of USD 50 and the amount Burnstate received for your use in the 12 months before the claim.

Nothing in these Terms limits liability that can’t be limited by law, such as for fraud, gross negligence, or death or personal injury caused by negligence. It also doesn’t limit your statutory rights as a consumer.

Indemnity. You agree to cover our reasonable costs, including legal fees, if a third party makes a claim against us because you broke these Terms. This doesn’t apply where the claim is caused by our fault.

Governing law. These Terms are governed by the laws of Ukraine. If you’re a consumer in the EU or UK, you also keep the protection of the mandatory laws of your country, and you can bring a claim in the courts where you live.

Disputes. Before going to court, please email us. We’ll try to resolve the issue informally within 30 days.

Changes to these Terms. We may update these Terms. We’ll post the new version here with a new effective date. If the changes are significant, we’ll post them at least 14 days in advance and, where we can, tell you in the app. If you keep using Burnstate after that, you accept the new Terms.

General. These Terms and the Privacy Policy are the whole agreement between us about the Services. If one part is found unenforceable, the rest still applies. If we don’t enforce a right, we haven’t waived it. You may not transfer these Terms without our consent. We may transfer them to a successor of Burnstate. You may not use the Services where US or EU sanctions prohibit it. If a translation of these Terms differs from the English version, the English version applies.

Setapp edition, website and waitlist: Yozhef Serhiiovych Hisem (individual), Chop, Zakarpattia Oblast, Ukraine

Direct edition and Mac App Store edition: Serhii Khvala (individual), Chortkiv, Ternopil Oblast, Ukraine

Email for both: support@burnstate.dev