Last updated: October 2026
1. Signing in
Your password is never stored. Ezymex keeps only an argon2id hash of it, a form designed to be slow and expensive to attack, so a stolen database does not hand anyone your password. Signing in also takes a one-time code sent to your e-mail, which means a password on its own is not enough to reach your account.
- Passwords stored as argon2id hashes, never as text
- A one-time code on sign-in, in addition to your password
- Repeated code requests are rate-limited, by account and by network address
- You can see your active sessions and end any of them
2. Letting someone look without letting them act
You can grant read-only access to your account - to a mentor, an accountant, or anyone you choose - and withdraw it whenever you like. A read-only visitor sees what you allow and can do nothing else: no trading, no transfers, no withdrawals, no changes to your details.
3. When our staff open your account
Support sometimes needs to see your account to answer you. When that happens you are told while it is happening: a banner across the Client Area names the member of staff who opened the session and counts down the time left on it, and the session expires on its own. Every such session is recorded.
4. Two people, not one, for money that moves by hand
Balance adjustments made by staff are capped by a threshold the broker sets. Above it, an adjustment does nothing until a second member of staff with a separate permission approves it. The same rule governs Ezymex SIP: a month's returns are settled once, and a settlement has to be approved by someone other than the person who prepared it before a single payout leaves.
5. Books that check themselves
The trading engine is event-sourced. Every fill, every balance change and every ledger entry is written as one event inside one database transaction, so a half-finished operation cannot exist. On every restart the engine replays all of those events, rebuilds the balances from them, and checks that the ledger balances - and refuses to start if it does not. Your balance is a consequence of recorded events, not a number anyone types in.
6. A record of what happened
Account changes, staff actions, approvals and sign-ins are written to an audit record with who did what and when. Operations that move money carry an idempotency key, so a double-click, a retried request or a flaky connection books the movement once rather than twice.
7. How the platform is exposed
The services behind Ezymex do not face the internet. They listen only on the machine they run on, and public traffic reaches them through a reverse proxy behind Cloudflare, over HTTPS. Database credentials and payment keys live in server-side configuration and are never sent to a browser or an app.
8. What we do not claim
Ezymex has not been through an external security audit or certification, and this page does not pretend otherwise. Trading involves risk to your capital regardless of how well an account is protected, and security measures do not reduce market risk. If you believe you have found a vulnerability, write to us and we will reply.
Report anything you find to [email protected].
Read this alongside our Deposit & Withdrawal Policy and Risk Warning.