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

# Disclosures

## Terms of Use

{% embed url="<https://www.eclipse.xyz/terms>" %}

## Privacy Policy

{% embed url="<https://www.eclipse.xyz/privacy-policy>" %}

## Cookie Notice

{% embed url="<https://www.eclipse.xyz/cookie-policy>" %}

## Responsible Disclosure

Our [bug bounty](/developers/eclipse-bug-bounty-program.md) is now listed on Immunefi. Start taking a look and wait for the launch to report vulnerabilities!

* Do not disclose vulnerabilities publicly or by executing them against a production network. If you do, not only will you be putting users at risk, but you will also forfeit your right to a reward.
* Do not disclose the vulnerability publicly, for example by filing a public ticket or Github issue.
* Do not test the vulnerability on a publicly available network, either the testnet or the mainnet.


---

# 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.eclipse.xyz/developers/additional-resources/disclosures.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.