<!-- tempo-docs-context -->
> Source: [/docs/protocol/zones/accounts](https://tempo.com/developers/docs/protocol/zones/accounts.md)
> Section: [Zones](https://tempo.com/developers/docs/zones.md). Connect to a Zone and work with private balances, deposits, and withdrawals. Zones is live on Mainnet; see the introduction to set up a Zone. Earlier testnet sandbox guides describe a separate integration.
> [Documentation index](https://tempo.com/developers/llms.txt) · [Docs skill](https://tempo.com/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.com/developers/llms.txt) and Markdown pages directly.

# Accounts and Privacy

A Zone keeps your balance and account activity private from other users.

## Overview

Zone privacy has two layers. RPC requests authenticate your Tempo account. Contract execution then restricts which balances and allowances that caller can read. Together, they enforce the account-level part of the [Zone visibility model](https://tempo.com/developers/docs/zones/privacy).

An account signs an authorization token for account-scoped RPC access. The RPC sends contract calls from that account. At the token contract, balance reads require the balance owner; allowance reads require the owner or spender.

The [RPC](https://tempo.com/developers/docs/protocol/zones/rpc) scopes transactions and event logs to your account. It blocks raw storage reads such as `eth_getStorageAt`. Contract-level caller checks prevent an `eth_call` from exposing another account's balance.

## Private Balances

Anyone can read any account's balance on public Tempo. A Zone enforces caller restrictions on TIP-20 `balanceOf(address)`:

* If `msg.sender == account`, the call succeeds and returns the balance.
* Otherwise, the call reverts with `Unauthorized()`.

These checks also apply to sequencer-signed getter calls. The Zone operator can still inspect the underlying node state. Account privacy doesn't hide balances from your operator. A contract on the Zone can't read and emit another account's balance.

## Private Allowances

The `allowance(owner, spender)` function is similarly restricted:

* If `msg.sender == owner` or `msg.sender == spender`, the call succeeds.
* Otherwise, the call reverts with `Unauthorized()`.

A non-zero allowance reveals a relationship between `owner` and `spender`. Restricting reads to those two parties preserves TIP-20 approval flows. It doesn't expose the allowance to other accounts.

## Other Account Reads

Public views like `totalSupply()`, `name()`, `symbol()`, and `decimals()` remain unrestricted. Some account-specific reads are restricted to their account owner:

* Permit nonces.
* `NonceManager` nonces.
* `AccountKeychain` key and spending-limit reads.

<span id="related-specifications" />

<span id="related-execution-rules" />

## Execution Rules

Zones reject public TIP-20 transfer calls with `Unauthorized()`. Token movement uses the inbox and outbox. Approval and permit calls remain available.

Zones also charge [fixed gas costs](https://tempo.com/developers/docs/protocol/zones/execution#fixed-gas-costs) for selected TIP-20 operations. These prevent gas-based side channels.

Zones currently [disable contract creation](https://tempo.com/developers/docs/protocol/zones/execution#contract-creation-disabled) (`CREATE` and `CREATE2`).

## Related

[Privacy](https://tempo.com/developers/docs/zones/privacy): Covers who can see Zone data and the trust assumptions behind it.

[RPC Reference](https://tempo.com/developers/docs/protocol/zones/rpc): Covers authorization tokens, method scoping, response redaction, and event filtering.

[Execution and Gas](https://tempo.com/developers/docs/protocol/zones/execution): Covers fee tokens, deposit and withdrawal fees, fixed gas costs, and token management.
