Security at Gainforthic

Your account sits behind several layers of protection, and most of them are under your control. This page explains each safeguard plainly: what it does, whether you have to use it, and what to do if something goes wrong. Security works best when it is understood, so we have written this for readers who have never worked in IT.

Account protectionnine safeguards explained Incident helppriority support channel

Two-factor login

An extra code on your phone keeps passwords alone out of your account.

Encrypted data

Both the connection to us and the stored records are protected.

Login alerts

Every new device triggers a notification you can act on.

1. Two-factor and multi-factor authentication

Two-factor authentication (2FA) is available on every account and can be enabled in the security settings of your dashboard. Once enabled, signing in from a new device asks not only for your password but also for a single-use code generated by an authenticator app on your phone, such as the ones most UK banks already encourage their customers to use. Multi-factor checks also apply automatically in sensitive situations, for example after a password reset or a login attempt from an unfamiliar country.

Using 2FA is optional but strongly recommended, and recovery is deliberately careful: if you lose your phone, you verify your identity with the support team through document checks and a short security conversation. Recovery is never granted on the strength of an email alone, because a stolen inbox should never be enough to reach a trading account.

2. Encryption of data at rest and in transit

All traffic between your browser and the platform travels over TLS encryption, and the certificate covering gainforthic-ai.org is checked by your browser on every connection. Records that hold personal details, identity documents and account activity are encrypted at rest in the systems that store them, with access limited to the specific services that need each record.

Encryption is applied across the responsible systems rather than one database: the identity-verification store, the account database and the activity logs each protect their contents independently. The practical effect is that a single compromised component never exposes the full picture of any client.

3. Anti-fraud and phishing protection

We communicate only from our official domain and from a short, published list of sender addresses, with [email protected] as the single contact for account matters. Messages that matter, such as withdrawal confirmations or security alerts, always reference the last four digits of your account rather than full details, and we never ask you to send passwords, one-time codes or document copies by email.

If a message claims to be from Gainforthic but asks for credentials, treats urgency as a reason to skip verification, or points to a look-alike domain, treat it as fraudulent. Our Fraud warning page explains the patterns we see most often, including clone firms misusing our name. When in doubt, type the address into your browser yourself or contact support before acting.

4. Login notifications

Every sign-in from a device your account has not used before triggers an email alert, sent immediately, describing the device type and the country of the connection. Unusual activity, such as several failed password attempts or a password change you did not make, raises an alert in the same way.

These notifications exist so that you know about events before they become problems. If an alert describes something you did not do, follow the link in the email to lock the account or contact support at once; a temporary freeze while we verify you costs minutes, whereas an unnoticed intruder can cost far more.

5. Device and session management

The security settings page lists every active session on your account, with the device type, the browser and the time of the last activity. You can end any session instantly, which signs that device out everywhere, or sign out all devices at once when, for example, a phone is lost or a shared computer was used by mistake.

Sessions expire automatically after a period of inactivity, and idle sessions on public connections end sooner than on your trusted home devices. The combination means an abandoned login is worth very little to anyone who finds it.

6. Account recovery

Recovering access always starts with proving who you are, not what you know: the support team checks your identity document, compares it with the details verified at onboarding, and asks security questions set during registration. Only after those checks pass is a new password issued or a new 2FA device paired.

Recovery has deliberate limits. It cannot be completed in a single anonymous email, it cannot be used to bypass an ongoing security review, and repeated recovery attempts on the same account attract manual scrutiny rather than automation. Slow but certain is the correct trade-off for a door this important.

7. API-key permissions

Where the platform connects to exchanges on your behalf, it does so through API keys whose permissions are as narrow as the task requires. Keys are issued for reading market data, for trading, and for withdrawal as three separate scopes, and a key granted one scope never silently gains another.

Withdrawal rights in particular are held apart from trading rights and are reviewed whenever your payout settings change. Keys can be revoked from the settings page at any time, and revocation takes effect immediately, cutting the connection without waiting for a trading cycle to finish.

8. Audit history

Your account keeps a timestamped record of the events that matter: logins and their origins, connections and disconnections, changes to strategies, and updates to settings such as risk limits or notification preferences. The history is presented in the dashboard as a readable list rather than a technical dump.

Two things follow from this record. You can check, at any moment, that nothing changed without your knowledge; and if you ever raise a dispute, both you and our compliance team are working from the same factual sequence rather than recollections. Audit records are retained in line with our Privacy Policy.

9. Support during incidents

Security concerns reach the support team through a priority route: write to [email protected] with the word "security" in the subject and the message is queued ahead of general queries. The first reply sets out what we have done immediately, beginning with freezing the affected account if you request it or if our checks support it.

From there an incident follows a fixed sequence: containment, verification of the affected client, investigation using the audit trail, and a written summary of what happened and what changed as a result. We aim to acknowledge security reports within one working hour during support hours and to keep you informed at each stage rather than going quiet while work continues.

Security reduces risk; it does not remove it, and no platform, including ours, can guarantee that trading losses will not occur. Safeguards described here protect your account and data, not the value of your investments.