> For the complete documentation index, see [llms.txt](https://uliquid-1.gitbook.io/uliquid-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uliquid-1.gitbook.io/uliquid-docs/security-and-risk-basics.md). # Security and Risk Basics The essential security and risk rules for every uLiquid Desk workflow. Use these rules before connecting an account, signing a transaction, placing an order, or starting a bot. ## Exchange API Security * Use the minimum API permissions required for the workflow. * Do not enable withdrawal permission for uLiquid Desk API keys. * Treat API keys and secrets as sensitive credentials; never paste them into chat, screenshots, or support requests. * Use exchange IP allowlists when available, and revoke or rotate exposed keys at the exchange. ## Wallet Security * Never share a seed phrase or private key. uLiquid Desk should never request either one. * Check the wallet, network, asset, amount, and target before every signature. * A wallet connection does not authorise arbitrary transfers. Each capital-changing action needs its own reviewed signature. ## Trading and Automation Risk * Cryptocurrency markets are volatile; leveraged positions can lose value rapidly. * Check live-data health, account selection, and open exposure before a new action. * Bots, grid settings, and AI tools do not eliminate market, execution, connectivity, or liquidation risk. * Treat a pending, degraded, or mismatched status as a reason to investigate, not to submit the action again. ## AI and Forecasts * AI output can be incomplete or incorrect. * AI analysis is decision support, not financial advice or execution authority. * Forecasts are probabilistic; historical results do not guarantee future outcomes. If an incident needs support, follow [Collect a Support Package](https://github.com/eds-labs/uLiquid-Desk/tree/main/docs/support/support-package.md). Never include secrets, seed phrases, private keys, or OTP codes. --- # 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://uliquid-1.gitbook.io/uliquid-docs/security-and-risk-basics.md?ask=&goal= ``` `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.