Sign in with whichever method you registered with. Both lead to the same account: if you registered with an email address and later sign in with Google at that same address, it is one account, not two.

Two methods

• Email and password - the address and password you registered with.
• Google - one tap, no password to remember or type.

Google never asks for a password. There isn't one to enter - Google itself confirms who you are.

The prompt on the front page

If you are already signed into Google in that browser, Google may offer to sign you in without your going to the sign-in page at all - a small card of its own in the top right, naming the account it would use.

That card is drawn by Google, not by us. We do not see the account it offers unless you choose it, and choosing it lands you on your account page the same way the button on the sign-in form does. If two-factor is on, you are still asked for a code before you get there.

Three things worth knowing about it:

• It only appears on the front page and the pages around it - pricing, verify, terms and privacy. Never over this manual, and never once you are signed in.
• Closing it is remembered. Google stops offering it for a while, and for longer each time you close it. Nothing is lost by closing it - the sign-in page still works.
• It needs you to be signed into Google already. If you are not, there is nothing for it to offer and it never appears. This is not a fault, and there is nothing to fix.

If the sign-in itself fails after you choose the account, you get the same message as any other failed sign-in:

Something went wrong with that sign-in. Try again.

If email and password fails

A wrong address and a wrong password give the same message:

That email or password is not correct.

That is deliberate. Saying which half was wrong would confirm to anyone trying addresses at random whether a given email is registered at all.

One case is not a failure and does not get that message. If you registered and never typed the confirmation code, your email and password are both right and the only thing missing is that last step - so signing in sends a new code and takes you to the screen that accepts it, rather than telling you a password was wrong when it was not.

If you registered with Google

A Google account has no password to begin with - sign in with Google itself. If you want a password as well, Forgot it? sets one.

Unlinking your Telegram account never affects this, or any other way of signing in. Those are separate things: see Linking Telegram.

Resetting a forgotten password

Forgot it? on the sign-in form asks for your address and emails you a code. Whether or not the address has an account, it says the same thing:

If that address has an account, a reset code is on its way.

Then it takes two screens: type the code, and choose the new password. Splitting them means a wrong code fails before you have typed a password twice. The second screen names the address it is about, so you can check it before typing anything.

A password reset never touches your exchange keys or your risk caps. Changing the password changes the password and nothing else - your Bybit connection, your guardrails and your trade history are all where you left them. The screen says so too:

Exchange keys stay connected. A password reset never touches your API keys or your risk caps.

Changing a password you still know

Security, in the sidebar of your account, has a Change password card, for when you have not forgotten it and simply want a different one. It asks for the current password as well as the new one, and the current one is really checked - a wrong one is refused and nothing changes.

The new password follows the same rule as everywhere else: twelve characters minimum. Other devices are not signed out - there is no control for that yet, and the page does not pretend otherwise.

You stay signed in throughout. Checking your current password does not disturb the session you are already in - but if two-factor is on, you are asked for a code before the new password is saved, in a dialog over the form. A stolen password should not be enough to replace itself. The card says which of the two applies to you, beside the button.

An account created with Google has no password, so the card is not shown at all. If you want one, use Forgot it? on the sign-in screen and set it there.

If a code does not work

A code is single use, expires 15 minutes after it is sent, and asking for another one stops the previous one working. Most refusals are one of those three things, and the screen says so without pretending to know which:

That code did not work. It may have been mistyped, or it may have expired - and if you asked for a second email, only the newest code works.

That wording is careful on purpose. When a code is refused we are told only that it was refused, never whether it was wrong or out of time, so claiming one would sometimes be a guess at your expense - being told a code expired when you simply mistyped it sends you looking for an email you do not need.

Two cases we can be certain about, and say plainly. If the countdown on that screen has run out in front of you, it says the code expired. And if you have tried many times in quick succession:

Too many attempts - wait it out

Wait a while before asking for a new code - trying again straight away will not work. Nothing is wrong with your account.

A new code comes from Send a new code on the same screen, which counts down as Resend in 0:47 for the first minute after one is sent. Both codes work the same way, whether you are confirming an address or resetting a password.

Other sign-in failures

A sign-in through a provider that does not finish is reported on the sign-in page, in the same place, with one of three messages depending on where it stopped:

That sign-in did not come back complete, so nothing was signed in. Try again from here.

That sign-in could not be completed. Try again.

That sign-in finished without an account attached to it. Try again.

Next

Manage the Telegram link on this account - see Linking Telegram.