A MetaMask user has reported a potential security concern after installing the wallet on a new Chrome profile. The user, identified as @tayvano_, detailed the process of setting up a new MetaMask wallet using Google OAuth and generating a new seed phrase. Upon importing an old seed phrase or private key, the user discovered that the information appeared to be sent, albeit encrypted, to web3auth.io. This incident raises questions about the handling of sensitive data during the wallet setup process.