> For the complete documentation index, see [llms.txt](https://docs.marinade.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marinade.finance/marinade-protocol/legal/terms-of-use-and-privacy-policy.md).

# Terms of Use and Privacy Policy

Terms of Use, Privacy Policy, and the legal terms governing use of the Marinade website and Services.

## Overview

The Marinade website and the Services made available through it are governed by the documents below.

{% hint style="info" %}
The use of any of our products and tools that can be made available from time to time is subject to and governed by our [Terms of Use](https://marinade.finance/terms-of-use). By accessing or using any of such products or tools, you confirm that you have read and understood our Terms of Use, agree to be bound by them, and that your use complies with all applicable requirements set out herein.

For information on how we collect, use, and process your personal data, please refer to our [Privacy Policy](https://marinade.finance/privacy-policy).
{% endhint %}

Our products and tools may not be available to users in certain jurisdictions. It is your responsibility to ensure that your use of the platform complies with applicable laws in your jurisdiction.

This platform is operated by Medium Rare Foundation, a foundation established in Panama.


---

# 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://docs.marinade.finance/marinade-protocol/legal/terms-of-use-and-privacy-policy.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.