> For the complete documentation index, see [llms.txt](https://docs.zirodelta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zirodelta.com/zidee-wallet/custody.md). # Custody This page answers the only question that matters in a wallet: **Can Zirodelta take my money?** The answer is no. The rest of this page explains exactly why, with the trust boundary made explicit. ## Self-custody by default Your keys are yours. Zidee gives you two Privy embedded wallets, one Solana and one EVM (Hyperliquid), and both sit inside Privy's Trusted Execution Environment. You hold your own ZDLT and wzdUSD, and every transfer is signed by you in the Privy modal. What you can do with your keys: * **Send / receive / swap ZDLT, USDC, SOL** on Solana. You sign every transfer. * **Withdraw your idle USDC** to an external wallet. You sign the withdrawal yourself, so the server has no permission to move your funds out: it prepares the payload, you sign it with your master key, and it only submits. * **Deposit and redeem (coming soon).** When the vault opens, you approve a USDC deposit and receive **wzdUSD**, your market-priced share of the pool, and you exit by redeeming that share back to USDC at its current value. Both open only after the vault's audit and legal review; you sign each yourself. * **Export your private key.** Settings → Export Key reveals the raw private key in a Privy modal so you can back it up or move it to another wallet provider. Privy's recovery model maps back to your Discord OAuth or email, so if you lose your phone you can sign back in from another device and reach the same wallet. Privy has been audited, is SOC 2 Type II certified, and is used in production by exchanges, games, and consumer crypto apps. *** ## How the Yield Engine trades without touching your money You never hand your funds to a person. When the vault is open, your USDC sits in the vault contract, and the [Yield Engine](/the-zirodelta-financial-engine/overview.md) runs a single delta-neutral position for the whole **pool**, not a separate one per user. Two facts make that non-custodial by construction: * **The withdraw-capable key is off-server.** The one key that can move funds out of the pool's Hyperliquid account is held off-server. No always-on machine can sign a withdrawal. * **The server holds only a trade-only key.** To run the strategy, the server signs with a Hyperliquid agent key whose authority is capped by the protocol itself: it can place, cancel, and close the pool's orders, and Hyperliquid L1 rejects any withdraw or transfer signed by it. So the worst a full server compromise can do is trade the pool badly. It cannot move a dollar off the pool's account, and it can never touch your own wallet. The ceiling on the damage is trading losses, never theft. This is a protocol-level boundary, not a contractual promise. ## The deposit rail When you deposit USDC, a Privy-policy-locked signer forwards it along the single route you authorize, and that is the only thing it can do. It cannot send your USDC anywhere else, cannot touch any other token, and cannot sign withdrawals. Privy enforces the policy server-side. You can revoke the delegation at any time from Privy's dashboard, or by exporting your key and rotating to a fresh wallet. ## Revocation You can pull every authorization at any time: * **Withdraw your idle USDC** to an external wallet at any time, signed with your own master key. There is no queue only Zirodelta can release. (Redeeming your wzdUSD share back to USDC opens with the vault.) * **Bridge delegation:** revoke from Privy's dashboard, or rotate to a new wallet. * **Privy session:** log out from Settings or wipe local storage on the device. There is no "support ticket" path Zirodelta needs to involve. Every authorization lives on protocols and providers you control directly. ## What Zirodelta sees Read-only access: * Your **vault share** balance and its current value. * Your Solana SPL balances for ZDLT, USDC, SOL (via public RPC). * Your Arbitrum USDC and ETH balances (via public RPC). The pool's own delta-neutral position is public on the [transparency page](https://wallet.zirodelta.com), not a private view into your account. Everything Zidee shows you is a re-render of what your own RPC calls would return. No privileged access to anything. *** The vault opens to user funds only after an independent security audit **and** a legal review. Until then the strategy is proven on the founder's own capital on a public address, and nothing here is open to user deposits. See [Vault Overview](/vault/overview.md). > **See also:** [Overview](/zidee-wallet/overview.md) · [Tiers](/zidee-wallet/tiers.md) · [Getting Started](/zidee-wallet/getting-started.md) · [The Yield Engine](/the-zirodelta-financial-engine/overview.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.zirodelta.com/zidee-wallet/custody.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.