Transparency & Methodology

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.

View Complete Signal History Open Performance Analytics

Customer verification checklist

Five checks to make before purchasing signals

1. Inspect the full results

Look beyond a headline TP rate: inspect stop-loss outcomes, TP-then-SL events and the methodology used for the denominator.

View published signals

2. Understand what is not independently verified

Public results are generated from TradeSentrix's own signal tracking. Do not treat them as an independent audit, a brokerage statement or a net account-profit calculation after fees and slippage.

Review outcome methodology

3. Check packages and billing terms

Confirm current signal quota, feature eligibility, pricing and checkout terms. Ask support to clarify refund eligibility before purchase if needed.

Compare packages · Terms

4. Review account and API risks

For optional Binance Futures automation, review permissions and withdrawal restrictions. Software safeguards cannot remove trading or exchange risk.

Security details

5. Ask for business and support verification

Before paying, request available operator details, billing documentation and support clarification if these matter to your decision. No independent trading-performance audit or specific regulatory licensing is asserted by this checklist.

About TradeSentrix · Contact support

Published Signals

3,208

Resolved for Rate

3,179

TP Before SL

98.5%

All SL Events

161

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.

Complete Results Detailed Transparency

Signal lifecycle

Published signal tracking follows the configured progression:

Entry→ TP1→ TP2→ TP3→ TP4 / SL

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.

Simulation

Paper Trading methodology

The current personal simulator starts each normal paper account with $10,000 of virtual capital. Each new paper trade commits 1% virtual margin at a fixed 20× leverage, creating modeled notional exposure equal to 20% of the current virtual balance. Negative terminal P&L is capped at the committed 1% virtual margin.

No real order is sent to Binance. The personal Paper Trading model is a simplified simulation rather than an exchange-exact maintenance-margin or liquidation engine. Paper Trading results are simulated outcomes and are not real Binance account returns. The separate Elite monthly competition keeps its own standardized methodology.

Paper Trading Guide Paper Competition

Historical Simulation

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.

Automation

Auto-Trading execution policy

At a high level, eligible automation follows this flow:

Signal → validation & safeguards → eligible user automation → Binance Futures → monitoring → reconciliation

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 Safety

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 Safety

Risk 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.