Keep access deliberate and account identity explicit.

The documented administration model restricts control to the configured owner and uses confirmation for supported changes. Keeping the owner's Telegram and operating-system accounts secure remains essential.

• Verify the intended owner during setup.
• Use only the official private setup process supplied for your deployment.
• Treat possession of a credential as sensitive access, even when a screen masks it.

The source account used for AccountCopy is observed separately from the destination. Account changes require checks of ownership and current exposure. A missing or stale status should prompt verification rather than an assumption of readiness.

• Review the selected broker account before enabling a source.
• Do not run competing copiers against the same account and state.
• Check actual broker positions when a saved observation may be out of date.

Passwords, source access keys, Telegram sessions and private alert links can grant access to your accounts or workflow. This website has no credential form, and ordinary troubleshooting should begin with a sanitized description.

• Remove secrets, personal account details and private links from screenshots.
• Describe the source type, time of the issue and visible error without sharing credentials.
• If a secret is exposed, use the relevant provider's process to revoke or replace it.

A network failure can hide the result of a trading operation. Atlas preserves records and does not treat an unknown outcome as permission to repeat an order. These controls reduce particular failure risks; they are not a security certification or a guarantee against loss.

• Confirm the broker result independently of notification delivery.
• Keep operating-system and platform access under your control.
• Review recovery procedures for the specific deployment before relying on them.