TradeSentrix Trust Center
Transparency is part of the product. This page explains how published signal outcomes are measured, how simulations differ from real trading, what the current automation policy does, and which API-safety controls are enforced by the platform.
What “TP Before SL” means
The public headline rate uses the same production methodology as the existing results page: a tracked signal is counted as a TP outcome when it reaches at least one configured take-profit level. The denominator is TP outcomes plus signals stopped before any TP was reached.
A TP-then-SL record is not hidden. It remains visible as an SL event in the broader statistics while still belonging to the any-TP outcome group for the headline TP-before-SL metric because a configured target was reached first.
Signal lifecycle
Public signal performance can continue recording TP3 and TP4 after TP2. The current live Elite auto-trading execution policy closes the automated position at TP2.
Paper Trading methodology
The current simulator starts each normal paper account with $10,000 of virtual capital and uses a 1% virtual risk model per trade, with simulated leverage capped at up to 20×.
No real order is sent to Binance. Paper Trading results are simulated outcomes and are not real Binance account returns.
Backtest methodology
Backtest Lab is a historical TradeSentrix signal simulation. It helps eligible users evaluate how recorded TradeSentrix signals would have behaved under selected capital, leverage and TP-exit assumptions.
The current backtest does not model exchange fees, funding, slippage, liquidation, execution latency, or portfolio margin contention. It is not a TradingView Pine Strategy Tester replacement and does not guarantee future results.
Auto-Trading execution policy
At a high level, eligible automation follows this flow:
The current live auto-bot exit policy is TP2. This Trust Center describes the policy at a high level and does not expose private execution endpoints, server details, credentials or other security-sensitive implementation information.
API & Security
Submitted Binance API credentials are encrypted by the Laravel application before database storage. Binance API validation rejects configurations where withdrawal permission is enabled.
Users are instructed to enable only the Futures trading permission required by the platform and to apply the approved IP-restriction configuration.
Security & API SafetyRisk disclosure
Leveraged futures trading can produce substantial losses. Past published-signal outcomes, Paper Trading, competition rankings and backtest simulations do not guarantee future performance or real-account profitability. TradeSentrix does not provide personalized financial advice.