ZimmBot Risk Disclosures

Effective September 28, 2026 · Version 1.0 (risk-v1.0-2026-09-23)

These disclosures are part of the Terms of Service. Part A is the full disclosure. Part B is the summary shown before a bot goes live, and Part C is the checklist you confirm before your first live bot. When you go live, we record the version shown above.

Part A — The full risk disclosure

1. You can lose money — up to everything you allocate

Cryptocurrency prices are volatile. A bot's allocated capital ("slice") can fall in value quickly and can fall to near zero if the coin does. Nothing in the Service prevents loss. Never allocate money you cannot afford to lose entirely.

2. How the grid strategy loses money — three specific ways

(a) It buys on the way down. The engine rests buy orders at price levels below the market. In a decline, those orders fill one after another and the bot accumulates coin bought above the current price. If the decline continues, you hold coin worth less than you paid, and the bot will not sell it at a loss on its own (it waits for price to recover to the rung above each purchase).

(b) It carries inventory across weeks. Every week the price band is recomputed from the prior week's prices. Coin bought in the old band is carried into the new one and offered for sale at the new rungs above the current price. In a sustained decline you can hold carried coin for weeks or longer.

(c) The defense gate sells at a loss on purpose. When a coin falls 15% from its 30-day high, the engine enters DEFENSE: it cancels its orders and sells all coin the bot holds at the current market price, then waits in cash until the coin recovers to within 7.5% of that high. This locks in a loss of roughly 15% on held coin (more after slippage) to avoid a larger one. If the market recovers immediately after the gate fires, the gate has cost you that recovery. In our own four-week paper pilot the gate cost more than it saved, because that window happened to recover. We call the gate insurance, not a source of returns, and we say so in our marketing.

3. The bot will spend a lot of time doing nothing — by design

A grid only trades when price moves through its rungs. When price runs above the band the bot holds cash and waits; when it drops below, the bot holds coin and waits; when the cash left after inventory is too small for a full ladder of minimum-size orders, the bot pauses until the next weekly recomputation. Days or weeks without a trade are normal and are not a malfunction. The dashboard tells you which state a bot is in, why, and what would end it. A bot that shows "waiting" is working as designed; a bot that shows an error is not.

4. Paper results are not live results

Sandbox (paper) bots simulate fills: every order fills exactly at its price the instant the market touches it, with a modeled fee and zero slippage. Live orders wait in a real order book behind other traders and may fill later, partially, or not at all. The strategy code is identical; the fills are not. We measure the gap with our own money under a pre-registered test and publish only what that test supports. Until we publish a passing result, assume live results will be worse than paper results.

5. The AI regime read is information, not a trading decision

Five AI models classify the market every 30 minutes and every vote is shown to you. In the current product no AI vote places, cancels, sizes, or blocks an order — the engine's decisions are fixed calculations on price data. The models can be wrong, can disagree, and can be unavailable (when the read is stale the engine holds its last state rather than guessing). Do not treat the regime read as a prediction.

6. The exchange is a risk you take on directly

Your orders live on Binance.US. Exchange outages, API rate limits, maintenance, delistings, fee changes, minimum-order-size changes, and geographic restrictions all affect your bot and are outside our control. If the exchange rejects or delays an order, the bot continues with whatever the exchange reports. Live rungs are rounded to the exchange's lot size, so live orders can be slightly smaller than the paper equivalent.

7. Software can fail — ours included

We have found and fixed real defects in the live engine while trading our own money, and we log each fix with the date it took effect. A future defect could place a wrong order, miss a fill, or misreport state. Restarts, scheduled jobs, hosting, and third-party providers can all fail. We monitor, but we do not guarantee we will catch every condition or notify you of it in time.

8. Stopping a bot does not close your position

Stopping a bot ends new order placement. It does not sell your coin. When a live bot stops — your Stop or Delete, a fleet-wide pause, a stop on our side (within one bot cycle, about 30 minutes), or an automatic stop because its API key failed — the Service cancels the limit orders that bot has resting on the exchange (only its own orders). If the exchange cannot be reached, an order cannot be cancelled, or the key no longer works, the bot still stops and the dashboard shows a red warning: cancel the remaining orders yourself in your Binance.US account (Orders → Open Orders). Until then they can still fill, and any such fill is reconciled when you restart. A routine software restart — a few seconds — does not cancel orders; the bot picks them back up when it restarts.

9. Your API key is the only link — protect it

The Service can only trade because you gave it a key. Keep the key's permissions to spot trading only; never enable withdrawals. Before a bot goes live we verify the key can read your account and place orders (a test order Binance.US validates and never executes); Binance.US does not let us see whether withdrawals are enabled, so that setting is yours to confirm and the exchange's to enforce. We encrypt keys at rest, but no system is invulnerable. If you suspect your key is compromised, revoke it on Binance.US immediately — that instantly stops the Service from trading. Orders a bot already placed stay on the exchange until you cancel them there.

10. Manual activity in the same account interferes with the bot

Withdrawing funds a bot is using, placing your own orders in the same coin, or moving coin the bot holds can leave the bot with less than it expects, orders it cannot fill, or inventory it does not know about. Give a live bot its own money and leave that money alone, or stop the bot first.

11. Concentration

The Service currently supports one exchange (Binance.US) and one strategy family (grid). If that exchange or that strategy has a bad period, every bot has it.

12. Taxes

Grid trading generates many small taxable events. You are responsible for reporting them. We provide trade history and, on some plans, CSV export; we do not provide tax advice.

13. Regulatory uncertainty

Rules governing crypto trading software and automated execution are evolving. A change in the law, or in how regulators apply it, could require us to change, restrict, or stop parts of the Service, in some cases on short notice.

14. No advice, no guarantee, no promises

Nothing in the Service is investment advice. No result — paper, backtested, or live — is a guarantee of future performance. Any figure we publish states its source and its limits.

15. Your bot's cash is USDT, a stablecoin — not dollars

Every pair the Service trades is quoted in USDT (BTCUSDT, ETHUSDT and so on). The money a bot holds between trades, the proceeds of every sale, and the "cash" the defense gate retreats to are all USDT: a token issued by Tether and designed to trade at one US dollar. It is not dollars, not a bank deposit, and not insured, and nothing in the Service makes it worth a dollar. USDT has traded below one dollar during market stress. If its issuer failed or froze tokens, if a regulator acted against it, or if Binance.US delisted it, USDT could be worth less than a dollar or hard to sell — and that loss would fall on your whole slice, including the part a bot is holding "safely in cash". Dollars you deposit on Binance.US must be converted to USDT before a bot can use them, and converted back afterwards; each conversion is a trade at Binance.US's price and fee. The dashboard shows every balance and result in USDT and writes it with a dollar sign; your result in actual dollars depends on the USDT price when you convert.

Part B — The summary shown before you go live

Live trading uses real money on your own Binance.US account. A grid bot buys on the way down and can hold coin bought above the current price for weeks. If the coin falls 15% from its 30-day high, the bot sells everything it holds at market and waits in cash — that locks in a loss to avoid a bigger one, and it can be wrong. Paper results are simulated with perfect fills; live fills are slower and smaller. The AI regime read is shown for information and does not place orders. Stopping a bot does not sell your coin; it cancels the bot's own resting orders, and warns you if the exchange could not be reached. You can lose everything you allocate. Read the full Risk Disclosures before continuing.

Part C — What you confirm before your first live bot

Each box must be ticked; the go-live button stays disabled until all are. We store your acknowledgment with a timestamp and the version of these disclosures you were shown.

Terms of Service · Risk Disclosures · Privacy Policy · support@zimmbot.com
// Risk Disclosures · RISK_DISCLOSURES.md · rendered from the repository at request time.