> 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/the-lacuna-wallet/viewing-keys.md).

# Viewing Keys & Selective Disclosure

Prove your activity to whom you choose read-only.

Privacy by default doesn't mean you can never prove anything. Lacuna gives you viewing keys, read-only keys that reveal your activity to a chosen party, without giving them any ability to spend.

## What A Viewing Key Does

A viewing key lets someone *see* your shielded transactions  an auditor, an accountant, a regulator, while your spending keys stay private and on-device.

## You Stay In Control

* Sharing is **opt-in:** Nothing is disclosed unless you choose to share it.
* It's **read-only:** A viewing key can never move your funds.
* It's **scoped:** You decide who gets it.

```ts
// Generate a read-only viewing key to share with an auditor
const viewingKey = await wallet.exportViewingKey();

// The holder can view — but never spend
const history = await LacunaViewer.getHistory({ viewingKey });
```

This is the foundation for [Compliance Integrations](/security-and-compliance/compliance-integrations.md) and the planned [Proof Of Innocence](/security-and-compliance/proof-of-innocence.md).


---

# 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/the-lacuna-wallet/viewing-keys.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.
