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

# Privacy on Rocky

Rocky's privacy model is built on Canton.

## Selective visibility

Canton does not require every network participant to see every transaction. Participants receive the information they are entitled to see for a specific workflow.

For trading, this architecture can reduce the unnecessary exposure of:

* Account-level balances and settlement activity
* Position and collateral workflows
* Large transaction intentions
* Institutional counterparties
* RWA negotiation and settlement information

## Privacy does not mean invisibility

Privacy should not be interpreted as anonymity or the absence of controls.

Depending on the market and workflow:

* Counterparties and relevant service providers may see information required to execute and settle a transaction.
* Market-level information such as prices, order-book depth, volume, and aggregated activity may be visible.
* Compliance, audit, or legal requirements may require information to be disclosed to authorized parties.

Rocky's objective is to avoid unnecessary global disclosure while preserving the information required for execution, settlement, risk management, and applicable compliance.