> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chance.cc/llms.txt
> Use this file to discover all available pages before exploring further.

# What stays private

> What onchain privacy covers, and who still needs access to your data.

Starknet private balances use a privacy pool. They reduce the link between your wallet and later spending. Public transfers, timing and amounts can still reveal information.

| Activity | What can remain public |
| - | - |
| Entering the pool | The source transfer, amount and deposit activity. |
| A private swap | The traded pair and amount on public liquidity. |
| Leaving the pool | The public recipient and amount. |
| A cross-chain bridge | The source and destination chain transactions. |

## Who can read more

Chance and the services used to scan balances or prepare private actions process the data needed to do that work. The pool also has its own viewing and audit model. “Private” here does not mean hidden from Chance or every service involved.

An AI provider receives the messages and tool results needed for your request. Private wallet activity discussed in chat is still part of that conversation.

## Keep your choices explicit

Ask for a **private balance**, **private transfer** or **private swap** when that is what you want. The agent should keep that choice through the workflow and explain when a destination is public.

A transaction's privacy is separate from [private verification records](/concepts/private-records), which concern how Chance check receipts are stored.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.