Privacy policy
The short version: the Burnstack app collects nothing, and your API keys, costs and revenue never leave your computer. This website keeps your email if you download the app or make an account, and only what it needs for that.
Who we are
Burnstack is made by Guy Dahan, trading as Burnstack, who is the controller of the personal data described here: "we" and "us" on this page.
- Privacy questions and requests: privacy@burnstack.app
- Postal address: available on request at privacy@burnstack.app
This policy covers the website burnstack.app, the free download, Burnstack accounts and the licenses they issue, and what the Burnstack app sends over the network. We don't sell personal data, share it for advertising, or use it to train AI models.
This website
- Server logs. Our host, Vercel, records standard request logs: IP address, time, the page asked for, and your browser's user agent. They're used to keep the site running and secure.
- Page counts. We count page views with Vercel Web Analytics. It sets no cookies, doesn't follow you to other sites and doesn't identify you: it records the page, the site that linked to it, and your country, browser, operating system and device type, and we only ever see totals. Its script loads from this site's own address.
- Nothing else. No advertising, no tracking pixels, no social media scripts. Pages load only this site's own files (fonts included), with three exceptions: the download page loads Cloudflare Turnstile once you start on the email form, the account page talks to Supabase to sign you in, and the checkout page (/pay/), which you reach only from a payment link, loads Paddle's checkout.
Downloading the app
To download Burnstack you enter your email address. There's no account and no password.
- What we keep: your email address, the platform you picked (Mac or Windows), when you first and last downloaded and how many times, whether the Turnstile check passed, and a keyed hash of your browser's user-agent string (a one-way code that can't be turned back into the string; it helps us spot automated abuse).
- What we don't keep: your IP address. It's used only in passing: Cloudflare Turnstile receives it to check you're a person, and our server turns it into a one-way code to limit how many links one network can request in an hour. Those codes are deleted after two days.
- Why: to give you the download link, to keep bots out, and to email you about new releases and important fixes, such as security updates. You can stop them any time: just email us. The app itself never sees your email.
- How long: until you ask us to delete it, and at most 24 months after your last download, when it's deleted automatically.
- Deleting it: email privacy@burnstack.app from that address. Deleting your Burnstack account doesn't delete it; ask us separately.
The installers are stored in Supabase, and the link you get works for 60 seconds.
Your Burnstack account
An account is needed only for the free revenue tracking license (beta) and for Burnstack Enterprise. Cost tracking and the free download never need one. You sign in with a link we email you; there's no password. You manage the account on your account page, where you can download your data, sign out of every device, or delete the account.
- What we keep: your email address, when the account was created and when you last signed in. Supabase Auth, which runs sign-in for us, also keeps a security log of sign-ins and sign-in emails, with IP addresses and browser details.
- Your plan: for Enterprise, the plan, number of computers (seats), its status and end date, and a note we may add, such as an invoice number.
- Why: to sign you in, to issue and check your licenses, to manage your plan, and to keep accounts secure.
- How long: until you delete the account. Delete my account on the account page removes your account, its sign-in, its plan record, its computers and licenses, at once. If an Enterprise plan is still running, you confirm that deleting ends it. The download record for the same email is kept until you ask us to delete it, or 24 months after your last download.
Activated computers and licenses
Only people who activate the app send anything here: Enterprise customers, and anyone who turns on revenue tracking with the free beta license. Cost tracking never contacts the account server. How activation works.
- Each Enterprise computer: the name you gave it, Mac or Windows, a random device id the app made (never a hardware serial), the Burnstack version, when it was activated and when it last checked in. You see the same list on your account page.
- Each free revenue license: the computer's name, Mac or Windows, the random device id, the Burnstack version, your account's email (it's also in the signed license, so the app can show whose it is), and when the license was issued, renewed and ends.
- What the app sends: when activating, a one-time code, the device id and its version. Enterprise also checks once a week, sending the signed entitlement we issued (account id, plan, seats, device id and dates) and its version. The free license is never checked again. The app never sends your API keys, costs, revenue or anything else from it.
- How long: one-time codes are deleted after a day (they stop working after 5 minutes, and we keep only a one-way hash of each). A deactivated computer is deleted 30 days after you deactivate it. Everything else stays until you delete the account.
Paying for Enterprise, and sales records
Burnstack Enterprise is paid through Paddle.com, our reseller and Merchant of Record. You pay Paddle, on Paddle's checkout: your card or bank details go to Paddle only, and we never see or store them.
- What Paddle tells our server about a payment: that it was paid, renewed, fell behind or was canceled; the amount, currency and billing period; and Paddle's ids for the customer, the transaction and the subscription. That's what we keep, with the payment link it was for. Never card numbers or bank details. Paddle's own records (such as your billing address and the email you paid with) stay with Paddle; we see them in Paddle's dashboard when we need to help with an order.
- Sales records: if you talk to us about Enterprise, we keep a record of the company: your name and work email, our notes from the conversation, the quotes and payment links we sent and whether they were paid, and which Burnstack account holds the plan. Only Burnstack staff can see it.
- Why: to agree and invoice a plan, to put it on your account, and to keep records the law requires.
- How long: while we're in touch and, for customers, as long as tax and accounting law requires after the last payment. Deleting your Burnstack account unlinks it from the sales record but doesn't delete that record; ask us to, at privacy@burnstack.app, and we'll delete what we don't have to keep.
The Burnstack app
The app collects nothing about you. It has no telemetry, and cost tracking needs no account. Your API keys stay in your computer's keychain and your spend and revenue data stay in a database on your computer. The app connects only to:
- The vendors you add, to read your billing and usage with your own key.
- The update check (new in 0.5.0): one public file (latest.json) from our update server, a public Supabase Storage bucket, on launch and every few hours. The request carries no account, no ID and none of your data; the server sees only what any web request shows, your IP address and that someone checked. Off with Settings → Update automatically.
- The price and vendor settings file (new in 0.8.0): while automatic updates are on, one small public file a day from the same server, signed with Burnstack's key. Like the update check, it carries no account, no ID and none of your data.
- Exchange rates (revenue tracking): only once a sale in a second currency appears, the European Central Bank's public reference rates, straight from the ECB. Nothing about you or your revenue is sent.
- Activation, only if you activate: see above.
Invoices you import are read on your computer, and the copies kept as evidence stay there. If you turn on the optional AI apps (MCP) setting, AI apps you connect, such as Claude or Cursor, can read your spend data on your computer; what they read goes to their AI provider under that provider's terms, and Burnstack doesn't receive it. More on security.
If you contact us
If you email us or use the contact form, we use what you send, including your name and email address, to reply and, for teams, to prepare a quote. An email from the app's Report a problem contains only what you saw in its draft (what that is). We keep the conversation as long as we need it to help you and to keep a record of what was agreed. The contact form is run by Tally, which stores what you submit on our behalf.
Why we're allowed to (legal bases)
Where the EU or UK GDPR applies, we rely on these bases in Article 6(1):
| What | Legal basis |
|---|---|
| Your account, licenses and Enterprise plan; sign-in emails | Contract (6(1)(b)): we need it to provide what you asked for. |
| The download record and the download link | Contract (6(1)(b)) for the link; legitimate interests (6(1)(f)) in keeping bots and abuse out. |
| Release and security emails to people who downloaded | Legitimate interests (6(1)(f)) in telling users about updates and fixes to software they installed. You can stop them any time; where the law requires your consent instead, we ask for it. |
| Server logs, rate limits, the Turnstile check and sign-in security logs | Legitimate interests (6(1)(f)) in keeping the site and accounts secure and working. |
| Page-view totals | Legitimate interests (6(1)(f)) in knowing which pages are useful, without identifying anyone. |
| Sales records, payment links and what Paddle tells us about payments | Steps before a contract and the contract itself (6(1)(b)); legal obligation (6(1)(c)) for tax and accounting records. |
| Answering you when you contact us | Legitimate interests (6(1)(f)), or steps before a contract (6(1)(b)) when you ask about a plan. |
| Anything we ask your permission for | Consent (6(1)(a)), which you can withdraw any time. |
Where we rely on legitimate interests, we've weighed them against your rights, and you can object (see your rights).
Who processes it for us
These services process personal data on our behalf, under their own data processing terms. We share nothing else with anyone, except where the law requires it.
| Service | What for | Where |
|---|---|---|
| Vercel | Hosts this website. Keeps standard server logs and runs Vercel Web Analytics (cookieless, totals only). | United States, served from a global network |
| Supabase | Runs sign-in (Supabase Auth), the database for accounts, licenses and download records, the Edge Functions this site calls, and the storage the installers and the app's update files come from. | European Union (Frankfurt, Germany) |
| Cloudflare Privacy policy and Turnstile addendum | Turnstile, the bot check on the download page. Email Routing, which delivers mail sent to our @burnstack.app addresses. | United States, served from a global network |
| Resend | Sends our emails: sign-in links from no-reply@burnstack.app, release emails if you downloaded the app, and payment links from sales@burnstack.app. | European Union (Ireland) |
| Paddle | Our reseller and Merchant of Record for Burnstack Enterprise: runs the checkout on /pay/, takes the payment, charges tax and sends receipts. For the payment itself Paddle is a controller in its own right, under its own privacy policy. | United Kingdom (Paddle.com Market Ltd), and where its policy says |
| Tally | The "Burnstack for teams" contact form. Nothing loads from Tally until you open the form. | Tally is based in Belgium; see its policy for where it stores data |
The service names link to their privacy policies.
How long we keep it
| Data | Kept |
|---|---|
| Download record (email, platform, dates, hashed user agent) | Until you ask us to delete it; at most 24 months after your last download |
| Rate-limit codes (one-way hashes of IP addresses and emails) | 2 days |
| Account (email, created, last sign-in), plan, active computers, free licenses | Until you delete the account |
| Deactivated computers | 30 days after deactivation |
| One-time activation codes (hash only) | 1 day |
| Sign-in security logs (Supabase Auth) | As long as Supabase keeps them under its own retention |
| Server logs (Vercel) and email delivery logs (Resend) | As long as each provider keeps them under its own retention, typically days to weeks |
| Page-view totals | No personal data is kept |
| Sales records and payment links | While we're in touch; for customers, as long as tax and accounting law requires after the last payment |
| Paddle's webhook event ids (no personal data) | 90 days |
| Emails and form messages you send us | As long as we need them to help you and keep a record |
International transfers
We're based in Israel, which the European Commission recognises as providing adequate protection for personal data. Our database and our email sending run in the EU. Vercel and Cloudflare are US companies whose networks serve visitors worldwide, so some data, such as server logs and the Turnstile check, may be processed in the United States or elsewhere. Where personal data from the EU or UK goes to a country without an adequacy decision, the provider relies on the safeguards the law allows, such as the EU–US Data Privacy Framework where the provider is certified, or the European Commission's Standard Contractual Clauses (with the UK addendum). Each provider's privacy policy, linked above, says which it uses.
Your rights
Wherever you live, you can ask us to:
- See your data (access): Download my data on your account page gives you a copy at once; for anything it lists as not included, or download records, email us.
- Take it with you (portability): the same file, in JSON.
- Correct it (rectification): rename a computer by activating it again; for your email, write to us.
- Delete it (erasure): Delete my account on your account page, or email us about a download record.
- Object to what we do on the basis of legitimate interests, including release emails, and restrict how we use your data while a question is sorted out.
- Withdraw consent you gave us, at any time, without affecting what was done before.
Email privacy@burnstack.app from the address the data is about, so we know it's you. We answer within one month, and it's free. If you're not happy with our answer, you can complain to a data protection authority: in Israel, the Privacy Protection Authority; in the EU, the authority in the country where you live or work; in the UK, the Information Commissioner's Office (ICO). We'd appreciate the chance to fix it first.
Cookies and local storage
This site sets no cookies, so it has no cookie banner. A few pages keep small items in your browser's local storage, each needed for something you asked for:
| Item | What it's for | How long |
|---|---|---|
sb-…-auth-token | Your sign-in on the account page (Supabase Auth). Other pages only check whether it's there, to say "Account" instead of "Sign in"; it's never sent anywhere but Supabase. | Until you sign out |
burnstack-activate | The app's one-time activation request, so activating survives signing in by emailed link. | Up to 30 minutes, removed once used |
theme | Light or Dark, if you pick one with the theme switch. | Until you pick System again |
Page counts are cookieless, and there are no advertising or tracking cookies. Cloudflare Turnstile, on the download page only, may use its own browser storage for the bot check, under its Turnstile addendum.
Children
Burnstack is a tool for developers and businesses. It isn't directed at children under 16, and we don't knowingly collect their data. If you think a child has given us personal data, email us and we'll delete it.
Security
Everything travels over HTTPS. Our database allows each signed-in person to read only their own account's rows; everything else is reachable only by our server functions. We store one-way hashes instead of IP addresses, user agents and activation codes, and the app's licenses are signed so they can't be forged. No system is perfectly secure; if we learn of a breach that affects your data, we'll tell you and the authorities as the law requires. Found a problem? Report a vulnerability.
Changes to this policy
When this policy changes, we update this page and the date at the top. If a change matters, such as a new use of your data, we'll say so on this site before it takes effect and, where it affects your account, email you.
Questions: privacy@burnstack.app.