security
Local-first security, stated precisely
AutoSignalCopier runs the trade path — sessions, parsing, routing, delivery — on your own Windows PC. Message content never leaves it; the cloud handles licensing and the dashboard mirror. This page states each protection, and each limit, exactly.
Free 7-day trial · Windows 10/11, no payment method
The line at your PC
The agent, your terminals, the cloud, and your browser connect through three independent connections with separate identities — and they are deliberately not chained. Your terminal talks to the desktop agent over loopback; the agent talks to the cloud over device-signed HTTPS for pairing, licensing, and dashboard sync; your browser talks to the cloud for the dashboard. The cloud is never in the trade-execution path.
That split is the whole model. Everything that decides or moves an order lives left of the line, on your machine. Everything right of it is licensing and review.
What stays on your device
Your Telegram and Discord sessions live on the PC running the app — sign-in secrets, session files, and chat data stay behind the application's internal boundary, and logs redact them rather than recording them.
Message text from your selected chats is stored only in the local database, capped at 8 KiB per message and purged after seven days. The desktop creates its own device identity on first start and binds the private key to your Windows user through OS-level encryption; the key is never written to the database, never shown to the interface, and no cloud credential is stored alongside it.
- Source sessions and message text: this PC only, never uploaded
- Device private key: bound to your Windows user, never stored as plain text
- Short-lived cloud tokens: never stored, never logged, never shown
The loopback bridge, honestly
Orders reach MetaTrader through a bridge that binds explicitly to the loopback address, so it answers only programs on your own machine. The packaged EA authenticates with random 256-bit session tokens of which only hashes are stored, compared in constant time, expiring after 15 minutes and bound to the registered terminal, account, and broker.
First contact uses a one-time credential written into that terminal's own data folder with access limited to your Windows user: it expires after ten minutes, is consumed once, and is deleted after registration. Bodies are capped at 16 KiB, and the packaged EA binary is pinned by SHA-256 and verified before install.
shipped, not promised
What the current build does today
Every item below exists in the desktop app now. Roadmap items are not marketed here.
Local source sessions
behind the app boundary · redacted logs
Message text local-only
local database · 8 KiB · 7 days
Loopback-only order path
127.0.0.1 · short-lived sessions
Pinned packaged EAs
SHA-256 verified install
Signed licensing, fail-closed
verified policy · 60-min cache
Dashboard mirror, metadata only
message content never uploaded
Licensing and pairing without trusting the network
Pairing starts with a one-time token from your dashboard, valid ten minutes and single use. The desktop signs the pairing request with its device key, and the licence policy that comes back is verified byte-for-byte against a built-in public key before anything is stored. A policy that fails either check is discarded and the device stays unpaired.
Cloud connections use TLS with public Web PKI roots, and non-TLS endpoints are refused. The licence is then re-issued about every 15 minutes over a signed heartbeat and stays valid for up to 60 — so a cloud outage does not stop routing, which continues on the last verified policy. Once it expires, new entries stop while risk-reducing actions and dashboard visibility keep their last signed values, and anything invalid fails closed.
Unpairing clears the cached policy but keeps the device identity. Revoking a device from the dashboard rejects its next heartbeat and fails it closed — but revocation is not instantaneous, so a running device can keep trading until its cached policy expires.
What the cloud sees — and what it never does
The cloud receives the dashboard mirror, drained in batches of 50: trade results, position events, account snapshots, journal notes, and symbol mappings. Symbol-mapping updates arrive signed and are verified before they apply — and only to future signals, never to commands already admitted. Sync runs one way, desktop to cloud.
What it never receives: message content, source sessions and API secrets, your broker password (never read at all), the device private key — and trade commands themselves, which never travel to the cloud. Trade commands are authenticated by the short-lived loopback session; they are not individually signed. The installer is unsigned, so Windows SmartScreen warns once on first run; build hashes are published next to each installer so you can verify what you ran.
faq
Questions worth asking
Does my Telegram or Discord data go to your servers?
Your source sessions live on your Windows machine. Signal messages (Telegram chats, Discord channels) are read locally, and the trade path goes to MetaTrader over a loopback connection on that same machine. No one else's server is on the execution path, and source message bodies are never uploaded. Your account dashboard does mirror structured data from the agent: signals, trades, account snapshots, journal notes, and symbol mappings, so you can review them in the browser. It holds metadata, never message text.
Will it place trades without my permission?
No. Routing is disabled by default, requires an active pairing and an explicit typed confirmation to enable, and only sends orders for signals that arrive after the gate is on. Anything received earlier stays review-only and is never executed retroactively.
Does my PC need to stay on? Can I run it on a Windows VPS?
Yes, the machine running the app needs to stay on: reading, parsing, and routing all happen locally on that PC, so there is nothing in the cloud to carry on without it. A Windows VPS works fine for this. Every plan includes 3 paired Windows devices, and a desktop, a laptop, and a VPS together count as three devices at no extra cost.
I lost my password. How do I reset it?
Password resets are support-assisted for now. There is no self-service reset link on the login screen. Email us from the address on your account and we will reset it for you. The same goes for cancelling a plan or deleting an account: contact support and we will handle it.
Features and safety model
the safety checks
How it works
the pipeline these protections cover
FAQ: honest answers
what is not available yet
Try it on your own machine
Free 7-day trial, no payment method, full local signal pipeline on your own machine.