# \[Archive\] Key Exportability on WaaS | Web3Auth

**URL:** <https://builder.metamask.io/t/archive-key-exportability-on-waas-web3auth/1444>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [April 2, 2024, 2:12pm UTC](https://builder.metamask.io/t/archive-key-exportability-on-waas-web3auth/1444 "2024-04-02T14:12:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [April 2, 2024, 2:12pm UTC](https://builder.metamask.io/t/archive-key-exportability-on-waas-web3auth/1444/1 "2024-04-02T14:12:33Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **shahbaz** on 4/2/2024.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

Web3Auth has offered a way for everyone to access and manage their wallets through simple authentication methods, such as email and social logins. What makes this approach self-custodial is that users retain complete control over managing their wallets, despite our SDKs abstracting away the processes of key and signature generation for them.

* * *
This is a companion discussion topic for the original entry at [https://blog.web3auth.io/key-exportability-with-web3auth-a-solved-problem-on-security-and-flexibility](https://blog.web3auth.io/key-exportability-with-web3auth-a-solved-problem-on-security-and-flexibility)