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

# Data scoping

> Sandbox and production are completely separate sets of data. Switching modes shows you the other set — you never see a mix.

Sandbox and production are fully isolated. Every wallet, transaction, bank account, identity verification, API key, webhook, and username belongs to one mode or the other. Switching the mode toggle shows you the other set — you never see data from both modes at the same time, and data from one mode can never affect the other.

## What is scoped per mode

| Data                             | Per mode? |
| -------------------------------- | --------- |
| Wallets and deposit addresses    | Yes       |
| Transactions and offramp history | Yes       |
| Bank accounts                    | Yes       |
| Identity verification (KYC)      | Yes       |
| API keys                         | Yes       |
| Webhooks                         | Yes       |
| Usernames / handles              | Yes       |

Your sandbox wallet has its own address. Your production wallet has a different address. Depositing to one does not affect the other.

## What is shared

Your account — the login email you signed up with — spans both modes. You use the same email to log in regardless of which mode you're using, and your account email is what Veil uses to reach you for support.

## Worked example

**"I claimed `@you` in sandbox. Do I own it in production?"**

No. Usernames are per-mode. If you claimed `@you` in sandbox, that handle is yours in sandbox. It may or may not be available in production — claim it there separately from Settings while the dashboard is in Production mode.

## See also

* [Sandbox vs. production](/concepts/sandbox-vs-production) — the full isolation model and common pitfalls
* [Mode toggle](/developers/production/mode-toggle) — how switching modes changes what you see
* [Usernames](/concepts/usernames) — per-mode handle ownership