Project closure and data export

Embedded Wallets (Web3Auth)
,
1

As we are trying to close our project and shutdown our wallet that was using embedded wallets, is there a possible way for us to get the analytics data on the users and also is there a way for users to access their wallet after we shutdown our wallet product?

2

For analytics: the current public Embedded Wallets documentation explains how to view project analytics in the MetaMask Developer Dashboard, but it does not document a supported analytics export/download API or a post-closure data-retention/export workflow. If you need a retained record, please capture the dashboard metrics you need before disabling the project. Whether any additional project-level data can be retained depends on your project’s dashboard configuration and closure plan — let us know which metrics you need and your intended shutdown date, and we can advise further.

Dashboard analytics: Analytics | MetaMask developer documentation

For wallet access: please don’t disable authentication until users have had a migration/withdrawal window. A user’s ability to re-access an Embedded Wallet depends on the authentication setup that originally derived the wallet:

  • Built-in social login under your project client ID: users can continue accessing the same deterministic wallet only while you maintain a working login path using that client ID/configuration. You can keep a minimal migration app available so users can log in and move their assets. If you remove the login entirely, we cannot sign users in on your behalf.
  • Custom authentication (your custom verifier, JWT issuer, or configured identity provider): that identity system belongs to your project. We do not hold the issuer or verifier and cannot reproduce the login or restore wallets after it is removed.
  • If your users did not enroll an additional recovery/MFA factor, there is no independent factor to fall back on if the original login path becomes unavailable — meaning that login path is the only route back to the wallet.

Before closure, please notify users, preserve the applicable auth configuration, and provide a time-limited path for each user to authenticate and move/export their assets through your product. Never ask users to send seed phrases, private keys, or account passwords to anyone — and we will never ask for them either.

Could you confirm whether you’re using built-in social connections or a custom JWT/verifier, and whether you plan to keep a minimal login/migration application live? That will determine whether users can still access their wallets after the main product is shut down, and we can follow up here with more specific guidance once you confirm.

Sources

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

3

I want the wallet address, email ID, login method, 2fa method used if applicable, we need all these data for compliance to be maintained so we would like to export these data.

4

Current public Embedded Wallets documentation does not describe a project-level or bulk compliance export that returns wallet address, email, login method, and MFA/2FA status for every user.

For a closure/export plan, the practical approach is to build the record set from data you already control:

  • Wallet address: capture and store the address in your application after the user authenticates and the wallet becomes available.
  • Email and login method: these come from the authentication connection and the ID token. See User details in ID token and Authentication. For custom JWT connections, your own JWT issuer is the source of truth for user identity and authentication history — see Custom JWT Login with Embedded Wallets.
  • MFA/2FA method and enrollment state: this should be retained by whichever identity provider or MFA system performs it. It is not a documented Embedded Wallets project-user export field.

The Developer Dashboard lets you configure authentication connections and, separately, control whether users may export their own private keys (Key export settings). That setting is a per-user key-export permission, not a bulk user-data export facility.

If you also need to preserve privacy/consent records, the Consent screen documentation covers what is shown to users at social login.

So, before shutdown, generate the export from your application database and your authentication provider’s audit records, correlating each row with the wallet address you recorded. Do not collect or export users’ seed phrases, private keys, or passwords as part of this process.

If you’d like us to check whether your current implementation captures enough to build that export, reply here with: the authentication model in use (built-in social/email login vs. custom JWT), the connection/verifier name, and whether MFA is handled by your own identity provider. Please don’t share end-user credentials, private keys, or seed phrases.

Sources

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

5

Is there a way I can run on a free plan and build a small app were users can login and export the private keys anytime in future?

6

Yes—Embedded Wallets supports private-key export, and you can build an app where an authenticated user exports their wallet key at any time while your app and its login flow remain available. You enable and configure export permissions for your project in the MetaMask Developer Dashboard, then implement the export call in the SDK for your platform.

Key things to plan for:

  • Export requires the user to authenticate to the same project with the same login method they originally used. If the app or its login connection is removed before they export, no one—including us—can sign in on their behalf to retrieve the key.
  • This is especially important if you use a custom JWT/verifier or your own token issuer: wallets derived behind your verifier can only be reached through that verifier, so keep it running until all users have had the chance to export.
  • Expose export proactively (for example, in account settings) and give users a clear deadline well in advance of any shutdown.
  • Once exported, the user controls that key independently and is responsible for storing it safely. Never collect, log, transmit, or ask users to send you a private key or seed phrase—and we will never ask for one either.

On the Free plan specifically: the public docs confirm key export is a supported capability but don’t specify which plan tiers include the setting or any associated limits, so we can’t confirm Free-plan eligibility from the docs alone. Check the key export setting and your plan status for your project in the Dashboard: https://dashboard.web3auth.io

Docs:

Let us know which SDK/platform you’re building on (React web, React Native, Flutter, Node) and whether you’ll use built-in social login or your own JWT provider, and we’ll point you to the exact integration path.

Sources

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

7

Thank you for inquiring about this, seriously. I am a user trying to recover funds stuck in a web3auth wallet created through a deprecated app that used a custom UI through web3auth. No one is actually helping and what you are doing would prevent this from ever happening to anyone.

I wonder how much value is locked away because of this…