Privacy Policy

We may collect account details such as name, email, organisation name, login and authentication records, subscription status, customer support messages and product usage events.

Where a user connects external services, we may store configuration metadata, masked credential references, encrypted credential material, token prefixes, permission settings, broker, CFD account, exchange, prediction-market, model-provider or data-source labels, bot connection settings, risk limits, strategy settings, approval records, audit logs, staged-order records and related workspace activity.

BYOK LLM/router keys, market-data keys and broker, CFD account, crypto exchange or prediction-market connector credentials may be stored only for the purpose of operating the user’s workspace and configured workflows. Users must not provide seed phrases, private wallet keys, withdrawal-capable keys or unrestricted asset-transfer credentials unless Oakhampton has expressly agreed in writing to a separate scope.

We may collect technical information such as IP address, browser and device data, session identifiers, security events, cookies or local-storage records, API request metadata, error logs and performance telemetry.

Payment card details are handled by Stripe. Oakhampton should not store full card numbers or card security codes in Trade Intel.

We usually collect information directly from users when they create an account, subscribe, configure a workspace, connect a bot, contact support or use the service.

We may also receive information from Stripe, broker, CFD account or exchange integrations, prediction-market platforms, data vendors, LLM/router providers, OpenClaw connections, analytics/security tooling and other service providers where that is necessary to operate the product.

We use personal information to create and secure accounts, provide the service, process subscriptions, maintain audit trails, deliver support, improve product reliability, investigate misuse, comply with legal obligations and communicate service notices.

We use workspace configuration data to run user-authorised workflows, connect approved providers, enforce subscription scope, check permissions, stage orders, route approvals, maintain audit logs, support investigations and help users diagnose connector or model-provider issues.

We may use aggregated or de-identified information to understand usage patterns, improve evidence workflows, monitor system performance and develop product features.

We may disclose information to service providers that help us operate the product, including cloud hosting, payment processing, email, analytics, security, logging, customer support, bot connectivity, model providers, market-data vendors, broker, CFD account, exchange or prediction-market connectors and data-processing providers.

Where a user enables an external connector, relevant order, account, symbol, strategy, approval, credential or workflow information may be transmitted to that third-party provider to perform the user-authorised action.

We may disclose information where required by law, where reasonably necessary to protect users, markets, Oakhampton or third parties, or in connection with a business transfer, dispute, investigation or enforcement process.

Some providers may process or store information outside Australia. This may include cloud, payment, analytics, support, model, data, broker, CFD account, exchange, bot-connectivity and infrastructure providers. Where practical, Oakhampton will use reputable providers and account controls appropriate for the sensitivity of the information.

We use reasonable technical and organisational safeguards for account, workspace, credential, connector and audit data, including encryption for stored sensitive credential material where supported by the product architecture, tenant scoping, access controls, logging and operational monitoring.

No online service can be guaranteed secure. Users must protect their own credentials, use narrow API permissions wherever possible, rotate compromised keys, revoke bot tokens they no longer need and immediately report suspected compromise.

If a user supplies prohibited or excessive credentials, including withdrawal-capable keys, seed phrases or private wallet keys, Oakhampton may delete, disable or refuse to use those credentials.

We keep personal information for as long as reasonably needed for the purposes described in this policy, including account operation, support, billing, audit, security, legal and dispute-resolution purposes. We may de-identify or delete information when it is no longer required.

Users may request access to personal information we hold about them, or ask us to correct information that is inaccurate, out of date, incomplete or misleading.

We may need to verify identity before acting on a request. Some information may be retained where required for security, audit, billing, legal or dispute reasons.

Privacy questions or complaints can be sent to ops@oakhampton.ai. We will review the request and respond within a reasonable period.

If a user is not satisfied with our response, they may be able to contact the Office of the Australian Information Commissioner or another relevant regulator.

We may update this policy as the product, law or information-handling practices change. The current version will be published on this website with an updated date.