← Back to Nimbus Flow

Privacy note

Last updated October 2026

Nimbus Flow is a small, independent beta project. This page explains, in plain terms, what happens with your information when you create an account.

What we collect

• Your email address and password, when you sign up (handled by Supabase, our authentication provider — we never see or store your password ourselves).
• A simple log entry each time you download the app, so we can see rough usage counts (which app, and when — nothing else).

Services the website loads

Visiting the site doesn’t require an account, but your browser does contact a few outside services to load the page. Each sees your IP address and browser details, as any website visit does:

• Cloudflare Web Analytics — counts page visits. It doesn’t use cookies or build a profile of you.
• Google Fonts — serves the site’s fonts.
• jsDelivr — serves the code library used for sign-in (Supabase).
• GitHub — the page asks GitHub for the latest release so download buttons point to the newest installer, and the installers themselves are hosted there.

What we use it for

• Logging you in and keeping your account secure.
• Sending you the one-time email confirmation and password-reset links you request.
• Getting a rough sense of how many people are using Nimbus during the beta, to help prioritize what to build next.

What we don't do

• We don't sell or share your email with anyone.
• We don't send marketing emails.
• We don't track you across other websites.

Your files and prep never leave your computer

This is the part debaters care about most, so we want to be blunt about it: Nimbus cannot take your files, your prep, your blocks, or your flows. There is no feature that uploads them, because the ability to do so was never built.

• The documents you open for CardMirror and Smart blocks — your .docx and .cmir files — are read and saved only on your own machine. They are never sent to us or to anyone else. We run no server that receives them, and we have no way to see them.
• Your flows, argument bank, snippets, timers and settings are stored locally on your device too, the same way. Nimbus is built to work fully offline after a single sign-in — there is no round of data phoning home in the background.
• We cannot “steal” another team’s files or prep, and neither can anyone using Nimbus. Opening a file in your own copy of the app does nothing but display it to you, on your computer.

The only information that ever leaves your device is (1) your login, described above; (2) when you choose to flow live with your partner, the cells of that one shared flow are passed between the two of you through a realtime relay so your partner can see them as you type. That relay carries only the flow you are actively sharing — never your stored files, prep, or other flows — it passes the data through rather than storing it, and only your partner receives it; and (3) when you press Ask AI in How do I…?, the question you typed is sent, together with Nimbus’s own built-in help text, to an AI model run by Cloudflare so it can answer. Nothing else goes with it — no flow, file or prep — and we don’t store the questions. If you never press Ask AI, nothing is sent.

Open source — don’t take our word for it

Every line of code Nimbus runs is public and free to read. The entire app is open source under the MIT license, at github.com/Asaw2011/nimbus. Nothing about how it handles your data is hidden.

If you would rather verify these claims than trust them, please do. Clone the repository and read it, ask a coach or a developer to look it over, or point an AI code assistant at the whole codebase and ask it plainly: “Does this app upload, transmit, or exfiltrate the user’s files or prep anywhere?” You are welcome to audit it however you like. There is nothing there to find, and that is exactly the point of keeping it open.

Deleting your account

Self-serve deletion isn't built into the site yet. If you'd like your account and data removed, open an issue on GitHub or reach out however you normally would, and it'll be handled by hand.

Questions

Ideas, concerns, or questions about any of this are welcome via the same GitHub Issues page used for bug reports.