> For the complete documentation index, see [llms.txt](https://support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.backpack.exchange/support-docs/es/legal/backpack-exchange-disclaimer-re-ftx-creditor.md).

# Backpack Exchange Disclaimer re: FTX Creditor

**Aviso Legal**

Backpack Exchange proporciona acceso a FTX Creditor únicamente como una conveniencia para nuestros usuarios. 

Backpack Exchange **no** respalda, apoya ni recomienda la venta o transferencia de ningún reclamo de FTX. No estamos afiliados con FTX Creditor y no hemos verificado de manera independiente la precisión, legitimidad o fiabilidad de sus servicios. Los usuarios interactúan con FTX Creditor completamente bajo su propio riesgo.

Backpack Exchange rechaza expresamente cualquier responsabilidad o obligación que surja de o esté relacionada con el uso de los servicios de FTX Creditor. Esto incluye, pero no se limita a, cualquier pérdida, error, retraso, disputa o reclamo que surja de o en relación con la plataforma FTX Creditor o tus transacciones con ella.

Por favor, realiza tu propia diligencia debida y consulta con tus asesores legales o financieros antes de proceder.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.backpack.exchange/support-docs/es/legal/backpack-exchange-disclaimer-re-ftx-creditor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.