Account security

Your account is safest when platform controls and careful habits work together. Review the available settings during onboarding and report unfamiliar activity promptly.

Multi-factor authentication

Enable a second authentication factor where the account supports it, preferably an authenticator app. Store recovery codes offline and never read a one-time code to a caller. If access is lost, use the documented recovery route rather than a link in an unsolicited message.

A second factor should be activated before money is placed in an account, if the provider offers it. An authenticator app is usually less exposed to mobile-number takeover than text messages, although the available methods depend on the system. Save backup codes in a protected place that is separate from your normal sign-in device.

A recovery request should be treated as a sensitive account change. The provider may need to verify identity and temporarily limit activity while access is restored. If someone asks you to read out a code for an alleged security check, end the conversation and contact support independently.

Encryption and data handling

Sensitive information should be protected in transit and at rest by the systems that process it. Ask which provider holds identity records and how access is restricted, since encryption does not prevent misuse of a stolen password.

Transport protection helps keep data from being read while it passes between your browser and the service. At-rest protection concerns stored records and should be combined with access limits, monitoring and responsible handling by staff and providers. Ask where identity documents are submitted and who processes them.

Encryption does not fix an unsafe device or a fraudulent site. Check the exact address and the secure upload process before sending information. If you are asked to email a document to an unfamiliar address, verify the request through the published support channel first.

Fraud and phishing

Use the published domain and contact address when checking a message. A genuine support request should not ask you to disclose your password or transfer funds to a personal wallet to unlock an account.

Attackers may copy a logo, use a near-match domain or claim an urgent compliance hold to pressure a payment. Their messages can appear inside a genuine conversation if an email account has been compromised. A request to install remote-control software or move funds to a new wallet should be considered particularly suspicious.

Confirm a payment or security instruction using a contact route you already know, not the number or link in the unexpected message. Report the full sender address and web address so the support team can investigate. Never use an alleged account protection payment as a way to resolve a withdrawal delay.

Login alerts

Review notifications of new-device sign-ins, password changes and unusual activity if available. Contact support using a known address when an alert does not match something you did.

An alert is useful only if you can distinguish a genuine message from a false one. It should describe the event without asking for a password or one-time code. A location shown in an alert can be approximate because network routing and VPN services affect it.

Compare the time and device with your own activity. If the event is unfamiliar, go directly to the known site, review sessions and change credentials. Preserve the alert so support can check the underlying sign-in record.

Devices and sessions

Sign out on shared devices and review active sessions in account settings where that feature exists. Revoke access you no longer recognise and update your password after a suspected compromise.

A session can remain active on a device after the initial login. Shared computers, repaired phones and lost tablets therefore need particular attention. Where the account shows a session list, review it after travel or a device change and terminate any session you no longer need.

Set a screen lock on every device used for the account and install security updates. Logging out of a browser is only one control; a compromised email account or saved password can still put access at risk. Tell support promptly if a device containing account access is lost.

Account recovery

Recovery can require identity verification to prevent an attacker from taking over the account. Provide documents only through the confirmed secure channel and expect temporary restrictions during an investigation.

A legitimate recovery process balances access with protection against impersonation. It may involve identity evidence, a waiting period or temporary withdrawal limits. These measures can be inconvenient but make it harder for an attacker to take over an account through support.

Begin recovery through the official site or published support email. Ask what evidence is needed and how it will be protected. Do not send full documents to a social media account or to a caller who contacts you first.

API permissions

If you connect a third-party venue, limit a key to the permissions needed. Keep withdrawal permission disabled unless a documented feature specifically requires it and you understand the consequences.

Some venues split key permissions into reading balances, placing trades and transferring assets. A strategy that only analyses information should need read access, while a trading feature may need order permission. Withdrawal access is particularly sensitive because it can move assets away from the account.

Inspect permissions before and after connecting a tool. Use an IP restriction where supported and revoke a key when it is no longer needed. If a connection behaves unexpectedly, disable the key at the venue and investigate before creating another one.

Audit history

Check records of sign-ins, linked services and strategy changes. Save a copy of relevant timestamps when raising a support case so the team can trace the event.

A useful record includes sign-in times, linked devices, connection changes, strategy edits and payment requests. Those events help distinguish an authorised action from an account takeover or software issue. A visible timeline should be compared with confirmations from the relevant provider.

Record the time zone when reporting an event and keep screenshots of the affected page without exposing secret codes. If a record is missing or inconsistent, ask support for an investigation rather than guessing what happened from a balance alone.

Incident support

Email [email protected] with the time, device and activity you observed, without including passwords or full payment details. Ask for account access to be reviewed and for a case reference.

When reporting an incident, state what you observed, when it happened, the device involved and whether a payment or order may be affected. Support may need to restrict access while checking the records. You should receive a case reference and a clear explanation of any information required.

If a bank or third-party venue is involved, contact it directly through its official channel as well. Keep the communication in writing where possible. After resolution, change credentials, review connected services and check account statements for further unfamiliar activity.