Privacy

This website has one form on it: the early-access waitlist. If you use it, we keep your email address so we can tell you when there is something to install. That is the entire collection story.

There are no analytics scripts, no advertising pixels, no tracking cookies and no third-party embeds on any page of this site. Nothing you do here is sent to anyone but us.

When you submit the waitlist form, exactly five fields are written down. Nothing is inferred, enriched or bought from anywhere else.

The honeypot field in the form is discarded either way — if it is filled in, the submission is silently dropped and nothing at all is written.

• Your email address, trimmed and lower-cased.
• Which product surface you signed up from — suite, code or voice.
• Which button opened the form, so we know which page persuaded you.
• The moment you submitted, as a UTC timestamp.
• Your browser's user-agent string, truncated to 300 characters, so we know roughly which platforms to prioritise.

The waitlist endpoint limits each address to five submissions in ten minutes. To do that it holds your IP address in the server's memory alongside the times you posted.

That list is never written to disk, never joined to your email address, and disappears when the process restarts or when ten minutes pass — whichever comes first. It exists to stop a script hammering the form, and it does nothing else.

Waitlist entries are appended, one JSON object per line, to a file on a disk attached to the single server that runs this website. That server sits in a rented rack in Germany.

There is no database, no customer-data platform and no email-marketing service in the path. We did not connect one, because a list of email addresses waiting for a launch does not need one.

Nobody. We do not sell, rent, trade or share waitlist entries, and there is no third party we hand them to for processing.

The two companies unavoidably in the picture are the hosting provider that rents us the server the file sits on, and — when we eventually send the launch email — whatever mail provider carries that message. Neither gets the list for their own use.

The one thing that would change this is a legal order we are compelled to obey. If that ever happens and we are permitted to tell you, we will.

The site sets no cookies. The only thing it stores in your browser is your light or dark theme choice, which lives in local storage under a single key and is never sent to the server.

Fonts are served from this domain rather than fetched from a font CDN, so loading a page does not tell anyone else that you visited. There are no embedded videos, no chat widgets and no social buttons.

The web server keeps ordinary access logs — request path, status code, timestamp, IP address — for operational debugging. They are not analysed for behaviour and are not linked to waitlist entries.

Waitlist entries are kept until the products launch and the early-access email has gone out, or until you ask us to remove yours — whichever comes first. After the launch mail, the list is deleted rather than repurposed into a newsletter.

You will not be added to any other mailing list, and the address will not be reused for a different product.

You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. There is no account to log into, so a request from the address you signed up with is enough for us to act on.

Deletion is exactly that: the line is removed from the file. There is no archive copy and no backup index we would have to go hunting through.

This policy covers the website. The apps are separate, and each ships its own terms — but since privacy is the reason many people are here, here is the honest shape of them.

NabuVoice runs speech recognition and text correction entirely on your own machine. It has no accounts and makes no network calls for transcription; the audio never leaves the device.

NabuCode is proprietary software that runs coding agents on your machine, using the agent CLIs already installed on your PATH. Pairing your phone to supervise and unblock a running session happens over a TLS connection you establish by scanning a QR code. Where NabuCode offers an optional cloud feature, it uses an API key you supply, and those requests go to the provider you chose — not to us.

If what we collect changes, this page changes on the same day, and the date at the top moves with it. We will not quietly widen the collection and leave the old text up.

If the change is material and you are on the waitlist, we will say so in the next email we send you rather than relying on you to re-read this page.