Fund Security

1.1 All cash balances and unrealised positions held in your Account are denominated in United States dollars and recorded on the Company's books as a liability owed to you, irrespective of the rail by which you funded the Account.

1.2 A statement of your position — cash, open trades, and historical activity — is available at any time from the dashboard and can be exported as a CSV or PDF. Every deposit, trade, swap, transfer, and withdrawal is recorded as a ledger entry that you can audit line by line.

1.3 We do not net your balance against the balance of any other client, and we do not lend your balance to any other client.

2.1 Bullion FX accepts on-chain deposits in USDT on the Tron, Ethereum, and BNB Smart Chain networks, and in BTC on the Bitcoin network. We do not operate a proprietary stablecoin and we do not issue any internal IOU; deposits arrive on chain and withdrawals leave on chain.

2.2 Incoming deposits are credited to your Account after a number of network confirmations appropriate to the network in question. The number of confirmations and the per-network minimum deposit are published on the deposit page in the dashboard.

2.3 Client crypto-asset balances are held in operational hot wallets controlled by the Company. The keys to these wallets are managed by the Company. Wallet activity is reconciled continuously against the Company's internal ledger; any divergence between on-chain state and the internal ledger triggers an operational alert.

2.4 The Company does not currently advertise a cold-storage policy, third-party qualified custodian, or insurance over hot-wallet balances. We rely on operational controls and rapid withdrawal processing rather than custody outsourcing. Section 5 of this page describes the residual risks of this arrangement.

3.1 Where fiat funding is available in your jurisdiction it is provided through licensed payment-service partners introduced by the Company. We do not directly hold a banking licence, and fiat funds are not held in a bank account in the Company's name.

3.2 Fiat funds received through these rails are held in segregated banking arrangements maintained by the payment partner, designated for client funds and kept separate from the partner's own operating accounts. Your interest in such pools is recorded on the Company's books as a pro-rata claim, denominated in United States dollars, against the pool.

3.3 The Company performs onboarding due diligence on each fiat rail partner before introducing it to clients and reviews each partner periodically thereafter. Where a partner fails its review, the Company will stop routing new traffic to that partner and will work with the partner to release any balances back to clients.

4.1 Approved withdrawals are processed on the same business day they are approved, on the same rail you funded with. We do not require you to wait days or weeks for a withdrawal review unless a specific compliance reason applies.

4.2 Withdrawal caps are tier-based and are described in full in Section 4 of the Terms of Service. The Tier 0 ("T0") default cap is a lifetime cumulative withdrawal of USD 2,500 across all rails. Higher tiers are unlocked by completing the corresponding level of KYC; the Tier 3 ("T3") tier may require enhanced due diligence including source-of-funds documentation.

4.3 Where a withdrawal must be paused for a compliance reason — for example, suspected fraud, a sanctions check, or a positive AML hit — the Company will notify you of the pause and the next steps in writing.

4.4 We do not impose a withdrawal fee on top of any unavoidable network fee for an on-chain rail. The network fee, where it applies, is disclosed before you confirm the withdrawal.

Segregation of client funds reduces the risk that client money is used for the Company's own operating purposes. It does not eliminate the following risks, which remain with you to the extent the Company cannot make you whole from its own resources.

• Operational compromise of a hot wallet. Although we monitor and reconcile hot-wallet activity, a successful attack on the operational keys could result in loss of crypto-asset balances. The Company does not maintain a private insurance policy against such loss.
• Default of a fiat payment partner. Where fiat funds are held in segregated accounts at a third-party payment partner, the partner's own insolvency could delay or impair the return of funds to clients. Our review process reduces, but does not eliminate, this risk.
• Network-level events on a deposit chain. A material reorganisation, fork, or congestion event on a deposit chain may delay confirmation, raise network fees, or in extreme cases affect the credit-to-account treatment of a transaction.
• Force majeure on a banking rail. A central-bank action, sanctions designation, or country-level capital control could prevent the Company or its partner from transmitting funds in a given direction or currency.
• Operational outages of the Company's own infrastructure. Despite redundancy and monitoring, the platform may, on rare occasions, be unavailable. We are not liable for losses arising from temporary unavailability, as set out in Section 2 of the Risk Disclosure.

We list these residual risks so that you can size and structure your account accordingly. The single most effective customer-side control is to keep no more on the platform than what you actively need to trade, and to withdraw promptly when funds are not in use.

6.1 Your dashboard publishes a complete activity log for the Account. Every deposit links to a network transaction hash. Every trade links to an MT5 execution record. Every withdrawal links to a network transaction hash for crypto rails or a settlement reference for fiat rails.

6.2 You may export your activity at any time, in CSV form for analysis or in signed-PDF form for a third party. You may also write to support and request a written explanation of any specific ledger entry; the Company will respond within five (5) business days.

6.3 If our explanation does not match your own records and the matter cannot be resolved through ordinary support correspondence, you may invoke the complaints procedure described in Section 29 of the Terms of Service and on the Regulation page.