PositionPilot
Understand the risk before you approve a position plan.
PositionPilot helps traders plan, manage and review positions, but structured workflows do not remove market, execution, API, exchange, configuration or personal decision risk.
Market context is information. Position plans are approved by the user. Trading outcomes remain uncertain.
Trading can produce losses.
Crypto markets can move quickly and unpredictably. A trader can lose part or all of the capital committed to a position. PositionPilot provides market context, position planning, account-connected workflow, audit and review tools. It does not guarantee profits, returns, win rates, loss reduction or better outcomes.
Approved rules may execute when their conditions are met.
PositionPilot is built around user-approved position plans. A plan can contain a decision tree: entry logic, protection logic, partial close logic, stop movement logic, exit logic and other allowed rules.
When the user approves that plan, PositionPilot can execute actions that belong to approved rules when the stated conditions are met. PositionPilot does not invent a new live plan on its own, and out-of-plan changes should require a new deliberate approval flow.
The exchange still controls execution.
Orders can be delayed, rejected, partially filled, filled at a different price or not filled at all. Fees, liquidity, latency, outages, API behavior, account permissions, exchange rules and market conditions can affect execution.
PositionPilot can request an action through a supported exchange integration, but the exchange controls account access, matching, balances, settlement and its own operating rules.
Market context is not prediction.
Market Intelligence can organize market structure, events, news, calendar data, snapshots and other context into a form that is easier for humans and algorithms to use. That context can be delayed, incomplete, unavailable or wrong. It is not a promise that price will move in a specific direction.
Sell-first spot control still carries risk.
Sell-first spot control is designed for owned spot inventory: a user can sell first and buy back later inside a structured position. This is not margin short selling and does not remove risk. The user can still lose value, miss a move, buy back at a worse price, pay fees or approve a plan that does not fit the market.
Restricted API keys reduce withdrawal exposure, not trading risk.
PositionPilot is designed around dedicated restricted API keys with withdrawals disabled for ordinary Position Intelligence workflows. Withdrawal-disabled keys reduce withdrawal exposure, but a trading-enabled key can still place or cancel spot orders inside the approved workflow.
Local rules and tax obligations remain the user's responsibility.
Trading rules, exchange access, asset availability, tax treatment, reporting obligations, payment options and product availability can vary by jurisdiction. PositionPilot does not provide legal or tax advice.