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

# Privacy

WCM is a fully lit order book, which means all orders are visible by defualt. Traders also have full visibility into the portfolios of their counterparties at all times.

On-chain privacy solutions have evolved over nearly a decade and will continue to improve as zero-knowledge research becomes increasingly advanced. WCM does not provide any built-in privacy solution as we believe it is outside the scope of the the core smart contracts. However, WCM is fully on-chain, which means every provider the industry with privacy services for EVM networks can integrate with WCM as easily as Uniswap or Curve.

If you have a preferred provider, or would like a recommendation, please reach out to us.


---

# 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.world.inc/venue/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.
