<!-- tempo-docs-context -->
> Source: [/docs/zones](https://tempo.xyz/developers/docs/zones.md)
> Section: [Zones](https://tempo.xyz/developers/docs/zones.md). Connect to a Zone and work with private balances, deposits, and withdrawals. Zones is in limited preview; see the introduction for access. Earlier testnet sandbox guides describe a separate integration.
> [Documentation index](https://tempo.xyz/developers/llms.txt) · [Docs skill](https://tempo.xyz/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.xyz/developers/llms.txt) and Markdown pages directly.

<span id="connect-public-and-private-balances" />

# Tempo Zones

Keep stablecoin balances and account activity in a private ledger connected to Tempo. Deposit funds from Tempo, read private balances, and withdraw to the public network.

[Read the privacy model →](https://tempo.xyz/developers/docs/zones/privacy)

A public deposit enters a private Zone account through a controlled boundary; the Zone operator can view its ledger.

:::warning
Zones is in limited preview. [Contact Tempo](https://tempo.xyz/contact) to discuss access and the deployment your application needs.
:::

<span id="understand-the-privacy-boundary" />

## How Zones work

Each Zone has its own network and a portal on Tempo that holds its backing assets. Account-scoped access lets your application read private balances and activity. The operator can read the ledger; deposit and withdrawal amounts remain public. Read [Privacy](https://tempo.xyz/developers/docs/zones/privacy) before choosing a deployment.

<span id="check-the-capabilities-of-your-deployment" />

## Supported features

The current permissioned runtime supports funding through the inbox and outbox. General TIP-20 transfers and user contract deployment are disabled. Confirm the operator's supported assets, signing tools, read access, and funding rules before integrating.

Execution-proof enforcement depends on the deployed verifier and network configuration. Review [proving and settlement](https://tempo.xyz/developers/docs/protocol/zones/proving) with the operator; forced exits are not a generally available recovery path.

<span id="integrate-a-zone" />

<span id="confirm-the-deployment-details" />

<span id="authenticate-private-account-access" />

<span id="deposit-from-tempo" />

<span id="read-the-private-balance" />

<span id="withdraw-to-tempo" />

## Start building

* [Connect](https://tempo.xyz/developers/docs/zones/connect) — Configure and authenticate access to your Zone.
* [Deposit](https://tempo.xyz/developers/docs/zones/deposit) — Fund a private account through the portal on Tempo.
* [Balances and activity](https://tempo.xyz/developers/docs/zones/balances) — Read the account's balances and filtered history.
* [Withdraw](https://tempo.xyz/developers/docs/zones/withdraw) — Return funds to Tempo and track delivery.

<span id="try-the-testnet-sandbox" />

The [testnet sandbox](https://tempo.xyz/developers/docs/guide/private-zones) has interactive examples for an earlier deployment, including direct transfers. Its interfaces and capabilities differ from the current preview. Use those examples only with the named sandbox deployment.
