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

# Why Privacy Matters

Why financial privacy and on-chain privacy matter on public blockchains.

Public blockchains leak more than most people expect. A single wallet address can expose your transaction history, counterparties, and token holdings to anyone, forever.

Financial privacy matters on-chain for the same reason it matters anywhere else. People and businesses need private transactions, not permanent public surveillance.

## Why On-Chain Privacy Matters

* **Personal Safety**\ <mark style="color:$info;">A public wallet balance can make you a target.</mark>
* **Front-Running**\ <mark style="color:$info;">Visible pending trades let bots move against you.</mark>
* **Business Confidentiality**\ <mark style="color:$info;">Treasury flows, payroll, and vendor payments should stay private.</mark>
* **Everyday Financial Privacy**\ <mark style="color:$info;">Your savings, salary, and spending habits should not be public data.</mark>

## Privacy Supports Legitimate Crypto Use

Privacy is not a loophole. It is a basic part of financial security.

Traditional finance does not publish your bank statement to the internet. Crypto should not force that tradeoff either.

Lacuna restores that baseline with private transfers, shielded balances, and selective disclosure. When you need to prove legitimacy, you can share [Viewing Keys & Selective Disclosure](/the-lacuna-wallet/viewing-keys.md) or use [Proof Of Innocence](/security-and-compliance/proof-of-innocence.md) as it rolls out.


---

# 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.lacunalabs.xyz/introduction/why-privacy-matters.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.
