> 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/key-management.md).

# Non-Custodial Key Management

Lacuna is built so that only you can ever access your funds.

## Keys Live On Your Device

Your private keys and shielded note secrets are generated locally and stored in your device's secure storage. They never leave the device in any form.

## PIN-Protected Access

Access to the wallet is gated by a PIN, used on-device to unlock your keys. It is never transmitted to any server.

## No Server Custody

There is no custodial backend. Lacuna's infrastructure, such as the relayer, only ever handles the minimum data needed to help broadcast a transaction, never anything that lets it spend your funds.

> **Note:** Continued hardening of on-device key storage and fully on-device proof generation are tracked on the [Roadmap](/resources/roadmap.md). The current security model is documented under [Security & Audits](/security-and-compliance/security-and-audits.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/key-management.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.
