FAQ
Everything people ask before putting their accounts under watch — including the ones we answer with a plain “no”.
Chartping is a read-only monitoring and alerting tool for trading accounts — MetaTrader 4/5 terminals and major exchange or broker accounts — that warns you before you cross the loss limits you set. It never places, modifies or closes a trade, never has withdrawal access, and never gives advice.
No. It is entirely read-only — it never sends any order. It only reads your account state and alerts you.
Never. Chartping exposes no withdrawal path and never calls a withdrawal endpoint. On exchanges where we can verify key scope (Binance, Bybit, Deribit), a withdrawal-capable key is rejected at connect; where scope can't be proven (OKX, Kraken and the other exchanges), the key is accepted but hard-flagged; broker tokens (OANDA, Alpaca, Tradier) are used strictly read-only, and Hyperliquid is watched from a public wallet address with no key. Either way it can't move your funds through us. MetaTrader monitoring uses no API key or password at all.
No. For MetaTrader, the agent reads your terminal locally on your own machine — no password ever leaves it. For exchanges, you paste a read-only API key: where the exchange lets us check scope we reject a trade- or withdrawal-capable key, and in every case Chartping only ever reads — stored encrypted (AES-GCM).
Yes. The Free plan is $0 forever: two machines, one exchange or broker connection, the daily-loss rule with early warning, and push, desktop and in-app alerts. No card to start — upgrade only if you need the full rule engine, more connections, or SMS and voice alerts.
No. Chartping only watches the rules you define and notifies you. It does not suggest strategies, values or trades.
MetaTrader 4 and 5 accounts via the Windows agent — a prop-firm challenge, a funded account or your own retail account (it works with accounts at firms like FTMO, FundedNext, The5ers and others). Thirteen exchanges and brokers connect with a read-only API key: Binance, Bybit, OKX, Kraken, KuCoin, Bitget, Deribit, Coinbase International, Gate.io, Hyperliquid, OANDA, Alpaca and Tradier; cTrader support is coming soon.
Mobile push (iOS & Android), desktop notifications (tray, toast, sound), SMS, a voice call for critical breaches, signed webhooks (Discord, Telegram, Slack or any URL) and a live in-app feed. You route severities per channel, and critical alerts are never suppressed by quiet hours.
Yes. The agent runs on any Windows machine, including a VPS — a common setup for MetaTrader. Your phone still gets the alerts wherever you are.
You get a “monitoring stopped” alert — silence is never mistaken for “all clear”. When the connection comes back, a “monitoring resumed” notice confirms you're covered again.
MetaTrader alerts fire inside the terminal, on price levels, only while that terminal is open on that machine. Chartping watches account risk — daily loss, drawdown-from-peak, margin level — across every account, keeps watching from the cloud, reaches your phone by push, SMS or voice call, and tells you if monitoring itself ever stops.
Yes. A read-only SDK lets any MQL EA or indicator emit a log or alarm in one line, and any alarm can POST to a webhook URL you control, signed with HMAC-SHA256. EA vendors can also license their products through Chartping — issue, meter and revoke licenses with an API. It never trades.
Alerts trigger as you approach a threshold, and we send a “monitoring stopped” alert if the connection drops. We don't guarantee any outcome — this is a monitoring and alerting tool, and alerts are best-effort.
Traffic is encrypted with TLS 1.3 and the agent link is device-bound (Ed25519 proof-of-possession), so an intercepted token can't be replayed elsewhere. Exchange keys are stored encrypted (AES-GCM), monitoring is read-only, and there is no withdrawal access. You can export or erase your data at any time.
Join the waitlist — be among the first to know what's happening across every account you trade.