Security & privacy
To read your bills, Burnstack needs admin or billing keys. Those are powerful, so Burnstack is built so they never leave your computer.
Where your keys live
- Keys are stored only in your computer's keychain: the macOS Keychain or the Windows Credential Manager.
- They're never written to the database, config files or logs. After you paste a key, the app never shows it again.
- Error messages from vendors are scrubbed of anything that looks like a key before they're shown or logged.
- An automated test makes a fake vendor echo its key everywhere it can, then checks the key appears nowhere in the database files or logs.
Where your data lives
Spend history, resources and alerts are kept in a small SQLite database on your computer. Vendor responses are stripped of credential-like fields before they're saved. Invoices you import, and the copies kept as evidence, stay in the same data folder.
Company card feeds (new in 0.7.0) read the card's transactions on your computer and save only the dev, SaaS and AI charges; every other charge is dropped in memory and never written to disk. Revenue (new in 0.7.0) stays in the same database: customer ids are stored only as a one-way hash, and AI apps (MCP) don't see revenue, profit or loss alerts.
Every network call
No spend data ever leaves your computer. The only way any of it can is one you switch on yourself: an AI app you connect reads it and sends it to that app's AI provider (AI apps, below). This is everything the app and this website send, and to whom:
The diagram in words
- On your computer: the Burnstack app, its SQLite database (your spend history) and the OS keychain (your API keys). Spend data and keys stay there.
- App → your vendors' billing APIs: read-only HTTPS requests with the key from your keychain. Back: your costs and usage.
- App → update server: GETs for
latest.jsonand the signed price file (connectors-v1.json), with no ID and none of your data. Can be turned off. - Browser → this website's download page: your email, the platform and a Turnstile check. Free download only.
- Enterprise only: app → account server: the signed entitlement (account, plan, seats, device id), a random device id and the app version; re-checked weekly with a 30-day offline grace. Free users never contact it. Details.
- Your vendors (the app). Read-only requests to each vendor's own billing and usage API, over HTTPS with certificate checks, using the key from your computer's keychain (macOS Keychain or Windows Credential Manager). Only vendors you add, and only their own API.
- The update check (the app, new in 0.5.0). One GET request for a public file (
latest.json) on launch and every few hours. The request carries no account, no ID and none of your data. The server only sees what any web request shows: your IP address and that someone checked. Updates are signed; the app refuses any update not signed with Burnstack's key. You can turn automatic checks off in Settings → Update automatically; then Burnstack checks only when you ask it to. - The price and vendor settings file (the app, new in 0.8.0). With automatic updates on, one GET a day for a public, signed file (
connectors-v1.jsonand its signature) from the same server, with no account, no ID and none of your data. It holds list prices and a few vendor API settings, and can pause a vendor whose API changed. The app checks its Ed25519 signature, never takes an older file than it has, and keeps the last good one offline. It can't change where your keys go: each vendor's API address is built into the app, and the file can only adjust the path on that same address. - The download page (this website, in your browser). To download, you enter your email. Your browser sends the email and the platform you picked to our download server, which records them with the time; Cloudflare Turnstile checks you're a person. The app is not involved. What's kept and for how long.
- Exchange rates (the app, revenue tracking, new in 0.7.0). Only once a sale in a second currency appears, Burnstack downloads the European Central Bank's public reference rates. The request carries nothing about you or your revenue.
- Enterprise and revenue activation (the app and your browser, only if you activate). Cost tracking never contacts the account server; nothing below happens until you click Activate… (Enterprise) or Activate free (revenue tracking, new in 0.7.0) in Burnstack. The free revenue license is issued the same way, lasts six months and is then checked offline only: no weekly check.
- Activating: Burnstack opens
/account/in your browser with a random one-time value. You sign in there and click Activate this computer; your browser sends the computer name you type and whether it's a Mac or Windows. The account server answers with a one-time code (valid 5 minutes), which your browser hands to Burnstack. Burnstack then sends the code, a random device id it made for this purpose (never a hardware serial) and its version number, and gets back a signed entitlement: your account id, plan, number of seats, the device id and its dates. Burnstack checks the signature on your computer and keeps the entitlement in your keychain. - Once a week: Burnstack sends the entitlement and its version number and gets a fresh one. If the server can't be reached, Enterprise keeps working for 30 days from the last successful check, then Burnstack switches to the free version. Your data stays as it is.
- Deactivating: from
/account/, or Deactivate this computer in Burnstack, which sends the entitlement once so the seat is freed. - Never sent: your API keys, spend data, vendors, file names or anything else from the app.
- Activating: Burnstack opens
No account for cost tracking, and no telemetry. No Burnstack server ever receives your keys or spend data. Like any web request, each of these shows the server your IP address.
Reporting a problem New in 0.11.0
Because Burnstack sends nothing about itself, we only learn that a vendor stopped syncing when you tell us. Report a problem… at the bottom of the sidebar, and Report this next to a connector's sync error, open a draft email to support@burnstack.app in your own mail app. You see exactly what it contains first: the Burnstack version, your system and, unless you untick the box, your vendors' names and their sync errors. Never keys, account names or amounts. Nothing is sent unless you send the email yourself.
AI apps (MCP)
Burnstack includes an optional MCP server so AI apps such as Claude or Cursor can read your spend data (new in 0.3.0). It's off until you turn it on in Settings.
- It opens the database read-only and can't sync, change settings or touch your vendors.
- It never opens the keychain, so it never sees your API keys.
- It has no network code: the AI app starts it on your computer and talks to it directly.
- It can be limited to chosen vendors or applications; anything outside the limit is left out before an answer leaves it.
What leaves your computer: when an AI app reads Burnstack data, that data goes to the app's AI provider as part of the conversation, along with your questions. Turn it on only for apps whose provider you trust with your spend data.
Imported invoices New in 0.4.0
- PDF and CSV invoices you import are read on your computer by fixed rules; no AI model and no server reads them.
- Burnstack keeps a copy of each file as evidence in its data folder on your computer. Nothing is uploaded.
- Nothing counts until you approve it in the review queue.
- The watched folder is off by default. When you turn it on, Burnstack only reads the folder you name and moves files it has read into a Processed folder beside it.
- AI apps can submit charges for review only with a second setting, off by default. The MCP server still never writes to your data: it leaves a request file that the app checks again and puts in the review queue, and those batches are never approved automatically.
Read-only by design
Burnstack only calls billing, usage and listing endpoints; it never changes, pauses or deletes anything. Where a vendor offers scoped keys (GitHub's fine-grained tokens, for example), the setup steps ask for the narrowest one that can read billing.
Some vendors' billing keys can do more than read: an Anthropic or OpenAI Admin key, a Vercel team token, an OpenRouter or xAI management key, or a Render, Together AI or Runway API key also has write access. That's exactly why Burnstack keeps them in your keychain and never sends them anywhere but the vendor itself.
Report a vulnerability
Found a security problem in the app, this website or its download and account servers? Email security@burnstack.app with what you found and how to reproduce it. Please give us a chance to fix it before you publish, and don't access other people's data or run denial-of-service tests. Machine-readable: security.txt.
Why this matters
Hosted cost tools need your keys on their servers. In October 2026 a developer tool's breach exposed users' stored AI keys, with reported losses of hundreds to thousands of dollars per user (Dealroom). A tool that never sends your keys to its servers can't leak them from there.
Start watching back.
Five minutes to connect your first vendor. Free for Mac, forever, and every byte stays yours.