Skip to main content

Legal · Risk Disclosure

Risk Disclosure

Version 1 · Effective 1 January 2025

Binding at activation

This page is binding. Acceptance is required before any live deployment of the Schduler Engine on your exchange account. Your acceptance is recorded immutably with timestamp, IP, user agent, and the version number above. Read each section. If anything is unclear, do not authorize.

Total loss is possible

Crypto markets can move violently in any direction. The engine includes risk controls but no automation can prevent loss in adverse market conditions.

Past performance is not predictive

Our master-account live deployment and the backtest record are shown for transparency. They do not guarantee future results on your account. Paper mode cannot perfectly replicate live conditions.

Exchange risk is real

Your funds remain at your exchange. Schduler is not responsible for losses caused by exchange failures, hacks, outages, or forced liquidations on the exchange's side. If your exchange halts withdrawals or freezes your account, Schduler cannot return your funds.

Execution risk is real

Slippage, API rate limits, latency, and network issues can cause fills to differ from intent. Paper mode mirrors live mode but cannot perfectly replicate live market microstructure.

You bear all market risk

Schduler is software. You are the operator of your account. You decide capital, asset, risk preset, and whether to run live or paper. You can pause at any time. The kill switch flattens any open position at market and revokes container authorization.

Authorization is signed and recorded

Every activation, pause, resume, and disclosure acceptance is written to an append-only audit log. You can review the full trail of your account at any time from the Audit page. The acceptance you make at activation is recorded with your user ID, the disclosure version number above, the timestamp, your IP address, and your user agent. It is immutable.

Risk Disclosure v1 · Effective 1 January 2025

The full binding text appears at /activate before any live deployment, where acceptance is recorded against this exact version.