> For the complete documentation index, see [llms.txt](https://docs.hipersnipe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hipersnipe.com/legal/disclaimer.md).

# Disclaimer

**We are not responsible for any loss of funds, damages, or other liabilities resulting from the use of this software or any associated services.**

HiperSnipe is provided for **educational purposes only** and does not constitute financial advice.

## Risks

* Cryptocurrency trading involves substantial risk of loss
* Smart contracts and tokens may contain bugs, rugs, or honeypots
* RPC providers, Jupiter, Pump.fun, and Jito may fail or return stale data
* Automated systems (shields, limits, snipers) may execute at unintended prices
* Software bugs may cause missed trades or incorrect PnL display

## Your responsibility

* Use a dedicated wallet with only funds you can afford to lose
* Verify every transaction on [Solscan](https://solscan.io)
* Understand slippage, MEV, and liquidity risks before trading
* Keep `.env` and `secure_storage/` secure

## No warranty

This software is provided "as is" without warranty of any kind, express or implied.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.hipersnipe.com/legal/disclaimer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.