Nine layers between your account and everyone else
Security at Southern Ledger works like a good ledger: every entry controlled, every change recorded, every exception reviewed. This page explains each layer in plain terms — what is switched on by default, what you should switch on yourself, and what to do if something looks wrong.
2FA / MFA
Multi-factor authentication on sign-in and every sensitive action.
Encryption
Data protected in transit and at rest across all systems.
Audit history
A tamper-evident log of every login, change and withdrawal.
1. Two-factor and multi-factor authentication
Two-factor authentication (2FA) is available on every account and we strongly recommend enabling it the day you join. With 2FA active, your password alone is not enough to sign in: a second factor generated by an authenticator app on your phone must be entered as well, with time-based one-time passwords (TOTP) as the default method because they work offline on any device.
Some actions always require the second factor, whether or not you have made 2FA mandatory for ordinary logins: creating or rotating API keys, changing your password or registered email, and initiating withdrawals to a destination you have not used before. This is deliberate friction — a few extra seconds at the moment money moves is the cheapest protection there is.
If you lose access to your second factor, recovery is a verified process rather than a reset link, described in section 6.
2. Encryption
All traffic between your browser and the platform is encrypted with TLS; connections that try to arrive over an insecure channel are redirected to the secure one. Inside the perimeter, personal data and identity documents are encrypted at rest, which means that a hypothetical copy of a storage volume is not readable without the key management layer in front of it. The same standards apply to session tokens, the audit history described in section 8, and backups, with keys managed separately from the data they protect.
Encryption does not protect a password typed into a compromised laptop, which is why the anti-fraud guidance in section 3 matters just as much as anything we do server-side.
3. Fraud and phishing protection
Phishing — fake websites and messages imitating a real company — remains the most common way trading accounts are compromised, and it targets you rather than our servers. Our countermeasure starts with domains: the platform is served from southern-ledger.com, and any address that differs, however slightly, is not us. Bookmark the real sign-in page and use the bookmark rather than following links in emails.
Official messages from Southern Ledger never ask for your password, your 2FA codes, or remote access to your device. A genuine support officer will never rush you, and never suggest moving funds to a "safe account" — that phrase is a fraud script, not a procedure. If you suspect a message or site is impersonating us, forward it to [email protected] and stop interacting with it.
4. Login notifications
Every sign-in from a device your account has not used before generates an email notification with the time, approximate location derived from the network, and the device type. You do not need to configure anything for this to work; it is on by default because an alert you never set up is the one you are most likely to read.
The same monitoring watches for suspicious patterns: a sign-in attempt from a new country shortly after one from your usual location, repeated failed password entries, or a withdrawal request that arrives minutes after an unusual login. Suspicious activity freezes withdrawal processing until you confirm through your registered contact channel that the activity was yours.
If a notification tells you about a login you do not recognise, act immediately: change your password, review active sessions in section 5, and contact support. Fast reporting is the difference between an incident and an anecdote.
5. Device and session management
The account dashboard lists every active session: browser sessions on desktop and mobile, and any application sessions created through API keys. Each entry shows when it started and when it was last used, and each can be revoked instantly. Revoking a session ends it at once — the device must sign in again with full credentials.
Sessions expire automatically after a period of inactivity, and the withdrawal flow asks you to re-authenticate if it has been open untouched for a while, so an unlocked laptop in a café is not a standing invitation.
Make a habit of reviewing the session list whenever you sign in from somewhere new, and revoke anything you cannot account for.
6. Account recovery
Recovering access to a locked account is a verification process, not a form. You will be asked to confirm details from your identity documents and your recent account activity — information an attacker cannot copy from a leaked database because it includes facts only the account holder and our records share. Recovery from a new device additionally requires confirmation through your registered email before any change takes effect.
If your 2FA device was lost or replaced, the same procedure rotates your second-factor enrolment: the old authenticator binding is revoked, a new one is created, and the change is recorded in the audit history with your confirmation. At no point does support ask you to read out a one-time code or grant remote screen access; those requests are fraud, and section 3 applies to them fully.
Recovery requests are handled by the security channel during business hours and are prioritised above ordinary tickets. If you are locked out because of a suspected compromise rather than a lost device, say so in the subject line — the process then starts with a protective freeze rather than a restore.
7. API key permissions
If you connect automated tools to your account, API keys carry explicit scopes: read-only, trading, and withdrawal. A read-only key can pull account statements and reports but cannot place, modify or cancel anything. A trading key can manage positions within your strategy limits but cannot move funds out. The withdrawal scope exists, is issued only on explicit request, and is subject to the same second-factor confirmation as a withdrawal entered by hand.
Keys are created with an expiry date you choose and can be rotated or revoked at any moment from the same dashboard panel as sessions. Rotation replaces the secret immediately; the old key stops working from the second the new one is active. Every create, use-band change, and revoke lands in the audit history described next.
Our guidance is simple: start read-only, grant trading only when a tool genuinely needs it, and never grant withdrawal scope to a third-party service. If a tool's documentation asks for more permission than its function requires, that is a reason to question the tool, not to widen the key.
8. Audit history
Every security-relevant event on your account is written to an append-only audit log: logins and failed login attempts, password and 2FA changes, session and API key management, strategy and setting changes, and the full life cycle of each withdrawal request. Entries cannot be edited or deleted — including by our staff — which is what makes the log evidence rather than anecdote. The history is visible to you in the dashboard, filterable by event type and date, and exportable for tax or record-keeping.
Beyond your own account, the same principle governs internal access: support officers act through scoped tools that log every lookup of client data, and those internal logs are reviewed. A record you can inspect and a record we cannot quietly rewrite is the standard we hold both sides of the platform to.
9. Incident support
If something goes wrong — a login you did not make, a message you suspect is fake, a withdrawal you cannot account for — contact the security channel at [email protected]. Mark the message urgent in the subject line. The first response acknowledges receipt and confirms what has already been done; in most cases the protective steps, such as freezing withdrawals and revoking sessions, are taken before the reply is written.
The escalation path is defined in advance: first responder, security lead, and — where client funds or regulatory obligations are involved — the compliance officer. You will be told who owns your case and updated at each stage, in writing, so the incident itself generates the kind of record this page promises.
After an incident closes, the review answers two questions: how the unauthorised access happened, and what makes it harder next time. Where the fix is on our side, it ships and is documented; where the lesson is user-side (a reused password, an over-broad API key), your manager will walk through it with you rather than leaving you to decode a security article.
One honest limit: no security architecture makes trading risk-free, and none makes you rich by design. These layers protect your account; the Risk Disclosure explains what markets can still do to your balance.