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

# Why Financial Privacy

Stellar transactions are public by design. That makes settlement independently verifiable, but it also makes balances, counterparties, amounts, and timing available for permanent analysis.

For a consumer, this can expose income and spending. For a company, it can expose payroll, suppliers, treasury policy, and deal flow. For a trader, it can expose positions and execution strategy. Privacy here is not secrecy from the rules of the system; it is protection from unnecessary public disclosure.

## Privacy with verifiability

Vayyl separates two questions:

1. **Is this action valid?** The network should be able to verify conservation of value, authorization, and non-duplication.
2. **Which private facts produced it?** The network does not need every note, balance, or strategy detail to answer the first question.

Zero-knowledge proofs bridge the two. A proof can establish that inputs exist, belong to the spender, have not been spent, and balance against outputs—without exposing the private witness.

## The practical goal

The goal is not to make public settlement disappear. Shielding and unshielding still cross a public boundary. The goal is to let value remain useful inside a private state for long enough that users do not need to reveal a public trail for every intermediate action.

That is why Vayyl extends beyond one deposit and one withdrawal. Private transfers, change notes, positions, orders, and application payouts all increase the utility of staying inside the private balance.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vayyl.gitbook.io/vayyl-docs/why-privacy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.