> 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/privacy-policy.md).

# Privacy Policy

At Zup, we respect your privacy and are committed to being transparent about the data we collect and how we use it. This Privacy Policy outlines the type of information we collect, how it's used, and your rights as a user.

## 1. Data we collect

Zup is a non-custodial Web3 protocol that does not collect personal information such as your name, email, or ID. However, we may collect limited data through cookies, including:

* Browser type and version
* Operating system
*  IP address (anonymized where possible)
* Usage patterns on our website
* Connected wallet address (if you choose to connect)

## 2. How we use your data

We use the limited data we collect to:

* Optimize platform functionality and performance
* Understand and improve user experience
* Analyze platform usage trends
*  Ensure platform security and integrity

## 3. Cookies

We utilize cookies and similar technologies to enhance your experience. Cookies may be set by us or third-party services (e.g., Google Analytics). By continuing to use Zup, you consent to our use of cookies.

You may manage or disable cookies through your browser settings. Disabling cookies may affect your experience on the platform.

## 4. Third-Party Services

Zup may integrate with third-party tools and protocols, such as:

* Web3 wallets (e.g., MetaMask)
* Analytics tools (e.g., Google Analytics) 

These third parties may collect data according to their own privacy policies. We encourage you to review the respective policies of any external services you use. Zup is not responsible for the privacy practices or content of third-party providers.

## 5. Data Security

Although we do not store sensitive personal information, we implement reasonable administrative, technical, and physical safeguards to protect the limited data we do collect from unauthorized access, loss, misuse, or alteration.

### Legal Basis for Processing

Where applicable, our legal basis for processing limited personal data includes:

* Your consent (connecting a wallet, accepting cookies)
* Our legitimate interests (e.g., platform optimization and security)
* Data Retention

We retain anonymized and aggregated data only for as long as necessary to fulfill the purposes outlined in this policy or as required by applicable law.

## 6. Your Rights

As a user, you have the right to:

* Disconnect your wallet at any time
* Disable cookies via your browser settings
* Request access to or deletion of any data we may have (subject to limitations)- Contact us for questions about your data

## 7. Changes to this Policy

We may update this Privacy Policy as our product evolves. Any changes will be posted on this page with a revised date. Continued use of the platform constitutes your acceptance of the updated terms. 

By using Zup, you acknowledge that you have read, understood, and agreed to this Privacy Policy.

If you do not agree with our practices, please discontinue the use of Zup immediately.


---

# 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/privacy-policy.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.