Security & Trust

Your funds stay yours.

Vordant is a trading control plane — it routes your strategy signals and manages execution according to your configured rules, but never touches your funds. We protect your credentials, validate permissions, secure webhooks, and require readiness checks before live trading.

Your Funds Stay on Your Exchange

Vordant does not provide custody, hold, or move your funds under any circumstances.
All trading activity occurs directly on your exchange account via its official API.
Vordant has no access to withdraw or transfer your assets — and keys with those permissions are rejected at connection time.
If Vordant is unavailable, your funds remain on your exchange unaffected.

Exchange API Key Security

When you submit an API key, it is encrypted with AES-256-GCM before being stored.
The full key and secret are never stored in plain text, never logged, and never returned to the frontend after submission.
Only the last 4 characters of your key are retained as a display reference so you can identify which key is connected.
Decryption happens server-side, in-memory, only at the moment an order is placed — and the decrypted value is cleared immediately after use.

For Binance and Bybit, Vordant validates your key's permissions at connection time and rejects keys with Withdrawal or Transfer permissions enabled. This validation is not yet fully implemented for OKX and Coinbase — those exchanges are supported for paper trading and connection, but live execution is not yet wired.

Permission Enforcement

Vordant requires Read and Spot Trading permissions — the minimum needed to check account state and execute strategy signals.
Keys with Withdraw, Transfer, Sub-account, or Futures Management permissions are detected and rejected.
A rejected key is flagged in your exchange connection list and cannot be used for trading until replaced.
OKX and Coinbase permission validation is in progress. Until fully supported, those keys are accepted but flagged for review, and live execution is not enabled.

TradingView Webhook Security

Each bot receives a unique, cryptographically random webhook token.
Only a SHA-256 hash of the token is stored — the raw token is shown once at generation time and never again.
Invalid token requests are rejected immediately.
Duplicate alerts (same alert ID) are blocked within a deduplication window.
Stale alerts — those received significantly after their timestamp — are rejected to help prevent replayed signals.
Tokens can be rotated at any time from your Webhook settings. Rotating a token immediately invalidates the previous one.

Live Trading Gates

Paper trading is the default mode for all new bots. No real orders are placed in paper mode.
Live trading requires an explicitly verified exchange connection, a risk manager with live trading enabled, and explicit confirmation.
Live trading gates are enforced server-side — they cannot be bypassed via the frontend.
Accounts that are suspended cannot place orders in any mode.

Binance is currently the primary supported exchange for live order execution. Bybit, OKX, and Coinbase connectivity is available, but live order routing for those exchanges is not yet fully wired. Orders on unsupported live paths fail closed — no order is submitted, and a failure record is logged.

Audit Logging

Sensitive actions are recorded in an audit log where applicable, including: exchange key connections and removals, bot status changes, live trading enablement, webhook token generation, order submissions, blocked orders, and admin actions.
Audit records include a correlation ID, timestamp, actor identity, resource type, and outcome.
Admin actions on user accounts (suspensions, plan changes, role changes) are separately logged in an admin audit trail.
Audit logs are not editable by regular users.

Current Limitations

• Live order execution is supported for Binance only. Other exchanges fail closed.

• Permission validation for OKX and Coinbase is not fully implemented. Keys are accepted but treated as unverified.

• Webhook token rotation policies (automatic expiry) are not yet enforced.

• Fill confirmation polling for Binance live orders is not yet implemented — orders are logged as live_submitted until manual review.

Questions about security or data handling? Contact us through your account settings. This page is updated as new security controls are implemented.

Ready to automate with confidence.

Connect your exchange, configure your signal source — TradingView webhook or Vordant-native strategy rules — test in paper mode, and go live only when readiness checks pass.

Start with paper trading How it works