Secure an exchange account by protecting its login and recovery channels, enabling supported strong authentication, reviewing devices and connected access, and checking withdrawal controls. Treat every request that can reset access or move money as a separate authorization to verify.

Map the routes into your account

Start with the password, email, phone, authentication methods, and any connected identity service used by the account. Security depends on the weakest usable route, including recovery. A strong login method can coexist with an outdated recovery contact.

Open the security settings through the official application. Review the methods currently enabled rather than relying on what you remember setting up. A previous phone or spare key may still appear, or a new method may have been added.

Check the email account that receives security notices. Protect its authentication and recovery settings, and inspect unfamiliar sessions. An exchange review cannot fully protect an inbox controlled by someone else.

Write a nonsecret inventory of dependencies: which device holds the authentication method, which contact receives alerts, and where official recovery instructions are available. Keep passwords, backup codes, and enrollment secrets out of that ordinary note.

AccessRecoveryMoney movement
Account protection must cover ordinary access, recovery authority, and the controls used to move money.

Strengthen authentication without losing access

Use an account-specific password and a supported method appropriate to your setup. Passkeys, security keys, and authenticator codes have different storage and recovery requirements. Read how the provider implements the method rather than assuming every device works identically.

Add a supported backup arrangement before retiring working access. Test the new method through a controlled login or documented verification flow. A successful enrollment screen should be followed by an understanding of how you would recover after a lost device.

Inspect which methods remain enabled. Some providers allow several alternatives, while others change the set when you enroll a new method. An unexpected fallback can affect the protection you thought you selected.

Read what every prompt authorizes. A login, new device, withdrawal, and security-setting change are different actions. Do not approve an unexpected request because a caller says it is needed to stop an attack.

If authentication fails, use the official troubleshooting and recovery process. Sending codes or granting remote access to a private helper can turn an access problem into a compromise.

Review connected sessions and automation

Inspect active devices and sessions if the platform exposes them. Remove access you no longer use through the documented controls. A location label can be approximate, so investigate an unfamiliar entry rather than treating one geographic mismatch as proof by itself.

If you created API credentials, review each credential's purpose and permissions. Trading, reading balances, and withdrawing can have different scopes. Keep only the access required by the application you intentionally use.

Store API secrets through a method suitable for sensitive credentials, and remove unused integrations. Deleting an application from a phone does not necessarily revoke access held by an external service. Use the exchange's credential controls.

Review browser extensions and devices used for account access. An unnecessary extension or compromised environment can affect what you see and approve. Install updates and applications through official channels.

Keep personal and shared access arrangements within the provider's supported model. Handing someone your login makes it harder to determine who authorized an action and can violate account rules.

Put checks around money movement

Inspect withdrawal-address controls and confirmation options offered by your provider. An allowlist or newly added-address delay can add useful checks, but understand its setup, recovery implications, and exceptions.

Before saving an address, verify the asset, network, recipient, and memo where required. A saved label is a convenience record, not proof that the destination will remain compatible forever.

Monitor alerts for new destinations, changed credentials, and withdrawals. Read them by opening the official account independently. A fraudulent alert can imitate the very notification you expect to use for security.

Keep only the balances needed for your chosen custody plan. Moving assets to self-custody introduces its own recovery and signing responsibilities, so make that a deliberate decision rather than an emergency reaction to a generic warning.

If the platform offers additional transfer protections, read which transactions they cover. Do not expand a narrow control into an assumption that every possible withdrawal or account change is blocked.

Run a short account review

  1. Open the official security settings and confirm ownership of all contact and recovery channels.
  2. Check enabled authentication methods and verify that your backup access remains usable.
  3. Review sessions, connected services, and API credentials. Remove obsolete access using the provider's controls.
  4. Inspect withdrawal destinations and any available protective settings. Verify saved details before treating them as trusted.
  5. Check recent account activity and alerts. Reconcile anything unexpected with actions you actually performed.
  6. Save the official incident and recovery route in a nonsecret reference so you can find it under pressure.

If something suspicious has already happened

Use a trusted device and open the provider independently. If the service offers an account-lock or compromise-reporting function, follow its official instructions. Protect the associated email and other recovery channels as part of the response.

Identify what was exposed or changed. A password disclosure, unauthorized session, suspicious API key, and confirmed withdrawal require different evidence and next steps. Preserve times, references, and notices without sending secrets into a report.

Do not continue a conversation with an unsolicited helper who demands more money to recover the account. Reopen authenticated support yourself. Public transaction knowledge or a realistic case number does not prove someone represents the exchange.

After access is restored, inspect pending transfers and retained integrations. Changing a password does not automatically answer every question about active permissions under every provider's model.

Security is an ongoing configuration you can inspect. Repeat the review after device changes, recovery updates, integration changes, or a suspicious event, and verify each later money-moving action on its own merits.

Schedule the review around meaningful changes rather than a vague promise to check someday. A new phone, changed email, added automation service, or updated withdrawal destination is a concrete trigger. Record the date and what changed without copying sensitive credentials. If another person helps you understand the settings, keep control of the device and perform the authorizations yourself. The helper can explain a public guide while you inspect the actual account. This preserves responsibility for changes and avoids turning ordinary assistance into an unnecessary shared-access arrangement.

Reader questions

Does KYC completion secure my login?

Identity verification and access control have different roles. Keep authentication and recovery channels protected after approval.

Does deleting a trading bot revoke its API key?

Check the exchange's credential settings. Removing local software does not establish that a credential is disabled.

Should support ask for my current one-time code?

Do not disclose codes to private contacts. Use the provider's official authentication and recovery interfaces to authorize actions yourself.

Sources and further reading