> For the complete documentation index, see [llms.txt](https://doc.rocky.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.rocky.exchange/trust-and-legal/security.md).

# Security

Rocky is **non-custodial** — you hold your own keys, and the exchange cannot move your funds without your signature.

## Protections

* **Independent audits** — smart contracts and critical systems are audited. *(Reports will be linked here.)*
* **Bug bounty** — security researchers can report vulnerabilities through our program.
* **Insurance fund** — backstops liquidation shortfalls (see [Margin & Liquidations](/perpetuals/margin-and-liquidations.md)).

## Your responsibilities

* Back up your **recovery phrase** offline; it cannot be recovered if lost.
* Verify you are on the official Rocky domain before connecting or signing.
* Review every signature request — reject anything unexpected.

{% hint style="danger" %}
Rocky will **never** ask for your password, recovery phrase, or private key. Anyone who does is trying to steal your funds.
{% endhint %}


---

# 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://doc.rocky.exchange/trust-and-legal/security.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.