> For the complete documentation index, see [llms.txt](https://docs.retro.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.retro.finance/resources/service-agreement.md).

# Service Agreement

When using Retro.Finance, fully read the agreement below. By using [www.retro.finance](http://www.retro.finance), you acknowledge that you understand how the site, it's Dapp and it's underlying protocol functions.

​

* Retro.finance is a Dapp interface that allows users to use their web3 wallet to interact with a decentralized protocol . It is the user's responsibility to carefully consider the benefits and risks related to using Retro.finance
* Expected return rates and token prices are estimations and not guarantees.
* Retro.finance is not responsible for user loss of assets, nor for generating profit that is less than projected, resulting from the use of Retro.finance
* Retro.finance does not guarantee the reliability of any blockchain used by Retro.finance , as well as any other 3rd party services.
* As in any Smart Contract, the code used in Retro.finance are susceptible to vulnerabilities, and risk of asset loss exists from hacks and exploits utilizing these vulnerabilities.
* It is the user's responsibility to carefully consider the benefits and risks related to using Retro


---

# 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.retro.finance/resources/service-agreement.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.