You sign in to Enta with the passkey on your device, and your email address is how we reach you and how recovery starts. So the question behind this one is really: what happens if you lose access to that inbox, or to the device holding your passkey?
That's what your recovery email is for — and it's why we ask you to put it on a different provider from your main address.
The fast path
If you're still signed in somewhere — another browser, another device — start there. And if your passkey syncs through your password manager or platform keychain, setting it up again on a new device is straightforward, with no waiting period.
Assisted recovery
If you've genuinely lost access, recovery runs in three steps.
Verify who you are. Using your registered recovery contact and an identity check.
A mandatory 72-hour security wait begins. You're notified as soon as the request is made, and you can cancel it with one tap from anywhere you're still signed in. The wait can be extended if we detect something suspicious.
Access moves across. Same wallets, same balances, same addresses, same history. Nothing moves — only how you get in changes.
Why the wait exists
Without it, anyone who compromised an email account could quietly take over the Enta account attached to it. The 72 hours is your window to notice and stop it, and it can't be shortened or waived — not by you, and not by us.
Recovery can only request a change of access. It can't move your funds, and you can veto it.
What to do before you ever need this
Keep your recovery email current, and on a different provider from your main one.
Keep a session open somewhere other than your primary device.
Set up a second way in. A device where you're already signed in, or a passkey that syncs through your password manager, is the difference between a two-minute fix and a three-day wait.
What this is not
Recovery restores access to your Enta account. It isn't a way to reverse a payment you've already approved, and it isn't a way to retrieve funds sent to a wrong address — see Sent to the wrong network? What to do next for that.