ZimmBot Terms of Service

Effective September 28, 2026 · Version 1.0

1. The agreement, the parties, and who may use the Service

1.1 Parties. These Terms of Service (the “Terms”) are a binding agreement between you and Dream State Investments LLC, an Indiana limited liability company (“ZimmBot”, “we”, “us”, “our”). ZimmBot is a product of Dream State Investments LLC. We operate the website, dashboard, and automated trading software at zimmbot.com (together, the “Service”).

1.2 Acceptance. You accept these Terms by creating an account, by clicking to accept them, or by using the Service. The Privacy Policy and the Risk Disclosures are part of these Terms by reference. If you do not agree, do not create an account and do not use the Service.

1.3 Eligibility. To use the Service you must (a) be at least 18 years old; (b) be a resident of the United States; (c) be legally able to open and hold a Binance.US account in your state; and (d) not be a person with whom U.S. persons are prohibited from dealing under U.S. sanctions or export laws. Live trading (Section 3) additionally requires a Binance.US account in your own name.

1.4 Electronic notices. You agree that we may give you notices — including notices of changes to these Terms and warnings about your bots — electronically, in the dashboard and by email to the address on your account, and that electronic notices satisfy any requirement that a notice be in writing.

1.5 Your account. You are responsible for everything done through your account and for keeping your password confidential. Tell us at once if you believe your account has been accessed without authorization. Accounts are for one person and may not be shared, sold, or transferred.

2. What the Service is — and what it is not

2.1 What it is. ZimmBot is software. You connect your own Binance.US account by entering an API key that you create. You choose which coin or coins to trade and how much money to allocate to each bot (the “slice”). The Service’s trading engine then places and manages spot buy and sell orders in your exchange account according to a grid strategy derived from that configuration, continuously, until you pause or stop it. Section 4 describes exactly how the strategy behaves, and by using the Service you agree to those mechanics.

2.2 What it is not. (a) Not a custodian. We never hold, receive, pool, or transfer your money or your cryptocurrency. Your funds remain in your exchange account at all times. The Service is designed so that it never needs withdrawal permission on your account and never calls a withdrawal function, and you should never grant it withdrawal permission (Section 3.2). (b) Not an investment product. We do not offer a token, fund, pooled account, or any investment of our own, and we do not accept deposits. (c) Not compensated by your results. We do not charge fees based on your assets or your profits. We charge a flat subscription (Section 6).

2.3 Adviser status. ZimmBot is a software tool that executes a strategy you configure. It does not provide personalized investment advice or recommendations. Nothing in the Service — including the AI market read described in Section 4.5 and the configuration suggestions described in Section 4.10 — is a recommendation to buy, sell, or hold any asset, and neither we nor any feature of the Service exercises discretion over your account beyond the fixed, disclosed rules of the strategy you selected.

3. Your exchange account and API keys

3.1 You create the key. You generate a Binance.US API key and enter it into the Service. The key must have spot trading enabled. Before a bot goes live, the Service verifies that the key can read your account and place orders — it asks Binance.US to validate a small test order that is never executed — and refuses to go live if the exchange rejects either check.

3.2 Do not enable withdrawals. The Service never needs withdrawal permission and never calls a withdrawal function. Binance.US does not disclose to us whether a key has withdrawal permission, so the Service cannot verify that setting for you: you confirm it when you go live, and the exchange enforces it — a key without withdrawal permission cannot withdraw no matter who holds it. The go-live record states which checks the Service verified and which you acknowledged. We also recommend restricting the key to our server’s IP address; the setup guide explains how.

3.3 We re-check your key. Once a bot is live, the Service re-verifies every hour that your key still reads your account and can still place orders. If a check fails — for example because the key was deleted or edited on Binance.US, an IP restriction no longer matches our server, or trading permission was revoked — the Service shows a warning on the affected bot’s card. The hourly check does not stop the bot, but until the key works again the bot cannot place, cancel, or reconcile orders, and any orders it already has resting on the exchange stay there. A live bot also checks its key each time it starts or restarts and after its key is replaced; if the exchange refuses the key, the bot stops itself, does not trade on that key, and its card says so. A refused key cannot cancel orders, so the bot’s resting orders stay on the exchange until you cancel them in your Binance.US account (Orders → Open Orders); the one exception is a replaced key, where the bot first uses the previous key, if it still works, to cancel its own resting orders. Fixing or replacing the key is yours to do.

3.4 How we store keys, and how to remove them. Keys are encrypted at rest, are decrypted only by the processes that place orders on your behalf, and are never displayed again after entry. You can replace or remove your key at any time in the dashboard (Settings → Manage API Keys). Removing it first stops every live bot you have and cancels that bot’s resting orders while the key still works, then deletes the stored key; the dashboard says so before you confirm. Deleting the key on Binance.US instead revokes our access at once but leaves any resting orders on the exchange until you cancel them there (Section 4.7).

3.5 Binance.US is not us. Your relationship with Binance.US is governed by its own terms. We are not responsible for the exchange’s availability, fees, minimum order sizes, lot-size rounding, listings, delistings, or geographic restrictions. If the exchange rejects, delays, or partially fills an order, the Service records what the exchange reports and continues; the exchange’s records are the source of truth for what happened in your account.

3.6 One account, one operator. The Service is for trading your own money in your own exchange account. You may not use the Service to trade an account that belongs to someone else, or to trade other people’s money through your account, unless you hold every license and registration that activity requires, and you represent that you will not do so.

4. How the trading engine behaves — the mechanics you are agreeing to

This Section is deliberately specific. A customer cannot meaningfully consent to a strategy they have not been told about, and our product is built on showing you every decision. Read it before you allocate real money.

4.1 The grid. For each bot, the engine computes a price band for your coin from the trailing seven days of prices, divides the band into evenly spaced price levels (“rungs”), and rests limit buy orders at the rungs below the current price. When a buy fills, the engine places a limit sell order one rung higher. When that sells, the buy is re-armed. All orders are limit (“maker”) orders; the engine does not chase the price. The number of rungs is derived from your slice — at most ten, and fewer for smaller slices so that every rung clears the exchange’s minimum order size — and each rung’s order is your slice divided by the number of rungs.

4.2 Weekly recomputation and carried inventory. The band is recomputed on a fixed weekly schedule (a “block”). Coin bought at the old rungs is carried into the new band and offered for sale at the new rungs above the current price. In a sustained decline the engine therefore buys on the way down, and you will hold coin bought above the current price — possibly for weeks or longer. The engine does not sell carried coin at a loss on its own; it waits for the price to recover to the rung above each purchase, except as the defense gate provides (Section 4.4).

4.3 Idle and paused states are normal. When the price is above the band, all cash waits and nothing trades until the price comes back down or the band is recomputed. When the price is below the band, buys fill on the way down and nothing sells until the price recovers. When the cash left after carried inventory is too small to place 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 shows which state each bot is in, why, and what would end it. Small allocations pause more often: the Service sets a minimum live allocation and, when you go live with less than $500, shows cautions based on our own testing (in our four-week test, $50–$250 slices spent about half the run paused while holding coin) together with a link to that test data.

4.4 The defense gate — read this. The engine tracks each coin’s drawdown from its highest price of the past 30 days. This is a price calculation, not an AI output. When the drawdown reaches 15%, the bot enters DEFENSE: it cancels its resting orders, sells all coin the bot holds at the market price (a taker order, filled at whatever the order book offers), and stops buying. It resumes only when the coin has recovered to within 7.5% of its 30-day high, at which point a fresh band is computed. Plainly: the defense gate locks in a loss of roughly 15% on held coin (more after slippage) in order to avoid a larger one. It can be wrong — in a market that dips 15% and then recovers, the gate costs you the recovery. In our own four-week paper test the gate cost more than it saved, because that particular window recovered. We describe the gate as insurance, not as a source of returns. It operates on every plan and cannot be turned off in the current product.

4.5 The AI market read is informational. Five independent AI models each classify the market’s condition every 30 minutes, and every vote is shown on the bot’s card. In the current product, no AI vote places, cancels, sizes, or blocks an order. The engine’s decisions — the band, the rungs, the weekly recomputation, and the defense gate — are fixed calculations on price data. The AI votes are displayed for your information and scored by us for accuracy. If we ever allow them to influence trading, we will say so in these Terms and in the engine’s version notes before it takes effect, and you will be asked to acknowledge the change before it applies to a live bot.

4.6 Paper trading versus live trading. Paper (“Sandbox”) bots simulate fills against real market prices with no slippage and no waiting in line. Live bots place real orders that wait their turn in the exchange’s order book and are rounded to the exchange’s lot size, so live orders can be slightly smaller than their paper equivalents. The strategy code is identical; the fill model cannot be. We measure the difference by trading our own money under a pre-registered test and publish only what that test supports; until we publish a passing result we make no claim that paper results predict live results.

4.7 Stopping a bot. You can stop a bot at any time from the dashboard. Stopping ends new order placement. Stopping does not sell your coin. When a live bot stops, the Service also cancels the limit orders that bot has resting on the exchange — only that bot’s own orders, never another bot’s and never an order you placed yourself. That holds for every way a bot stops: your Stop or Delete (at once), a fleet-wide pause (Section 4.9, at once), a stop performed on our side (at the bot’s next cycle, within about 30 minutes), and an automatic stop because the bot’s API key failed (Section 3.3). If the exchange cannot be reached, an order cannot be cancelled, or the bot’s API key no longer works, the bot still stops, and the dashboard shows a red warning telling you to cancel the remaining orders in your Binance.US account (Orders → Open Orders); until you do, those orders can still fill, and the Service reconciles any such fill when the bot is restarted. A routine restart of our software — a few seconds while new code loads — is not a stop: the bot’s orders stay in place and it picks them back up when it restarts (Section 4.8).

4.8 Restarts and engine versions. After a restart, a bot’s first cycle begins by reading its orders and fills from the exchange, which is the record of truth; any fill that happened while it was down is booked before the bot places or cancels anything. The engine software is versioned. We may deploy new versions; each change is recorded with the date it took effect and, where it changes the mechanics described in this Section, announced in the dashboard before it applies to live bots.

4.9 Fleet-wide pause. We may pause all trading across the Service in an emergency — an exchange outage, a suspected defect, a security incident. A fleet pause stops new orders and cancels each live bot’s own resting orders (Section 4.7); it does not sell your coin. We will post notice of a fleet pause in the dashboard.

4.10 Configuration suggestions are never applied automatically. The dashboard may show you a configuration suggestion generated by a fixed, published rule — for example, suggesting fewer rungs when a bot has been paused for lack of cash for several days. A suggestion states the rule that produced it and the numbers it was based on. It is never applied unless you accept it; you may dismiss it; and an accepted change takes effect at the bot’s next weekly recomputation. Suggestions are computed from your bot’s own state and the rule’s fixed thresholds; they are not produced by an AI model and they are not personalized advice.

5. Paper trading (Sandbox)

Sandbox bots trade simulated money against real prices. Simulated results are hypothetical: they assume every order fills exactly at its price the moment the market touches it, with a modeled fee and no slippage. They are useful for learning how the strategy behaves and are not a prediction of live results. Sandbox accounts cannot trade live.

6. Plans, billing, and limits

6.1 Plans. The Service offers the plans below. Plan contents are listed on the pricing page, which controls if this table and the page differ.

Plan	Monthly price	Live trading	Coins (one bot per coin)	Aggregate live-capital cap	Trade-history window	CSV export
Sandbox	Free	No — paper only	BTC	—	30 days	No
Starter	$9.99	Yes	BTC, ETH, SOL, XRP	$5,000	90 days	No
Pro	$19.99	Yes	BTC, ETH, SOL, XRP, ADA, DOGE, LINK, AVAX	$25,000	Full	Yes
Elite	$49.99	Yes	Same eight coins	$100,000	Full	Yes

6.2 Billing. Paid plans are billed monthly in advance through Stripe, our payment processor, and renew automatically each month until you cancel. Prices exclude any applicable taxes. You may cancel at any time by emailing us at support@zimmbot.com (Section 21); cancellation takes effect at the end of the current billing period, and you keep your plan’s features until then. Except where the law requires otherwise, fees are non-refundable.

6.3 Downgrades and cancellations never force a sale. If your plan changes to a lower tier or ends, your existing live bots keep running to their natural exits. The lower tier’s limits apply to new bots and new capital only. We will never sell your coin, and never stop a running live bot, because of a billing event.

6.4 Capital limits and per-coin ceilings. Each plan has an aggregate cap on live capital across all of your bots. In addition, each coin has a platform-set per-bot ceiling derived from the measured depth of the exchange’s order book (one rung may not exceed 1% of the book within 2% of the price), recomputed weekly. Ceilings apply to paper and live bots alike and are checked when a bot goes live and when its slice changes. If a coin’s order book thins under an existing bot we warn you; we never force a bot to shrink or sell.

6.5 Never paywalled. The defense gate (Section 4.4), the display of every AI vote and every trade receipt, and the per-coin ceilings apply on every plan, including Sandbox.

7. No advice, no guarantees, and your acknowledgment of risk

7.1 Nothing in the Service is investment, financial, legal, or tax advice, and nothing in it is a recommendation to buy, sell, or hold any asset.

7.2 You can lose money, including everything you allocate to a bot. Cryptocurrency prices are volatile; the grid strategy accumulates coin in declines; the defense gate sells at a loss by design; and the exchange, our software, and third-party providers can all fail. No feature of the Service prevents loss.

7.3 Past performance — paper, backtested, or live, ours or anyone’s — does not predict future results. Any figure we publish states its source and its limits under our marketing-claims policy.

7.4 Go-live acknowledgment. Before your first live bot, and again after any material change to the mechanics in Section 4, you must read the Risk Disclosures and confirm each item of the acknowledgment checklist. The Service records the version of the disclosure you were shown, the items you confirmed, the allocation, the pre-flight results, and the time, IP address, and browser used, as evidence of your consent.

8. Your responsibilities

You agree to: (a) keep your login credentials and API keys secure — we will never ask for your exchange password; (b) give each live bot money of its own and leave that money alone: do not withdraw funds a live bot is using, and do not place your own orders in a coin a live bot is trading, because manual activity in the same account can leave a bot holding less than it expects, waiting on orders you did not intend, or unaware of inventory it did not buy; (c) keep enough quote currency (USDT) in the account for the bot’s orders; (d) monitor your bots — the Service shows each bot’s state, reasons, and next event, but does not guarantee to notify you of every condition; (e) determine and pay any taxes on your trading — the Service provides trade history and, on some plans, CSV export, but not tax advice; (f) provide accurate account information and keep it current; and (g) use the Service only as these Terms and the law allow.

9. Availability, changes, and defects

9.1 No uptime guarantee. The Service is provided without an uptime guarantee. Scheduled jobs, the exchange, third-party AI and data providers, and our own hosting can fail. When the AI market read is stale, the engine keeps its last state rather than guessing.

9.2 Defects. We have found and fixed real defects in the live engine while trading our own money, and we expect to find and fix more. We log each fix with the date it took effect. A future defect could place a wrong order, miss a fill, or misreport a bot’s state; Sections 15 and 16 govern our responsibility for that.

9.3 Changes to the Service. We may change, add, or remove features, coins, and limits. Changes to the engine mechanics described in Section 4 are announced in the dashboard before they apply to live bots (Section 4.8).

10. Prohibited uses

You may not: (a) share, sell, or transfer an account; (b) use the Service on an exchange account you do not own in your own name; (c) manage other people’s money through the Service without every license and registration that requires; (d) reverse-engineer, scrape, copy, or interfere with the Service, or access it by any means other than the interfaces we provide; (e) use the Service to violate the exchange’s terms, any law, or anyone’s rights; (f) misrepresent the Service or its results to others; or (g) use the Service if you are under 18 or otherwise ineligible (Section 1.3).

11. Privacy and data

We collect your email address and a one-way hash of your password, a Stripe customer identifier, your encrypted exchange API key, your bot configurations, engine state, orders, fills, results, and settings history, the AI votes and market data used to produce your bots’ market read, your live-trading consent records, and ordinary server logs. Every AI vote and every trade receipt that concerned your bot is shown to you. We send market data and anonymous platform-wide statistics — never your identity, balances, keys, orders, or trades — to the third-party AI providers that produce the market read. We do not sell personal information and we do not run advertising trackers. The Privacy Policy explains what we collect, how long we keep it, who else sees it, and your choices, and it governs if it conflicts with this Section.

12. Intellectual property and license

12.1 Ours. The Service — its software, engine, documentation, designs, and the ZimmBot name and marks — belongs to us and our licensors and is protected by intellectual-property laws. We grant you a limited, revocable, non-exclusive, non-transferable license to use the Service for your own trading under these Terms. No other rights are granted.

12.2 Yours. Your bot configurations, your trade history, and any data you export are yours. You grant us the right to store and process them to provide the Service and to include them in anonymous, aggregated statistics that cannot identify you.

12.3 Feedback. If you send us suggestions, we may use them without obligation to you.

13. Third-party services

The Service depends on services we do not control, including Binance.US (your exchange), Stripe (payments), the AI providers that produce the market read, hosting and database providers, and market-data sources. Your use of Binance.US and Stripe is governed by their terms. We are not responsible for the acts, omissions, availability, fees, or data of any third-party service, and an interruption or change at a third party may interrupt or change the Service.

14. Term, suspension, and termination

14.1 By you. You may stop any bot at any time, remove your API key at any time (Section 3.4), and cancel a paid plan at any time (Section 6.2). To close your account, contact us (Section 21); we will delete your account and personal data, or anonymize records we are required to keep, within 30 days, as described in the Privacy Policy.

14.2 By us. We may suspend or terminate your account, or restrict features, if you breach these Terms; if we are required to by law or by a third party we depend on; if we reasonably believe your use creates risk for you, us, or others; or if we discontinue the Service. Where practical we will give notice first.

14.3 Effect. On suspension or termination, your bots stop placing new orders. Any coin you hold, and any resting order the Service did not cancel, remain in your exchange account (Section 4.7); you can cancel orders there at any time, and removing your API key — in the Service or on Binance.US — ends our access. We do not sell your coin on termination. Sections 7, 12, 13, 15 through 20, and 21 survive termination.

15. Disclaimers

THE SERVICE IS PROVIDED “AS IS” AND “AS AVAILABLE,” WITH ALL FAULTS, AND WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, OR NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE; THAT ANY ORDER WILL BE PLACED, FILLED, OR CANCELLED; THAT ANY DEFECT WILL BE CORRECTED; OR THAT USING THE SERVICE WILL BE PROFITABLE OR WILL AVOID LOSS. NO ORAL OR WRITTEN INFORMATION OR ADVICE FROM US CREATES A WARRANTY. SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SOME OF THE ABOVE MAY NOT APPLY TO YOU.

16. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW: (A) WE ARE NOT LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, DATA, OR GOODWILL, OR FOR ANY TRADING LOSS — INCLUDING LOSSES FROM ORDERS THE SERVICE PLACED, FAILED TO PLACE, FAILED TO CANCEL, OR MIS-PRICED, FROM THE DEFENSE GATE, FROM PRICE MOVEMENTS, OR FROM THE ACTS OR FAILURES OF THE EXCHANGE OR ANY OTHER THIRD PARTY — HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, EVEN IF WE WERE ADVISED OF THE POSSIBILITY; AND (B) OUR TOTAL LIABILITY FOR ALL CLAIMS ARISING OUT OF OR RELATING TO THE SERVICE OR THESE TERMS WILL NOT EXCEED THE GREATER OF (I) THE SUBSCRIPTION FEES YOU PAID US IN THE TWELVE MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM AND (II) ONE HUNDRED U.S. DOLLARS ($100). THESE LIMITS DO NOT APPLY TO LIABILITY THAT CANNOT BE LIMITED BY LAW, INCLUDING LIABILITY FOR OUR GROSS NEGLIGENCE, WILLFUL MISCONDUCT, OR FRAUD. THE LIMITATIONS IN THIS SECTION ARE AN ESSENTIAL BASIS OF THE BARGAIN AND APPLY EVEN IF A REMEDY FAILS OF ITS ESSENTIAL PURPOSE.

17. Indemnification

You will defend, indemnify, and hold harmless Dream State Investments LLC and its members, managers, employees, contractors, and agents from and against any claim, demand, loss, liability, damage, cost, or expense (including reasonable attorneys’ fees) arising out of or relating to: (a) your breach of these Terms; (b) your use of the Service, your exchange account, or your trading, including any tax obligation; (c) your violation of any law or of the rights of any third party; or (d) any use of the Service through your account or with your API key, whether or not authorized by you. We may assume the exclusive defense of any matter subject to indemnification, in which case you will cooperate with us.

18. Governing law and disputes

18.1 Governing law. These Terms, and any dispute arising out of or relating to them or the Service, are governed by the laws of the State of Indiana and applicable federal law, without regard to conflict-of-laws rules.

18.2 Informal resolution first. Before starting any formal proceeding, you agree to contact us (Section 21) with a written description of the dispute and to work with us in good faith to resolve it for 30 days.

18.3 Arbitration. Any dispute not resolved informally will be resolved by binding individual arbitration administered by the American Arbitration Association under its Consumer Arbitration Rules, before a single arbitrator, with any hearing held in Cass County, Indiana or by video at your election. The arbitrator, not a court, decides whether a dispute is arbitrable. Either party may instead bring an individual claim in small-claims court. YOU AND WE EACH WAIVE THE RIGHT TO A JURY TRIAL AND TO PARTICIPATE IN A CLASS, COLLECTIVE, OR REPRESENTATIVE ACTION; CLAIMS MAY BE BROUGHT ONLY IN AN INDIVIDUAL CAPACITY. You may opt out of this arbitration agreement by emailing us at support@zimmbot.com within 30 days after first accepting these Terms. If you opt out, or if the class-action waiver is found unenforceable as to a claim, the dispute (or that claim) will be brought exclusively in the state or federal courts located in Cass County, Indiana, and you consent to their personal jurisdiction.

18.4 Time limit. Any claim arising out of or relating to the Service must be brought within one year after it arises, or it is permanently barred, except where the law does not permit this limit.

19. Changes to these Terms

We may update these Terms. We will post the new version with its version number and effective date, and we will notify you in the dashboard and by email at least 14 days before a material change takes effect. Your continued use after the effective date is acceptance of the new Terms; if you do not agree, stop using the Service and close your account before that date. Changes to the engine mechanics in Section 4 also require the re-acknowledgment described in Section 7.4 before they apply to a live bot. The version you accepted, and the version shown at each go-live, are recorded.

20. General terms

20.1 Entire agreement. These Terms, together with the Privacy Policy and the Risk Disclosures, are the entire agreement between you and us about the Service and supersede any prior agreement or understanding.

20.2 Severability. If any provision is held unenforceable, it will be enforced to the maximum extent permitted and the rest of these Terms remain in effect.

20.3 No waiver. Our failure to enforce a provision is not a waiver of it.

20.4 Assignment. You may not assign these Terms. We may assign them in connection with a merger, acquisition, or sale of assets, or by operation of law, and they bind and benefit successors and permitted assigns.

20.5 Force majeure. We are not liable for any failure or delay caused by events beyond our reasonable control, including exchange outages, internet or hosting failures, third-party provider failures, acts of government, and natural disasters.

20.6 No third-party beneficiaries. These Terms create no rights in anyone other than you and us.

20.7 Export and sanctions. You represent that you are not located in, and will not use the Service from, a country or region subject to comprehensive U.S. sanctions, and that you are not a prohibited person under U.S. law.

20.8 Interpretation. Headings are for convenience only; “including” means “including without limitation.”

20.9 Notices to us. Notices to us must be sent to the addresses in Section 21.

21. Contact

Dream State Investments LLC (ZimmBot)

4128 N County Road 50 E, Logansport, Indiana 46947-8731

Email: support@zimmbot.com