Keep the limits in the picture.

Trading involves financial risk

Market outcomes can differ from expectations, and losses are possible. Historical statistics do not establish a reliable outcome for a future trade. Frequent activity, leverage, execution conditions, and costs can change the amount and nature of risk.

The site does not assess your finances, objectives, experience, or ability to withstand losses. Its material should not be treated as a personalized recommendation.

Simulations are conditional

A backtest depends on the selected data, information timeline, rules, execution model, costs, and evaluation procedure. Attractive results may reflect selection, look-ahead information, omitted observations, or assumptions that do not hold in practice.

The backtesting guide and systems workflow explain how to make those assumptions visible. Doing so does not turn a simulation into a guarantee.

Metrics leave things out

A return does not describe the whole path. Drawdown depends on observation frequency. Volatility does not encompass every type of risk. Model-based alpha depends on the chosen model and estimation sample.

Read definitions alongside the numbers and avoid comparing figures with incompatible periods, costs, or return conventions. Our methodology documents the conventions behind every site example.

Crypto and account safety

A network observation or wallet symbol is not a recommendation or verification of an asset, address, or service. Market, operational, and security concerns require their own analysis.

AnalyticsAlpha does not ask for account credentials, private keys, recovery phrases, wallet signatures, or money transfers. All interactive financial examples are local sample data, not connections to financial services.