# Security ## **Security of Wallet Address Keys** Your wallet addresses' keys offer the same level of security as asset keys. 1. The DeGate protocol and degate.com do not and cannot access users’ wallet private keys. 2. Wallet address keys are temporarily stored in the browser’s local SessionStorage and are automatically cleared when the browser tab is closed. SessionStorage does not support cross-domain or cross-session access, which makes it secure. 3. DeGate has implemented a front-end security isolation strategy by splitting the front-end into "wallet codes" and "trade codes". The wallet and trade codes are isolated: wallet code handles the signature mechanism within an iframe, while trade code executes in a sandboxed environment, ensuring the keys and signatures are secure and inaccessible from the trade side. In the future, the core front-end code will be deployed on decentralized platforms to make it immutable, further enhancing private key security. {% hint style="info" %} For submission of bug bounty reports, please contact us at {% endhint %} --- # 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://docs.degate.com/your-wallet/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.