ARX Algorithms
We decide how customer data is used for checkout, licensing, portal access, and support.
This notice explains what personal data we collect, why we collect it, how long we keep it, who we share it with, and what rights you have.
Last updated: 23 May 2026
This page is written to match the ARX Algorithms website, checkout, portal, dashboard, licensing, email, and broker-connection flows.
We decide how customer data is used for checkout, licensing, portal access, and support.
We collect customer, platform, licence, dashboard, and broker-connection data needed to sell, secure, operate, and support ARX products.
Most personal data reaches us when you buy, sign in, connect a broker, activate a licence, use a dashboard, or contact support.
ARX products rely on checkout, licence enforcement, portal delivery, dashboards, broker connectivity, automation controls, and support. That means we need some personal data, technical account data, and broker-connection data, but we aim to keep it tied to those operational needs.
Email address, optional full name, and optional Telegram handle if you provide one through support or account interactions.
Plan type, billing status, subscription dates, Stripe customer IDs, Stripe subscription IDs, Stripe price IDs, and purchase events tied to your account.
Licence key, product entitlement, MT4 account ID where relevant, machine fingerprint where relevant, connected broker identifiers, activation timestamps, reset events, and licence-status history.
Where you choose to connect a supported broker or enable automation, we may process API keys or tokens, connection status, portfolio holdings, cash balance, proposed orders, executed orders, rejected orders, fills, operating mode, approval thresholds, risk limits, and automation status.
Signals, rankings, target holdings, live holdings, order history, performance calculations, benchmark comparisons, health checks, alerts, and audit logs used to operate your dashboard and explain product behaviour.
Magic-link tokens, token hashes, expiry timestamps, signed portal-session tokens, and download-token events used to protect portal access and downloads.
Messages you send us, install or troubleshooting context you provide, and system events needed to investigate fraud, failed billing, access issues, or abuse.
Email capture records from unfinished checkouts, selected plan, checkout-session IDs, reminder-email history, unsubscribe status, and any tips, update, or offer-email preference you actively choose on the pricing page.
We collect personal data directly from you when you buy, start checkout, request a magic link, use the portal, use a dashboard, connect a broker, activate a licence, approve an order, enable automation, or contact support.
We also receive billing and payment metadata from Stripe when checkout completes or subscription events are sent to our webhook.
If you separately opt in to tips, updates, or offer emails, we record that preference so we know whether we can send those follow-up messages lawfully.
Activation, dashboard, automation, and portal-security data are generated when a product verifies a licence, connects to a broker API, calculates signals, creates proposed orders, issues a download token, or creates a portal session.
To create your account, process your order, deliver portal access, issue and enforce your licence, and provide the product you paid for.
To prevent abuse, secure the platform, investigate fraud or chargebacks, protect our intellectual property, troubleshoot support cases, maintain audit trails, and keep the service reliable.
To keep records where tax, accounting, fraud-prevention, or other legal obligations require it.
We share personal data only where there is an operational reason to do so.
We do not sell personal data or license-customer lists to data brokers.
We use signed tokens, hashed magic-link records, authenticated API requests, access controls, and operational logging to protect customer data and software delivery.
Where broker API keys or tokens are used, they should be treated as sensitive credentials. We use them only to provide the connected functionality you enable, such as reading account data, preparing proposed orders, or placing orders in Automated mode. You can revoke broker API access through your broker or by disconnecting the product where that control is available.
In the current portal implementation, your signed portal-session token is stored in your browser's local storage so you can stay signed in between page loads. It is not currently stored as an authentication cookie.
This website may use analytics, tag management, advertising pixels, and session replay tools to understand website performance, measure conversion paths, attribute advertising activity, and improve the buying experience. Current tools may include Google Analytics, Google Ads, Google Tag Manager, Microsoft Clarity, Meta Pixel, and Reddit Pixel where configured and where marketing consent is granted.
You are responsible for securing your own API keys, broker credentials, VPS, MT4 installation, devices, and email inbox.
We do not promise a single blanket retention period for every record because the purpose of the record matters.
Where data is no longer reasonably needed, we aim to delete it, anonymise it, or reduce it to the minimum we still need to keep.
Depending on your location and the applicable law, you may have the following rights:
Some rights are not absolute and may depend on the purpose of the data or the legal basis we are relying on.
For privacy or data-rights requests, contact us through the customer portal where available or through our published support routes: Telegram at https://t.me/arxalgorithms or email at [email protected].
If you are unhappy with how we handle your personal data, you may also complain to the UK Information Commissioner's Office (ICO) at https://ico.org.uk.
This privacy notice has been written against the current ARX product stack and the ICO's guidance on privacy information and individual rights. If the stack changes materially, this notice should be updated as well.