> For the complete documentation index, see [llms.txt](https://zupprotocol.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zupprotocol.gitbook.io/documentation/legal/terms-of-use.md).

# Terms of use

Welcome to Zup, a decentralized protocol designed to facilitate the analysis and selection of liquidity pools across Web3 ecosystems. By accessing and/or using Zup, you agree to the following Terms and Conditions:

## 1. Use of the protocol

Zup operates as an interface that enables users to interact with third-party smart contracts (e.g., DEXs) for liquidity provision. We do not execute or intermediate any transactions on behalf of users and never have access to user funds. All interactions occur directly between the user and the external protocols.

## 2. Risks

Using DeFi protocols involves inherent risks, including capital loss, smart contract vulnerabilities, and market volatility. Zup does not provide financial advice, guarantees, or assume any responsibility for losses incurred through use of the protocol. Users acknowledge and accept full responsibility for these risks.

## 3. Data and Information

Zup aggregates and displays information from various sources and protocols to support users in making informed decisions. We do not guarantee the accuracy, timeliness, or continuous availability of this information. Users are encouraged to conduct their own research ("DYOR") and independently verify information before making any decisions.

## 4. Wallets and Security

Zup does not store private keys or access connected wallets. Users are responsible for ensuring they are using the official site and for maintaining the security of their devices, wallets, and associated credentials.

## 5. Changes and updates

Zup is under active development and may modify or update features, terms, or interfaces at any time without prior notice. Continued use of the protocol constitutes acceptance of such changes.

## 6. Limitation of Liability

In no event shall Zup, its affiliates, or its partners be liable for any indirect, incidental, special, consequential, or punitive damages, including but not limited to loss of profits, data, goodwill, or other intangible losses, arising out of or related to your use of or inability to use the platform.

## 7. Regulatory Compliance

Users are solely responsible for ensuring that their use of Zup complies with all applicable laws and regulations in their jurisdiction. Zup does not guarantee that its services are appropriate, available, or lawful for use in all locations. We expressly disclaim any responsibility for users' non-compliance with local laws.

## 8. Jurisdiction

Zup is a decentralized protocol developed and operated by a company that is legally incorporated. While the protocol itself is non-custodial and decentralized, the company behind Zup is subject to the laws and regulations of its jurisdiction of incorporation. Users are solely responsible for ensuring that their use of Zup complies with applicable laws and regulations in their country.

By continuing to use Zup, you confirm that you have read, understood, and accepted these terms and Conditions.


---

# 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://zupprotocol.gitbook.io/documentation/legal/terms-of-use.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.