Trust and methodology
Everything asked about before the product.
Nine pages on how the system works, what it enforces, and what we do not do — naming no certification we do not hold and no audit that has not happened. Where something is missing, it is written down as missing.
- Security
What is implemented, not what is intended.
Every item on this page is verifiable from the site's own behaviour. We name no certification we do not hold and no audit that has not happened — a claim here is worse than silence.
- Compliance
We sell technology. We do not manage your money.
The distinction is not a wording preference, it is a legal boundary: managing money on someone's behalf is a licensed activity, and selling software that a professional runs themselves is not. We are the second.
- Risk methodology
The limit is written first. The position is whatever survives it.
Risk management here is not a dashboard showing exposure after the fact. It is a condition every order passes before it leaves. What breaches the limit is not sent.
- Execution methodology
The system does not start with the signal. It starts with the rule.
Automated execution is not a strategy. It is a layer running inside assumptions, limits and intervention rules defined before it starts — and written so they can be reviewed after.
- Performance methodology
A figure without its context is not a result. It is a headline.
We do not show an equity curve stripped of what it cost. Any performance figure we publish carries the period and the risk taken to reach it.
- Responsible AI
The model declares where it holds, and where not to act on it.
An undocumented model makes a decision faster without making it better. The most useful thing our intelligence engine says is when its output should not be acted on.
- Data protection
What we hold, why, and what we do not collect.
The shortest data policy is the most honest one: we do not collect what we do not need, and the site carries no tracking of any kind.
- System reliability
What matters is not that it never fails, but how it fails.
Every system fails. The difference between one that can be trusted and one that cannot is what it does in that moment.
- Service status
Status is read from the system, not written about it.
An on-demand configuration and connectivity check, with the last check time and a clear measurement scope.
Trading and investing involve risk and may result in partial or total capital loss. Historical examples or simulations do not guarantee future outcomes.
This section does not provide personal financial advice. Information is general and methodological, and requires the user's own judgement and independent review.