When login recovery fails, a new registration can look like the quickest route back. It can also create a duplicate identity, split deposits and trigger later account review. Recovery should prove ownership of the existing profile while protecting passwords and one-time codes from support impersonators.
01
Use the reset flow on the verified domain
Navigate to the exact domain already tied to the account and request one password reset. Check spam and filtered folders, then verify the message sender and destination before opening it. Do not use a reset page delivered by an unsolicited social message. If no email arrives, note the request time rather than sending many more.
02
Identify the old account with safe fields
Prepare the registered email, masked phone, approximate creation date and a recent masked transaction reference. Support can use these details without receiving the password, PIN or full payment credential. If the registered email is inaccessible, ask for the official ownership-change procedure and its document channel.
03
Treat an account lock as a security event
If the password changed unexpectedly or an unknown device appears, secure the email account first and change reused passwords elsewhere. Ask support to revoke active sessions and freeze payments until ownership is confirmed. Record the warning email and device information without clicking unfamiliar sign-out links.
04
Do not test access by registering again
A second account can complicate terms compliance and KYC. Keep one recovery case, answer requested checks in that thread and ask support to confirm the original player ID when access returns. Review profile details, payment methods and withdrawal history before resuming activity.
Check the current account screen and terms before taking the next material step.