> For the complete documentation index, see [llms.txt](https://docs.kyte.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyte.sh/legal/privacy.md).

# Privacy policy

What data kyte.sh handles, and what it does not.

*As shown on kyte.sh/privacy. Last updated 30 October 2026.*

**What we collect.** The website does not use accounts, cookies for tracking, or analytics. When you connect a wallet, your public address is used in your browser to read your positions. It is not stored by us.

**Wallet connection.** The wallet picker is provided by Privy. Only wallets already installed in your browser are shown. Privy processes your public address under its own privacy policy.

**On chain data.** Every transaction you send is public on Robinhood Chain and is indexed by our indexer to show the order book, proof of fee splits and burns. This data is public by nature and cannot be deleted.

**Third parties.** The site talks to a Robinhood Chain RPC endpoint and to our indexer. No advertising networks are loaded.

**Contact.** Questions about this policy can be sent to the Kyte team through the links in the footer.


---

# 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.kyte.sh/legal/privacy.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.