Guide for the forthcoming edition. The old version 3.14 PDFs are retained as an archive, not instructions for this edition. Replacement PDFs follow completed acceptance checks.
1. Create your local account and device request
Choose your own local username and a password of 8–128 characters. Keep it safely: central password recovery is unavailable in this edition. Read and accept the displayed terms yourself.
In License file, choose 1. Download device request. It contains the local customer identifier and device identifier, without your password or broker credentials. Share it with LSCT when arranging your paid license.
2. Pay the invoice, then import the signed file
Once release delivery is confirmed, review the invoice and agreed billing month. After payment, LSCT supplies a signed .lsct-license file. Choose it under 2. Import signed license, then check the displayed status and expiry. A payment receipt or screenshot alone is not a license.
The application checks the file against its trusted issuer key and your device and local customer identity. Paid verification is local; there is no activation code or paid activation-server login. Importing or renewing a file does not start trading or deliberately stop existing protection.
3. Calendar-month renewal in Dubai time
Each file names its billing month. It covers that calendar month and the whole first day of the following month in Asia/Dubai (UTC+4). The cutoff is the start of day 2, rather than an assumed broker closing time.
Example: the September 2026 entitlement ends at 00:00 on 2 October 2026 in Dubai, which is 2026-10-01 20:00 UTC. A file bought partway through September still has that billing-month cutoff; it is not a rolling 30-day subscription.
Obtain and import the next monthly file before the cutoff. A future renewal can wait without shortening the current period. An older file cannot overwrite a newer recorded renewal. If an import is interrupted, refresh the status before retrying.
4. Change settings while keeping the device license
During validity you can change the trading account, Telegram sources, symbols and operating settings without requesting a new license merely for those changes. The license stays with its device and local customer identity; copying it to another device does not authorize that device.
Switch accounts deliberately while new entries are paused. The runtime must verify the exact selected account, broker server and Demo/Live mode. Resolve and supervise existing exposure on the previous account; a settings change does not transfer ownership of positions or make protection follow an account that is no longer connected.
5. Seven days from the first device registration
When the trial service is available, review the device-registration notice and select Start seven-day trial. One initial HTTPS request registers the pseudonymous device identifier and returns a signed file valid for 7×24 hours. Paid license verification remains independent.
Re-downloading or repeating registration returns the same original expiry. When you re-download or open a fresh session after the trial expires, the application locks reading, management and execution and shows only the expiry warning and subscription page until a valid paid file is imported. Review any open positions directly in MT5. An already-running protection process retains its existing owned-position duties; this does not grant a new session or fresh trading access. Paid-license protection recovery follows its separate ownership checks. Public trial registration is not available yet.
Device identification is not hardware attestation. Reinstalling Windows, changing identifiers or privileged tampering cannot be prevented absolutely. Keep the original installation and data; do not reset them to try to recover an interrupted trial.
6. Paid expiry blocks new entries; protection has a separate duty
Paid-license expiry must not disable management of positions already owned by the program, including recovery after restart. There is no commercial 24-hour management cutoff in this revised design. Management still requires the running program, broker connection, matching account, valid ownership and protection plans.
Expiry does not close positions. A stopped computer or disconnected broker cannot provide software trailing. Check broker-held stops and targets independently, and resolve uncertain execution outcomes before resuming. This guide describes intended and locally tested behavior; controlled broker acceptance remains a release requirement.