Your code stays yours.
Here’s what we do collect.

Zeltro sells no AI. When you use your own AI with Claude Code, Codex, Antigravity, Qwen Code, Aider, OpenCode or Hermes Agent (a plan, your own API key, your own OpenRouter account or a local model), your prompts and code go straight from your computer to the provider you chose, under that provider’s terms. They never pass through Zeltro.

The first time you open Zeltro, it offers to let you try it out on our key: enough for a first project, one per computer, while it lasts. It’s a try‑out, not a free plan. Accept it and Zeltro sets up Claude Code on Claude Haiku for you, with no account and no card. That AI runs through Zeltro’s server, which passes your prompts, and the code and files the AI reads or writes for you, to OpenRouter and on to the model’s provider, under Zeltro’s account. For Claude Haiku that is Anthropic itself, or the Amazon, Google or Microsoft clouds that host the model. Each request tells OpenRouter to use only providers that don’t collect or train on what they’re sent, and prompt logging at OpenRouter is turned off.

What we keep. When you accept the try‑out, the app sends a one-way scrambled (hashed) identifier of your computer, so that each computer gets it once. We scramble it once more before storing it, and keep it with your install ID, how much AI the try‑out includes, how much of it you’ve used, how many requests you’ve made, and when it was last used or switched off. The access code your app gets for the try‑out is stored only in scrambled and locked form. For each request we record the model, the token counts, the cost and OpenRouter’s reference number for it, and delete those records after 90 days (the running total stays with your try‑out).

What we never keep. Your prompts and the AI’s answers pass through the server’s memory and are never written down or logged. We also never keep your computer’s ID or its first scramble, the access code in readable form, or your IP address with the try‑out (our ordinary server logs still record it, as below). To limit how many try‑outs one network can claim, a scrambled copy of the IP address is held for one day and then dropped. Once you connect your own AI, nothing goes through Zeltro, as above.

When the app sends usage counts, an error report or a license check, or you try Zeltro on our key, our servers record the IP address it came from. We use it for security, to prevent abuse, and to work out roughly where you are (country, region and city). Server logs, which include IP addresses, are kept for 14 days. They record which address asked for which page and when, never what was sent or answered. The usage statistics keep only that rough location, not the address, and error reports don’t contain it.

If you enter a Zeltro license key, the app checks it with the license server (license.zeltro.ai, run by Cane Bay Computers & Mobile, over HTTPS) when you enter it and about once a week after that. Each check sends exactly four things: the license key, the install ID, the app version and the operating system. The server never stores the key itself: only a scrambled (hashed) copy and its last four characters, so a key can be recognised but not read back. For each install that checks a key we issued (including one that has since been disabled) it keeps the install ID, app version, operating system, when that install first and last checked, and how many times it has checked. It does not store your IP address. To stop abuse it briefly remembers a scrambled form of the address: for 60 seconds, or up to an hour when you start a purchase. Like our other servers, its logs keep the address for 14 days (see above). A copy of the app with no key entered makes no license checks at all.

The command line tool sends nothing. It is open source, so you can check.

A business buys a license from inside the app, and the only thing you type is the business name. The license server records it as an order, together with the install ID, app version, operating system, the amount and the order’s status, then sends you to our card processor (ValorPay) to pay. To set up the payment, it gives ValorPay only your business name, the order number, the amount and the name of the license, never your email address, your name or anything about your computer. You type your card details on ValorPay’s page, so they never reach us, and ValorPay’s own privacy policy covers them. When the payment goes through, ValorPay tells the license server its payment reference, transaction number and approval code, and the email address you typed on its payment page, if any.

Your copy of the app then collects the key itself. When you start a purchase it makes a private claim code that stays on your computer. The server keeps only a scrambled form of that code, and after you pay it keeps your key locked with it, so only the copy of the app holding the code can open it. Someone reading the server’s database could see neither the code nor the key. If you typed an email address on ValorPay’s page, the key is also emailed there once, through Amazon SES. (Older versions of the app asked for an email address and contact name at checkout. Those are kept on the order, and the key is emailed to that address too.)

The license itself keeps the business name, any contact name and email address from the order, the payment reference, any notes I add, and a scrambled (hashed) copy of the key with its last four characters. Apart from the locked copy your app collects, the key isn’t kept anywhere it could be shown again, so a lost key is replaced rather than resent. Licenses, their orders and their install records are kept for as long as the license exists. An order that is never paid, or that a newer purchase attempt replaces, is deleted automatically after 7 days, and a payment page stops working after a day. The server’s own log records order numbers and why a payment was rejected or held for review, never keys or card details. Only I can see any of this.

zeltro.ai uses Google Analytics to count visits and see which pages are read, and like most websites its server logs visitors’ IP addresses, kept for 14 days. If you email me, I use your message only to reply. It is never shared or added to a mailing list.

Email canebaycomputers@gmail.com. App data isn’t linked to your name, so include your install ID (shown in Settings → License in the app) if you want yours deleted.