> For the complete documentation index, see [llms.txt](https://fordex.gitbook.io/fordex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fordex.gitbook.io/fordex/security-risk-warnings/disclaimer.md). # Disclaimer Fordex is a **trading tool, not financial advice**. All information and risk scores provided are intended to help traders make informed decisions, but Fordex does not guarantee accuracy or profitability. #### **Key Points** * 📌 **Non-Custodial** → Fordex never holds user funds. All trades are executed directly on-chain via decentralized protocols. * 📌 **No Guarantees** → Market data, AI scores, and risk checks are provided “as is.” * 📌 **User Responsibility** → Traders remain fully responsible for their actions and should conduct independent research (DYOR). * 📌 **Regulatory Note** → Users must comply with their local laws and regulations regarding cryptocurrency trading. By using Fordex, you acknowledge that you understand the risks of DeFi trading and accept full responsibility for your transactions. --- # 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://fordex.gitbook.io/fordex/security-risk-warnings/disclaimer.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.