> For the complete documentation index, see [llms.txt](https://stealf-fi.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stealf-fi.gitbook.io/docs/the-stealf-app/private-balance.md).
# Private balance
Your private balance shows and manages the funds you hold in Umbra's shielded pool. Amounts and activity here are not readable onchain.
#### One-time registration
Before using the private layer, you register once on the Umbra protocol. You'll be asked to sign a message with your wallet's master seed: this signature registers your wallet on Umbra (so you can receive private transfers) and confirms your acceptance of the terms of use.
#### Shield
Moves funds from your public balance into the shielded pool. This transaction is **public**: anyone can see that your address deposited into the pool, and how much. Once inside, the trail stops.
#### Unshield
Moves funds from the shielded pool back to your public balance. Also a **public** transaction: the exit amount and destination address are visible onchain.
> **Good to know** — Shielding and unshielding are the two visible edges of the private layer. Timing and amounts can be correlated: shielding 500 USDC and unshielding exactly 500 USDC to the same address shortly after weakens your privacy. Varying amounts and timing preserves it.
#### Private send
Sends funds from your private balance to another Umbra user. The transaction is **unlinkable**: no onchain connection exists between sender and receiver. The recipient must be registered on Umbra, and claims the transfer into their own private balance.
#### Incoming transfers
The scan icon (top left) checks for private transfers sent to you. Detected transfers are claimable directly into your 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://stealf-fi.gitbook.io/docs/the-stealf-app/private-balance.md?ask=&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.
