> For the complete documentation index, see [llms.txt](https://docs.hyperbot.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperbot.network/risk-and-security/risk-disclosure-and-fund-security.md).

# Risk Disclosure & Fund Security

### Q: What is Hyperbot?

Hyperbot is an AI-powered, full-chain DEX perpetual trading gateway that provides data analytics, whale tracking, intelligent copy-trading, and strategy execution.

Hyperbot is an independent third-party tool and does not custody user funds.

***

### Q: Is my money safe when using copy-trading?

We recommend choosing the appropriate setup based on your capital size. The core principle is: the larger your funds, the more they should remain in your own account.

#### Small-scale usage

If you are just exploring copy-trading performance, we recommend starting with a small amount of capital to test and observe the system, and gradually increasing exposure once you understand the mechanism.

#### Large-scale trading

If you are trading with a larger amount of capital (over USD 10,000), we recommend creating an API wallet (also referred to as a proxy wallet) in your official Hyperliquid account and using it with Hyperbot.

In this setup, your funds always remain in your own Hyperliquid account. Hyperbot only executes trades according to your configured strategy and does not have access to your principal.

For key management, Hyperbot uses Turnkey’s non-custodial wallet infrastructure to ensure security at the foundational level.

That said, no software system can fully eliminate technical, operational, market, or third-party risks. Please allocate your capital according to your own risk tolerance.

***

### Q: What risks should I be aware of when using Hyperbot?

Using Hyperbot may involve, but is not limited to, the following risks:

* Smart contract risk — vulnerabilities or exploits in contract code
* System or service disruption risk — maintenance, downtime, or network failures may prevent strategy execution
* API or exchange interface risk — rate limits, interface changes, or failures on the exchange side affecting order execution
* Fund security risk — improper storage or leakage of private keys or API keys
* Copy-trading execution deviation risk — delays, slippage, or insufficient liquidity may cause execution differences from target wallets
* Market volatility and liquidation risk — extreme price movements may result in losses or forced liquidation
* Third-party service provider risk — failures in underlying infrastructure (such as Turnkey, Hyperliquid, etc.)

Past performance of any wallet, trader, or strategy does not guarantee future results. All trading decisions and their outcomes are solely the responsibility of the user.

***

### Q: What happens if something goes wrong?

We continuously invest in security and system stability to minimize the above risks.

For losses directly caused by Hyperbot’s own system failures or material negligence, the maximum compensation per individual customer is capped at 10,000 USDT.

However, losses caused by market volatility, liquidation, user error, key leakage, or failures of third-party service providers (including exchanges, Turnkey, Hyperliquid, etc.) are not eligible for compensation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hyperbot.network/risk-and-security/risk-disclosure-and-fund-security.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.