Know where your credentials live.
YO4X’s local mode keeps the broker trading password in a Windows-protected vault on your PC. It is not sent to YO4X servers for local execution.
Your broker holds the account.
YO4X does not custody your trading funds. The desktop connects to a supported MT5 account you control. The current execution workflow is gated for demo accounts; live-money execution is not yet released.
Local credential storage does not make a computer immune to compromise. Keep your Windows account and device protected, and do not share passwords or recovery information through support messages.
Strategies operate within controls.
The product design places entitlement and risk checks before its broker gateway. Strategy logic does not connect directly to the broker. Checks are intended to block new exposure when quotes, permissions or account state cannot be trusted.
These controls do not guarantee a maximum trading loss or successful execution during every connection or broker problem. Review the account, instrument, inputs and order journal before and during a demo run.
Compatibility is limited deliberately.
YO4X does not run arbitrary EX5 files. MQ5 source compatibility analysis supports a restricted subset, and unsupported behaviour is reported. The included strategy workflow is separate from uploading or licensing an original third-party EA.
Read about strategy imports →Cloud mode has a different boundary.
Cloud execution is planned and is not available to purchase now. Its design requires a separate managed cloud vault rather than the local-only credential arrangement. Review the released terms and controls when that mode becomes available; local-mode statements should not be assumed to describe cloud storage.
Ask about your setup.
This page explains the supplied product design. It is not an independent security audit, certification or guarantee against loss. For an account-access concern, use YO4X support and include the issue and app version without sending your password.