Privacy

Short, because there isn't much to say.

Last updated: 13 August 2026.

Who is responsible

The data controller for this website and the early-bird list is Bandura, whose full legal identity and place of establishment are set out in section 14 of the licence agreement. For anything privacy-related, write to [email protected]. It is read and answered by a person, not a ticket queue.

What we collect, and why

If you join the early-bird list, one record is created and it holds five things: your email address; which tool you currently use and which platform you are on, both optional and both blank unless you answer them; the date and time you signed up; and which page of this site the form was on. That last one exists so we know which pages are worth writing, and it records the page, not you. That is the entire record. No IP address, no browser fingerprint, no tracking pixels in the emails, no enrichment, no third-party ad tech.

The legal basis is your consent (GDPR Art. 6(1)(a)): the form says exactly what you'll receive, one or two launch emails, and submitting it is the consent. You can withdraw it at any time; see below.

Cookies

This site sets no cookies, none at all, not even "essential" ones, and it does not fingerprint you. It stores exactly two localStorage entries, both of them a preference of yours rather than an identifier: your light/dark theme choice, written only if you flip the toggle, and a note that you have already given us an email address, written only if you submit the form, so that the download page does not ask you a second time. Neither is sent anywhere. Analytics, if enabled, is a privacy-preserving, cookie-free page counter: aggregate counts only, no personal identifiers, no cross-site tracking. There is no cookie banner because there is nothing to consent to; this section is the entire cookie policy.

Advertising measurement

There is none. This site used to carry Google's conversion tag in a locked-down, cookieless mode so we could tell whether search ads paid for themselves. It was removed on 14 August 2026, together with the five Google hosts the site's Content-Security-Policy allowed for it, so no request now leaves your browser for anyone but us. This paragraph stays rather than disappearing because a privacy policy that quietly drops a section leaves you unable to tell whether the practice ended or the disclosure did.

How long we keep it

Your address stays on the list until the launch emails have gone out, or until you opt out or ask us to remove it, whichever comes first. When you opt out or ask, the address is deleted, not just suppressed. The list is not reused for anything after launch without asking you again.

Where it's processed

Signups are stored in Linear (linear.app), the U.S.-based issue tracker we already run the project in, which processes the list only on our instructions under GDPR data-processing terms. The website is served by Cloudflare, and the form submits through a small Cloudflare function that writes to Linear and keeps nothing itself. That's the complete list of processors; nobody else touches the data.

What we will not do

No selling, no sharing, no "trusted partners." The list exists to tell you when the product ships, and for nothing else: one or two emails before launch, carrying the launch-day download link. There is no confirmation step and no welcome sequence: you sign up, and then you hear from us when there is something to say.

Your rights, and getting off the list

Every email we send includes a working opt-out link. Beyond that, you have the right to ask what we hold about you (spoiler: an email address and maybe a tool name), to correct it, to have it deleted, to receive a copy of it, and to withdraw consent. Write to [email protected] and it's handled promptly, by a human. If you're in the EU/EEA or UK and think we've handled your data badly, you also have the right to complain to your local data-protection authority, though we'd appreciate the chance to fix it first.

The product itself

Bandura the app is local-first by design: your flows are files on your machine, your API keys live in your OS keychain or your own .env, and nothing is sent to us. Any future telemetry will be strictly opt-in. That's a product principle, not a policy footnote.

Two exceptions, named rather than buried: AI features contact the provider whose key you supplied (or nothing at all, if you point Bandura at a model running on your own machine), and the app asks our public releases list on GitHub, at most once a day, whether a newer version exists. That second request carries no identifier, no licence key, and nothing about your machine or your flows, and a single switch in Settings turns it off. If a newer version does exist, Bandura can fetch and install it, but only after you press the button or turn on automatic downloads, which ship off. Fetching a file tells GitHub which file, so it reveals the operating system, the processor architecture and the version, exactly as downloading it in a browser would. Neither exception sends anything to us. The full wording is in §7 of the licence, and the complete table is on the security page.

For the product-side detail, meaning where flows, credentials, run history and your AI chat history are stored on disk, how the desktop app is sandboxed, and the complete table of what crosses the network, see security and privacy in the app. It is also the page to send a security reviewer or a vendor questionnaire to.