Your account, protected on nine fronts

Security at AfriQuant AI is not a single feature; it is a set of layered protections that work together while you trade, and while you sleep. This page explains each layer in plain language: what it does, when it applies, and what you should do if something looks wrong.

If you ever suspect unauthorised access to your account, contact us immediately at [email protected] and we will secure the account with you on the call.

2FA / MFA

Two-factor authentication on every login, with a verified recovery path.

Encryption

Data protected in transit and in storage across all systems.

Login alerts

Notifications for new devices and suspicious activity.

1. Two-factor and multi-factor authentication

Two-factor authentication (2FA) adds a second proof of identity at login: something you know (your password) plus something you have (a one-time code). AfriQuant AI supports one-time codes delivered by authenticator app or SMS. We strongly recommend the authenticator app, because it does not depend on mobile network coverage and is far harder to intercept than SMS codes.

Enabling 2FA is optional at registration but becomes mandatory before your first withdrawal and before any change to your withdrawal details. That rule exists because those two actions are exactly what an attacker wants to perform on a stolen account.

If you lose your device, recovery is deliberate and human: you contact support from your registered email, verify your identity with the documents described on the AML / KYC page, and a specialist resets your 2FA after a mandatory waiting period. The waiting period exists so that an attacker cannot use recovery to lock you out of your own account.

2. Encryption of data in transit and at rest

All traffic between your browser and the platform travels over TLS, and we redirect every plain-HTTP request to HTTPS. Certificate transparency monitoring alerts us if a certificate for our domains is ever issued unexpectedly.

Data at rest, including identity documents and personal details, is encrypted at the storage layer of the systems that hold it, and decryption keys are managed separately from the data itself, with access limited to the specific services that need it. The same standards apply to backups, which are encrypted before they leave the primary environment. Encryption protects confidentiality; it is not a substitute for the access controls and audit logging described in sections 5 and 8.

3. Anti-fraud and phishing protection

Our official domain is afriquant-ai.co.za, and it is the only domain we ever use to contact you. We will never phone you asking for your password, your 2FA codes, or a payment "to release funds". Any message making such a request is fraudulent, whatever it looks like.

Messages from the platform are sent from verified addresses and always identify themselves in a consistent format. Where a message concerns withdrawals or personal data changes, we additionally ask you to complete the action inside the platform rather than by replying. If a website, call centre or WhatsApp group uses our name but a different domain, treat it as a clone: do not share any personal information, and report it to us so we can act. The Fraud warning page describes the tell-tale signs in more detail.

4. Login and activity notifications

You receive an email notification whenever a login happens from a device or browser not previously seen on your account, and a separate alert when we detect activity that matches known fraud patterns, such as a password change followed immediately by a withdrawal-details change from a new location.

Each notification tells you the country, the device type and the time, so you can judge in seconds whether it was you. If it was not you, the notification links directly to the session-management screen, where you can terminate the session and freeze withdrawals in one step, and to our support inbox. Read these notifications even when you are busy; they are short by design.

5. Device and session management

The security page of your account lists every active session: browser, approximate location, last activity and the date it was first authorised. You can end any session instantly, and "end all other sessions" signs out everything except the device you are using now.

Sessions expire automatically after a period of inactivity, and logging in on a new device requires the full authentication flow, including 2FA once it is enabled. Password changes invalidate all other sessions automatically, which is the single most effective step if you suspect someone has your credentials.

6. Account recovery

Account recovery verifies that the person requesting access is the account owner, not merely someone who knows the email address. Recovery therefore combines checks: confirmation from the registered email, verification of identity documents, and a review of recent account activity that only the true owner would recognise.

All recovery requests are handled by our support and compliance specialists, never by automated self-service reset of withdrawal details. A mandatory delay applies between a successful recovery and the first withdrawal from that account. These frictions are deliberate; they exist to make stolen accounts worthless to attackers while costing legitimate users one extra day at most.

7. API key permissions

Where the platform connects to exchanges on your behalf, the keys it uses are scoped to the minimum permissions needed. Trading keys can read balances and place or close orders but cannot withdraw to new destinations. Withdrawal permission, where a strategy genuinely requires it, is a separate key that you explicitly authorise, restricted to destinations already verified in your name, and visible in the same audit history as everything else.

You can review the exact permissions each connection holds at any time, and revoke any key instantly. Revocation takes effect immediately; there is no grace period during which orders can still be placed.

8. Audit history

Every security-relevant event on your account is recorded in an audit log you can read: logins (successful and failed), password and 2FA changes, new devices, API key creation and revocation, strategy starts and stops, and changes to personal or withdrawal details. Each entry shows what happened, from where and exactly when.

The log cannot be edited or deleted by anyone, including our support staff. If anything in it surprises you, quote the entry back to support and we will investigate it as a security incident rather than a routine query.

9. Incident support

If you suspect a security incident, the fastest channel is [email protected] with the words "security incident" in the subject. Such cases are triaged ahead of the general queue. The first step is protective: we can freeze withdrawals and terminate sessions on your account within minutes of confirming your identity, before any investigation begins.

You will then have one named point of contact for the incident, who will tell you what we found, what we did, and what steps we recommend you take on your side, such as changing a reused password. We aim to give you a first substantive response within one business hour during support hours. Security incidents are also reviewed by management and feed back into the protections described on this page.

No security system makes trading risk-free, and none of the above removes market risk. They exist so that the only thing that can move your money is a decision, human or algorithmic, that you authorised.