# Security ### Tower's approach to keeping user funds safe. #### Non-Custodial by Design Tower Exchange is fully non-custodial. At no point does Tower hold, control, or have access to user funds. Every transaction is signed client-side through the user's own wallet. Private keys never touch Tower's servers. #### Wallet Security Tower integrates wallet connections through Privy, Dynamic, and Circle, established providers with robust security track records. These integrations support a wide range of wallet types, including hardware wallets (Ledger) for users who require maximum security. #### Code Security Tower has completed manual code reviews of its smart contract and platform code. Smart contract audits by third-party security firms are planned and will be completed before mainnet launch. User funds are always under the user's control. Tower is a routing and aggregation layer, it identifies the best way to trade and routes swaps through optimal paths, but actual execution is always initiated and approved by the user through their own wallet. --- # Agent Instructions: 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: ``` GET https://tower-exchange.gitbook.io/tower-exchange/fundamentals/security.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.