Local by design. Clear about the limits.

One local execution authority.

Desktop supervises a local backend. That backend owns active plans, evaluates eligible data and sends orders to IBKR TWS or IB Gateway. Chart clients display snapshots and send commands; they do not independently execute an alternative plan.

Pairing separates clients from credentials.

Clients pair with the local service. The extension keeps authorization in its relay rather than exposing it to the TradingView page. Website account and subscription services are separate from the broker’s local API connection.

Connection health is visible.

Fresh data and a functioning broker connection are required for automatic execution. Branch health, reason codes and alerts report degraded, missing or blocked inputs. If your computer sleeps, the backend stops or the required source disconnects, do not assume an exit remains protected.

Recovery checks facts before acting.

The backend reconciles orders, executions and positions after a restart. A recovery barrier prevents execution while reconciliation is incomplete. Startup catch-up orders can be held for your decision in Desktop rather than being silently sent.

Evidence you can inspect.

Recorded events, replay and redacted incident exports help explain a decision. Redaction removes sensitive fields from the generated package; review any additional files you attach before sharing them.

Website, accounts and updates.

Website services manage accounts, subscriptions and device activation. They do not route brokerage orders. Published macOS installers are signed and notarized, and update metadata is signed and checked against rollback protection. Optional website analytics are collected only after you opt in. Existing subscriptions and agreements remain with the original service.

Report a concern.

Contact contact@optiontrigger.com with a concise description and a redacted reproduction. Do not send credentials, access tokens or complete account identifiers.