This is a working template prepared for review by qualified counsel in the United States, India, the United Kingdom and the European Union. It is not yet in force and creates no rights or obligations until a final version is published.
- We don’t execute trades ourselves. We send your orders to the broker you chose, which executes them under its own execution policy.
- Every order passes the same risk checks, in the same order, for every customer. No one gets priority.
- We take no payment for order flow and no commission from brokers. Any future referral arrangement will be disclosed here before it starts.
- Staff may not trade ahead of, or on the basis of, customer signals.
The summary helps you navigate; the sections below are the document.
1Our role in your orders
- AlgoNexus does not hold client money or assets and does not execute orders on a venue. When live features are available, we transmit instructions to your broker through its official API. Your broker is responsible for execution, clearing and settlement under its own best-execution or order-execution policy.
- In the UK and EU, transmitting orders on a client’s behalf can be a regulated activity (“reception and transmission of orders”). We will do so only once authorised; see Regulatory Status and our Best Execution policy.
2Order lifecycle
Every order moves through a fixed state machine, recorded in a tamper-evident audit log:
| State | What happens |
|---|---|
| Proposed | A model or rule creates an order intent with its reasons. |
| Approved | You approve it (Copilot) or your signed policy authorises it (Autopilot). |
| Risk-checked | The risk gate re-checks limits against live account state at submit time; any failure or missing input blocks the order. |
| Submitted | Sent to your broker with an idempotency key to prevent duplicates. |
| Acknowledged / filled / rejected / cancelled | Status comes from the broker and is reconciled; we never assume a fill. |
3Order types and timing
- By default we use limit orders with a price band around the current quote, to protect against poor fills in fast markets. Market orders are used only where a limit order is not supported and the policy allows it.
- Orders are sent only during the venue’s regular session unless you enable extended hours where your broker supports it.
- Unfilled day orders expire at the session close. Proposals in Copilot expire at the time shown on the idea.
4Fair handling across customers
- Orders are processed in the order they pass the risk gate. Plan tier never affects order priority.
- We do not aggregate different customers’ orders into one order; each order is sent to that customer’s own broker account.
- When a signal applies to many customers, submissions are spread over a short randomised window so that no group of customers systematically trades ahead of another and market impact is reduced.
5Errors
If an order is sent in error because of our systems — for example outside your policy or in duplicate — we will notify you, work with your broker to correct it where possible, and compensate you for any loss caused by our error, in line with the Terms and applicable law. Report suspected errors to support@algonexus.trade.
6Conflicts of interest we have identified
| Potential conflict | How we manage it |
|---|---|
| Revenue from trading activity | We charge flat subscriptions only. No commissions, no payment for order flow, no performance fees. Our revenue does not increase when you trade more. |
| Broker relationships | We receive no payment from brokers today. Any future referral or partnership fee will be disclosed here and in the app before it starts, and will never influence which broker is suggested or how orders are routed. |
| Staff personal trading | Staff with access to signals must pre-clear trades, may not trade ahead of customer orders, and are subject to holding periods and monitoring. |
| Own-account positions | AlgoNexus does not trade for its own account or take the other side of customer orders. |
| Use of customer data for model training | Only de-identified or aggregated data, under the Privacy Notice; no customer’s orders are used to trade ahead of others. |
| Promoting paid plans | Plan features never change the risk checks applied to your orders. |
7Governance
We maintain a conflicts register reviewed at least annually by [compliance function] and the board. Where a conflict cannot be prevented, we disclose it to you clearly before you are affected.