Trade IntelUpdated 20 May 2026

Oakhampton AI

Risk Disclosure

Trade Intel is a client-driven research, strategy workflow and approval-gated automation product. In supported connected-account lanes, approved tickets can be submitted to the user's own broker, exchange or venue account. Trading and investing involve risk, including loss of capital. This page is intended to make the product boundaries explicit before users rely on any dashboard, signal, backtest, bot output, strategy card, connector workflow or subscription feature.

1. No guaranteed returns

No dashboard, model, signal, backtest, bot output, benchmark, claim or subscription tier guarantees any return, win rate, income, drawdown limit or future result.

Past performance, simulated performance and settled replay evidence are not reliable indicators of future performance.

2. Research and paper-first operation

Trade Intel is designed for evidence review, research workflow, user-authored strategy testing, paper-first setup, staged approval and customer-controlled connector workflows. It is not a broker, exchange, custodian, managed account provider or execution venue.

Any rule translation, order proposal, risk score, dossier, bot action or connector workflow should be reviewed by the user before any external trade is placed. A user should not approve a ticket unless they understand the instruments, logic, risks, limits and consequences.

If external routing is enabled for a customer workspace, it remains subject to subscription scope, configured permissions, venue support, limits, user approval, account status and applicable law. Approval in Trade Intel does not guarantee that an external venue will accept, execute, price, settle, amend or cancel an order.

3. Market and product risk

Shares, crypto assets, prediction markets and other financial or quasi-financial markets can be volatile and illiquid. Prices may move rapidly and users can lose money.

Crypto assets and prediction markets may have additional risks, including limited regulation, custody risk, wallet or exchange compromise, settlement ambiguity, oracle or event-resolution risk, venue outages, geographic restrictions, data gaps, manipulation risk and sudden changes to market rules.

Prediction-market outcomes can depend on venue-specific resolution criteria. A user may be economically right about an event and still lose because of the market wording, timing, liquidity, fees or dispute process. Prediction-market access may also be restricted by location, venue rules or gambling/derivatives laws.

4. Futures, CFDs, margin and leverage

CFDs, margin FX, futures, options and other derivatives can be complex and high-risk. Leverage can magnify losses and may make a product unsuitable for many users.

CFD support is research, paper-ticket and staged customer-owned broker handoff only unless a separate approved product scope expressly allows more. The CFD provider, not Trade Intel, is responsible for product disclosure, eligibility, leverage, margin and execution.

Trade Intel may show derivatives research or staged workflow support only within the product scope shown to the user. Unless expressly enabled in writing, derivatives content should be treated as informational and should not be read as an invitation to trade CFDs, futures, margin FX or options.

5. Data and model risk

Market data, third-party APIs, AI model output and historical datasets may be delayed, incomplete, incorrectly mapped, biased or unavailable. A user-authored strategy can look robust in historical testing and fail in live conditions.

LLMs and routing services can hallucinate, omit important context, misunderstand user instructions, mishandle stale data or produce plausible but wrong explanations. Users should independently verify important data and must not rely solely on AI-generated output for trading or investment decisions.

BYOK providers may impose their own rate limits, costs, retention rules and model behaviour. Changing a model, prompt, data source or API plan can change a strategy workflow’s output.

6. Technology and automation risk

Software can fail. Integrations can disconnect. Bots can receive stale context, hit permission errors, submit duplicate requests, miss a cancellation window or produce unintended proposals. Users must configure limits, review output and maintain their own account security.

OpenClaw or other bot access should be scoped, audited and revocable. Human approval should remain the default before external execution. Users should use read-only, paper, sandbox or trade-limited API permissions wherever possible and avoid withdrawal-capable API keys.

Connector credentials, bot tokens and BYOK keys can create financial, privacy or operational risk if misconfigured or compromised. Users should rotate keys regularly, revoke unused access and keep independent controls at the broker, exchange or provider level.

7. Regulatory and tax risk

Rules for financial products, crypto assets, prediction markets, tax, licensing and market conduct vary by jurisdiction and may change. Users are responsible for understanding the rules that apply to them.

Users must not use the service for market manipulation, wash trading, spoofing, insider trading, unlawful promotion, sanctions evasion or activity that breaches venue rules or market conduct laws.

Users should seek qualified legal, tax and financial advice before trading, using leverage, connecting live broker, CFD, crypto exchange or prediction-market accounts, or relying on the service for business or professional purposes.

Reference points used for this policy draft

Questions can be sent to ops@oakhampton.ai. Oakhampton is based in Brisbane, Queensland, Australia.