6. Review, renew and recover
Preserve the account evidence and private state. A local dashboard, a subscription trial and a demo setup check are three different things.
Expiry, outages and uncertain outcomes
Monitor verified expiry and renew using an owner-issued code. The recorded authority cutoff governs permission; broker end-of-day treatment requires the owner’s explicit calendar procedure. Expiry does not imply pending-order cancellation or position closure.
Fresh online licensing checks are required for entries and protective modifications. An outage can block both; existing broker-side SL/TP remain but software management is not guaranteed. For Unknown results, disconnect or quarantine, inspect exposure and preserve journals, ledger and protection state. Use support-led reconciliation before resuming; do not delete state or resend a message to force a trade.
Backups and reporting
Disconnect before maintenance or backup and review open exposure. Restore to a new destination with supported tools. Telegram sessions and Windows-protected credentials may require supervised recovery or renewed sign-in. Restoring does not start trading.
Choose the reporting period before source analysis and XLSX export. Verify logo, account, username and license identity; use A4 Landscape with repeated headings and disclosure in print preview. Reconcile statistics with the broker statement.
Support and the first-use check
Use a category and a description of up to 200 characters. Review identity/license details before sending. Never share passwords, API Hash, tokens, recovery codes or session files. Recovery requires owner identity verification and the supported flow.
In the authorized demo setup, compare real broker tickets, leg counts, risk, SL/TP, replies, controls and restart records. A demo check is not trial-subscription activation. The default dashboard is local: a phone cannot reach this PC through its own 127.0.0.1. Remote HTTPS access and notifications need separate deployment; closed-browser alerts are not guaranteed.