> For the complete documentation index, see [llms.txt](https://docs.clique.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clique.tech/clique-wallet/features-and-capabilities/export-private-keys.md). # Export Private Keys Clique Wallet provides a secure export functionality that allows users to export their private keys, ensuring users maintain full control and ownership of their assets. #### Export Process The export process uses a two-step verification mechanism: 1. **Initiate Export**: Request to start the export process, which generates verification information 2. **Complete Export**: Provide the verification information to complete the export and receive the private keys This two-step process ensures that only authenticated users can export their keys and prevents unauthorized access. #### After Export Once a user exports their private keys: * The account is marked as exported * **By default**, Clique Wallet will no longer sign transactions for exported accounts * Users can still view their account information * This is the default security measure to prevent unauthorized use after export **Re-enabling Signing After Export:** If necessary, signing can be enabled even after exporting private keys. However, it's important to note that in this case, the private keys are not as secure as before. Since the private keys have already been exported and are outside the TEE, Clique Wallet cannot ensure the same strict security guarantees as when keys remain exclusively within the TEE. Users should carefully consider the security implications before re-enabling signing for exported accounts. #### Export Use Cases * **Migration**: Move wallets to another service or self-custody solution * **Backup**: Create a backup of private keys for disaster recovery * **Self-Custody**: Transition to full self-custody while maintaining access to exported keys --- # 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.clique.tech/clique-wallet/features-and-capabilities/export-private-keys.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.