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

# Withdrawals

> Exit in-app through the same account that deposited — and what never happens.

Withdrawals are built and executed in-app through the same account that deposited:
the app constructs the protocol's redeem/withdraw call (including protocol-specific
routes where a position token must be swapped back to a base asset) and the user signs
it. This matters especially for email/Google users, whose smart account is driven by the
app — they are never stranded needing a protocol's own interface to exit.

Withdrawal *speed* is a property of the vault, not of Atlas: instant vaults exit
immediately; queue/cooldown vaults exit on the protocol's schedule. This is exactly what
the [Liquidity pillar](/score/pillars-and-factors#pillar-3--liquidity) scores and what
the [tier policy](/engine/tier-policy) caps.

## What never happens

* **No pooling:** user funds are never commingled with other users' or with Atlas's.
* **No discretionary movement:** Atlas has no key, no allowance, and no permission that
  would let it move user funds.
* **No hidden legs:** every transaction the user signs is shown before signing, and every
  leg's outcome is verifiable on-chain.