Security

2026-09-21-draft · SHA-256: bf40a2036d3fd4edf70e52182a2f7dd38a8d17ef4aab2cb3cb61d2b2431b9085

TradingNext is designed so users’ trading funds remain with their own broker or exchange.

TradingNext does not custody trading funds or assets and does not support withdrawals from connected accounts.

Where API permissions are configurable, TradingNext should request only the minimum permissions required and may reject credentials that permit withdrawals.

Broker/exchange API secrets and OAuth tokens should be encrypted at rest, transmitted over encrypted connections, segregated where practical, least-privilege access-controlled, excluded from ordinary logs/support messages, and revoked/deleted when no longer required.

A bot must have an active user-authorised configuration before it can submit trading instructions. Material strategy/configuration changes should be versioned and auditable.

Where TradingNext cannot verify a required account, market, product, permission or strategy condition, preferred behaviour is fail closed: skip/reject rather than silently substitute an unauthorised alternative.

Automation should use idempotency and duplicate-protection mechanisms to prevent the same instruction being submitted twice because of retries, timeouts or restarts.

TradingNext maintains technical records designed to establish what the user authorised, which strategy/configuration was active, what instruction was derived, what was sent to the provider, what response was returned, and what result was later reported.

Security issues: security@tradingnext.net