Privacy Policy | AlgoAlpha

AlgoAlpha recognises the importance of protecting Personal Data, User Content, source code, communications, and other information entrusted to us.

This Privacy Policy explains how AlgoAlpha (“AlgoAlpha,” “we,” “us,” or “our”), an online service operated from Singapore under the AlgoAlpha brand, collects, uses, stores, anonymises, shares, and otherwise processes information when you access or use the Services.

“Services” means all websites, applications, subscriptions, indicators, signals, analytical tools, educational materials, artificial-intelligence-assisted features, code-generation and code-analysis tools, compilers, testing and validation tools, APIs, developer tools, protocol-based integrations, automated systems, connected-account features, communities, documentation, content, and other products or services provided under the AlgoAlpha brand, whether currently available or introduced in the future.

References to a category of Service do not mean that every product, feature, model, integration, exchange, market, or capability is currently available. The information collected depends on the Services you actually use and the content you provide or cause another service to transmit.

For purposes of this Privacy Policy:

“Personal Data” means information relating to an identified or reasonably identifiable person.
“User Content” means content submitted to, transmitted through, created within, or generated using the Services, including prompts, conversations, messages, source code, files, project context, API or tool requests, feedback, outputs, and related materials.
“Interaction Data” means information about how a user interacts with a Service, including clicks, edits, accepted or rejected suggestions, feature activity, compiler events, tool activity, and other usage signals.
“Product Improvement” means developing, testing, evaluating, maintaining, and improving the Services, including prompts, retrieval, memory, tools, interfaces, safety systems, automated systems, and artificial-intelligence or machine-learning models.
“Anonymised Data” means information from which direct identifiers and associated mapping keys have been removed and which is not intended to be reasonably linkable to an identifiable person.

For applicable data-protection purposes, AlgoAlpha is responsible for Personal Data processed through the Services unless a third-party provider independently determines its own purposes and methods of processing under its own terms.

Our privacy and data-protection contact is admin@algoalpha.io.

Collection of Information

AlgoAlpha collects different categories of information depending on how you interact with us and which Services you use.

Account and Contact Information

We may collect:

your name or chosen display name;
email address;
country or region;
account, customer, or membership identifiers;
TradingView username;
Discord username;
subscription or access status;
communication preferences; and
other information you provide when creating or administering an account.

AlgoAlpha currently uses Wix or related third-party account infrastructure for login and authentication. The authentication provider may collect and process passwords and login credentials under its own privacy terms.

AlgoAlpha does not ordinarily receive or directly store your complete Wix account password.

Providing a TradingView or Discord username does not provide AlgoAlpha with your password, authentication token, or unrestricted access to that account.

Payment and Transaction Information

When you purchase, subscribe to, or pay for a Service, we may collect or receive:

billing name and address;
email address;
order details;
products or plans purchased;
subscription status;
billing interval;
transaction identifiers;
payment status;
payment-method type;
currency;
renewal information;
refund and cancellation information;
fraud indicators;
dispute or chargeback information; and
limited payment-method details supplied by a payment provider.

Complete payment-card numbers, card security codes, online-banking credentials, and PayPal login credentials are generally collected and processed directly by Wix, Stripe, PayPal, or another payment provider rather than by AlgoAlpha.

Payment providers may independently collect additional information for payment processing, fraud prevention, identity verification, dispute management, regulatory compliance, and other purposes governed by their own privacy policies.

Technical, Device, and Usage Information

When you access or use the Services, we may automatically collect:

Internet Protocol address;
approximate location derived from an IP address;
browser type and version;
operating system;
device type;
device, browser, session, or account identifiers;
referring website or source;
pages, products, and features viewed;
buttons, links, and interface elements selected;
navigation paths;
session dates, timestamps, and duration;
login and authentication events;
application interactions;
feature usage;
cursor, focus, input, keystroke-level, and session-replay events where enabled;
performance and latency information;
error messages and crash reports;
security events;
cookie, analytics, and tag identifiers;
rate-limit and usage information; and
other technical, diagnostic, telemetry, or operational information.

Communications and Support Information

We collect information you provide when communicating with AlgoAlpha through:

email;
website forms;
support channels;
AlgoAlpha-operated community spaces;
surveys;
reviews;
feedback forms;
billing or payment disputes; and
other communication methods.

This may include the contents of your communication, attachments, account details, transaction information, technical information, and records of our response.

AlgoAlpha does not operate a general feature designed to collect your private messages from unrelated third-party services. We may, however, process messages you send directly to AlgoAlpha or in support or community spaces accessible to us.

User Content and AI-Assisted Interaction Information

When you use conversational, AI-assisted, research, analytical, coding, or other interactive Services, we may collect and process:

complete conversations;
prompts and instructions;
text, code, or other content entered into input fields, editors, or canvases, including drafts where the Service records them;
questions and messages;
files, documents, images, links, and other submitted materials;
retrieved information;
model inputs and outputs;
tool requests and results;
conversation titles and history;
saved items, strategies, projects, or configurations;
ratings, corrections, reports, and feedback;
quality and safety classifications;
errors;
performance and reliability information; and
other content or metadata associated with the interaction.

Conversation history and saved content may be retained so that users can review prior interactions, continue work, and use features that depend on history or context.

Coding, Compiler, Execution, and Validation Information

When you use coding, compilation, execution, testing, debugging, or validation Services, we may collect and process:

source code and scripts;
code typed, pasted, uploaded, imported, or edited;
files and project context;
generated code;
code revisions, diffs, and version history;
compiler inputs and outputs;
execution, validation, backtesting, and testing results;
errors, warnings, stack traces, and diagnostics;
dependencies, environment information, and configuration;
tool calls and tool results;
copied, accepted, rejected, edited, or regenerated suggestions;
application clicks and workflow events;
explicit and implicit feedback; and
associated account, session, usage, safety, and performance metadata.

Implicit feedback may include whether an Output was accepted, copied, edited, compiled, executed, rejected, regenerated, or subsequently corrected.

API, Developer Tool, and Protocol Integration Information

When you use an AlgoAlpha API, developer tool, compiler endpoint, protocol-based integration, or related machine-readable interface, we may log and process:

complete request content;
tool names and tool arguments;
prompts and instructions;
source code;
files and project context;
requested endpoints, tools, models, or features;
generated responses or outputs where applicable;
compiler, execution, testing, or validation activity;
timestamps;
originating IP address;
account, workspace, or organisation identifiers;
API credential identifiers;
token, credit, and usage information;
request and response status;
rate-limit information;
safety and policy classifications;
errors and diagnostic information;
suspicious or potentially prohibited activity; and
other content transmitted by the client.

All API and developer-tool requests are subject to automated safety, security, and legal monitoring.

Requests may also be reviewed by authorised personnel where reasonably necessary for service operation, support, debugging, safety, security, fraud prevention, abuse investigation, legal compliance, or policy enforcement.

AlgoAlpha may retain an identifier, hash, or secure representation of an AlgoAlpha-issued API credential. We do not intentionally retain the complete secret portion of an issued credential in ordinary application logs after issuance.

External AI Assistants, Coding Agents, and Clients

A third-party AI assistant, coding agent, command-line tool, integrated development environment, protocol client, plugin, or other application may transmit content to an AlgoAlpha Service.

Depending on the external client and task, AlgoAlpha may receive:

tool requests and arguments;
source code;
files;
project context;
prompts or instructions;
generated content;
compiler or execution inputs;
diagnostics and errors;
account or request identifiers;
usage metadata; and
any other content the client includes in the request.

AlgoAlpha does not necessarily receive the user’s entire external conversation. We receive the content the external client chooses or is instructed to transmit.

The external client or model provider independently processes information under its own privacy policy, terms, account type, workspace settings, and data controls. AlgoAlpha does not control that independent processing.

Connected Accounts and Automated Service Information

When you connect a third-party trading, financial, data, software, or other account to an AlgoAlpha Service, we may collect and process:

the connected provider or exchange;
account and subaccount identifiers;
API keys, API secrets, passphrases, access tokens, or similar credentials;
credential permissions and connection status;
balances, holdings, available funds, or margin;
open positions;
outstanding and historical orders;
transactions and execution history;
asset or instrument information;
allocation and position-sizing information;
automation settings;
order type, take-profit, stop-loss, leverage, or risk settings;
errors and connection diagnostics; and
other information necessary to authenticate, operate, monitor, secure, or support the connected feature.

Credentials required for continuous operation may be stored encrypted at rest.

Automated systems and authorised AlgoAlpha personnel may decrypt and access connected-account credentials where reasonably necessary to operate the Service, diagnose a connection, provide support, debug, investigate a security incident, or protect the Service.

Raw credentials are excluded from ordinary application logs, general analytics, error reports, and support records. Restricted encrypted backups may contain credential records as part of the applicable database.

AlgoAlpha does not require permission to initiate withdrawals or asset transfers for automated trading Services. Read-only access to deposit, withdrawal, or transfer information may be processed where required for account visibility.

Connected-account credentials are not used for model training or Product Improvement datasets.

Analytics and Interaction Metadata

AlgoAlpha may use analytics, tag-management, monitoring, and similar services to collect metadata and usage events concerning how visitors and users interact with the Services.

This may include:

page views;
clicks and navigation paths;
feature usage;
session events;
timestamps;
browser and device information;
approximate location derived from IP;
performance and latency information;
referral information; and
technical errors.

Raw conversations, source code, files, and form-field contents are not intentionally provided to general analytics or tag-management providers. AlgoAlpha-controlled application logging, monitoring, or replay systems may record content entered into the Services and detailed interaction events. Raw content may also be processed by hosting, storage, AI, compiler, or infrastructure providers where necessary to provide the relevant Service.

Information from Third Parties

We may receive information from third parties involved in operating or providing the Services, including:

website and authentication providers;
payment processors;
AI and model providers;
connected platforms;
TradingView;
Discord;
exchanges and financial platforms;
hosting, storage, and cloud providers;
analytics and tag-management providers;
security and fraud-prevention providers;
communication and customer-support providers;
referral partners; and
services you choose to connect.

The information received depends on the provider, integration, permissions, and Service involved.

Information We Do Not Intentionally Request

AlgoAlpha does not operate dedicated features designed to collect:

precise GPS location;
address-book contacts;
camera or microphone recordings;
biometric identifiers;
health information;
unrelated government-issued identity documents;
Social Security numbers; or
private messages from unrelated services.

Users may nevertheless include sensitive or third-party information in User Content. Any information voluntarily submitted or transmitted may be processed under this Privacy Policy.

Unless specifically required by a connected feature, do not submit:

third-party account passwords;
Discord authentication tokens;
TradingView passwords;
private cryptographic keys;
cryptocurrency wallet seed phrases;
complete payment-card credentials;
unnecessary government identifiers; or
credentials that could provide access to an account or system.

If you accidentally expose a credential, revoke or rotate it immediately. AlgoAlpha cannot guarantee that an accidentally submitted credential was not processed, logged, or transmitted before it was detected.

Where reasonably possible, we may redact, restrict, isolate, or delete exposed credentials.

Methods of Information Collection

AlgoAlpha collects information through several methods.

Information You Provide Directly

We collect information when you:

create or manage an account;
purchase or subscribe to a Service;
provide a TradingView or Discord username;
use an interactive or AI-assisted Service;
type, paste, upload, or import code or files;
submit an API or tool request;
connect an account or integration;
enable an automated feature;
provide feedback;
contact support;
complete a survey;
submit a review; or
otherwise communicate with us.

Information Collected Automatically

We may collect information automatically through:

server logs;
cookies and local storage;
application telemetry;
analytics and tag-management systems;
authentication systems;
security and fraud-prevention tools;
error-monitoring systems;
compiler and execution logs;
API gateways;
usage meters; and
infrastructure-monitoring systems.

Information Received from Service Providers and Connected Services

We may receive information from website, authentication, payment, hosting, analytics, AI, security, exchange, platform, and other providers involved in operating a Service or fulfilling a user-directed integration.

Purpose of Information Collection

AlgoAlpha may collect and process Personal Data, User Content, and Interaction Data to:

create, authenticate, secure, and administer accounts;
provide and operate the Services;
provide access to trading tools, indicators, signals, applications, communities, and content;
fulfil purchases and subscriptions;
grant, verify, or remove TradingView, Discord, or other platform access;
process payments, renewals, refunds, cancellations, disputes, and chargebacks;
generate, retrieve, analyse, compile, execute, validate, test, or debug content and code;
preserve conversations, projects, saved items, configurations, and history;
operate APIs, developer tools, connected accounts, and automated features;
provide customer support;
investigate and resolve technical issues;
monitor quality, reliability, performance, and usage;
conduct Product Improvement;
develop and improve artificial-intelligence and machine-learning models;
process explicit and implicit feedback;
improve prompts, retrieval, memory, routing, tools, guardrails, interfaces, and workflows;
detect fraud, abuse, spam, attacks, credential exposure, unauthorised access, and misuse;
monitor API and tool activity for safety, security, billing, and legal compliance;
enforce our Terms & Conditions and other policies;
protect AlgoAlpha, users, service providers, and third parties;
maintain transaction, accounting, tax, and business records;
establish, exercise, or defend legal claims;
comply with applicable laws, regulations, court orders, and valid legal processes;
send service, account, subscription, security, legal, and operational communications;
send marketing communications where permitted; and
create aggregated, statistical, or Anonymised Data.

We will not use Personal Data for a materially incompatible new purpose without providing appropriate notice and obtaining consent where applicable law requires it.

Grounds for Processing

The legal grounds on which AlgoAlpha processes information depend on the jurisdiction and activity.

They may include:

Providing the Services and Performing an Agreement

Processing may be necessary to create an account, fulfil a purchase, provide a requested Service, operate an integration, process a payment, generate an Output, or perform our obligations to a user.

Consent

We may rely on consent for optional processing, connected services, certain marketing communications, cookies or similar technologies, or another activity where consent is required.

Where processing is based on consent, you may withdraw consent as described below. Withdrawal does not affect processing that occurred lawfully before withdrawal.

Legitimate Business, Safety, and Security Interests

Where permitted by applicable law, we may process information where reasonably necessary to:

operate, maintain, and improve the Services;
provide support;
monitor quality and reliability;
conduct Product Improvement;
maintain security;
prevent fraud and abuse;
investigate incidents;
enforce our agreements; and
protect AlgoAlpha and others.

Legal Obligations and Claims

We may process and retain information for tax, accounting, payment, consumer-protection, sanctions, regulatory, litigation, law-enforcement, security, and other legal purposes.

Product and Service Improvement

Eligible Data

Eligible User Content and Interaction Data collected through AlgoAlpha applications, APIs, developer tools, compiler services, protocol-based integrations, and other interactive Services may be selected for Product Improvement where AlgoAlpha considers the information useful or valuable.

Eligible data may include:

conversations and prompts;
source code and files;
project context;
generated Outputs;
tool and compiler interactions;
edits and revisions;
accepted, rejected, copied, or regenerated suggestions;
testing and validation results;
ratings, corrections, and feedback; and
other content or interaction signals generated through an interactive Service.

General account data, billing data, raw IP and device identifiers, security records, and credentials are not eligible for model-training datasets as described below.

Product Improvement Activities

Product Improvement may include:

developing, testing, and evaluating prompts;
improving retrieval, memory, context assembly, tools, routing, interfaces, workflows, and safety systems;
debugging and reliability testing;
building benchmarks and evaluation datasets;
developing, pre-training, continued pre-training, training, fine-tuning, distilling, or otherwise improving artificial-intelligence and machine-learning models;
reinforcement learning and other post-training methods;
model comparison and quality evaluation; and
improving other automated systems or components of the Services.

Anonymisation Before Training and Evaluation

Before eligible User Content is included in a model-training or internal evaluation dataset, AlgoAlpha will remove direct account identifiers and associated mapping keys and apply measures designed to make the resulting data not reasonably linkable to an identifiable user.

We may use automated and authorised human review to remove or reduce identifying information contained in free text, code, files, metadata, or other content.

Where content cannot be sufficiently anonymised with reasonable confidence, AlgoAlpha may exclude it from model-training or evaluation datasets.

The following categories are excluded from model-training datasets:

account identifiers;
billing and payment metadata;
raw IP-address logs;
device-identification logs;
fraud, abuse, and security-investigation records;
passwords;
authentication secrets;
private API credentials;
connected-account credentials;
private cryptographic keys; and
wallet seed phrases.

Human Review Before Anonymisation

Authorised AlgoAlpha personnel and contractors may access identifiable User Content before anonymisation where reasonably necessary for:

customer support;
debugging;
quality evaluation;
safety review;
service operation;
security monitoring;
fraud or abuse investigation;
policy enforcement; or
legal compliance.

Personnel and contractors with access must be subject to written confidentiality and data-protection obligations.

Private Training and Evaluation Infrastructure

Anonymised training and evaluation data may be stored or processed through private, access-restricted:

cloud-computing environments;
storage systems;
code repositories;
dataset repositories;
model-hosting platforms; and
machine-learning infrastructure.

AlgoAlpha does not intentionally publish these datasets or authorise infrastructure providers to use them for unrelated independent model training.

Model-Training Opt-Out

You may opt out of the use of future User Content for model training by emailing admin@algoalpha.io from the email address associated with your account.

Your request should identify the relevant account and Services.

The opt-out becomes effective after AlgoAlpha processes the request.

Unless mandatory law requires otherwise, the opt-out does not apply retroactively to:

content collected before the request was processed;
content already anonymised;
existing training or evaluation datasets;
completed evaluations;
derived statistics;
trained or fine-tuned models;
model weights;
checkpoints; or
information no longer reasonably linkable to your account.

The opt-out applies to model training. It does not prevent processing required to:

provide or maintain the Services;
preserve user-requested history;
operate compilers, tools, APIs, or integrations;
maintain security;
prevent fraud or abuse;
provide support;
debug or evaluate systems without updating model weights;
enforce our agreements; or
comply with law.

Where applicable law provides broader mandatory rights, AlgoAlpha will process the request in accordance with those requirements.

Continued Use of Anonymised Data

AlgoAlpha may retain and use Anonymised Data indefinitely for Product Improvement, research, analytics, safety, reliability, and other lawful purposes.

Except where applicable law requires otherwise, AlgoAlpha is not required to reverse completed model training, alter existing model weights, remove completed evaluations, or identify information that can no longer reasonably be linked to a user.

Third-Party AI Providers and External AI Clients

AI Providers Used by AlgoAlpha

AlgoAlpha may use third-party AI and model providers to process prompts, code, files, context, instructions, and Outputs necessary to provide a Service.

Where AlgoAlpha sends eligible production content through its own OpenAI API account, AlgoAlpha uses a project configured for OpenAI’s Zero Data Retention control and does not opt in to permitting OpenAI to use the API inputs or outputs for OpenAI’s independent model training.

Zero Data Retention applies only to eligible OpenAI endpoints, capabilities, and traffic sent through AlgoAlpha’s configured project. It remains subject to provider-specific technical limitations, safety controls, contractual terms, and legal exceptions.

Zero Data Retention concerns the provider’s handling of eligible content. It does not prevent AlgoAlpha from storing and processing information in AlgoAlpha-controlled or AlgoAlpha-contracted systems as described in this Privacy Policy.

AlgoAlpha may add, replace, or change AI providers as the Services evolve. Where a change materially affects how User Content is processed, we will update this Privacy Policy or provide additional notice where required.

User-Controlled External AI Clients

A user may access an AlgoAlpha compiler, tool, API, or integration through ChatGPT, Codex, Claude Code, another AI assistant, or another external client.

The user’s conversation and environment on that external service are processed under the external provider’s own plan, workspace, settings, terms, and privacy policy.

AlgoAlpha’s OpenAI Zero Data Retention configuration does not apply to a user’s separate ChatGPT or Codex account, and it does not apply to another provider’s service.

AlgoAlpha controls only the information received by AlgoAlpha through its own Services and the processing AlgoAlpha performs after receipt.

No Sale of Personal Data or User Content

AlgoAlpha does not sell or rent Personal Data or User Content for money.

AlgoAlpha does not intentionally provide raw conversations, source code, files, or API request content to:

data brokers;
unrelated advertisers;
third parties for their independent marketing;
third parties for unrelated commercial purposes; or
AI providers for those providers’ independent model training.

This does not prevent information from being processed by service providers where reasonably necessary to operate, secure, support, develop, or improve the Services.

Some privacy laws may define certain analytics disclosures as a “sale,” “sharing,” or targeted advertising even where no money is exchanged. Where such a law applies, AlgoAlpha will provide any rights or controls legally required.

Raw User Content is not used for targeted advertising.

Website, Account, and Authentication Providers

AlgoAlpha uses website, commerce, account-management, and authentication providers, including Wix, to operate websites, forms, login, customer accounts, subscriptions, and related functionality.

These providers may process:

account and contact information;
login and authentication information;
form submissions;
order and subscription information;
website and device information;
cookies and identifiers;
IP addresses; and
other information processed through enabled features.

They process information under their own privacy policies and contractual arrangements with AlgoAlpha.

Payment Providers

AlgoAlpha may use Wix payment functionality, Stripe, PayPal, and other payment providers to process payments, subscriptions, refunds, fraud checks, disputes, and related services.

Payment providers may receive:

payment and billing information;
contact information;
transaction information;
IP and device information;
fraud-prevention information;
refund information; and
dispute or chargeback evidence.

Payment providers may process information both on AlgoAlpha’s behalf and independently for payment-network, fraud-prevention, regulatory, legal, security, and compliance purposes.

AI, Cloud, Hosting, and Operational Providers

AlgoAlpha may disclose or transmit information to service providers that perform functions such as:

AI inference;
cloud computing;
hosting and storage;
databases and content delivery;
authentication;
email and communications;
analytics and tag management;
security monitoring;
fraud prevention;
error logging and observability;
customer support;
code compilation, execution, testing, and sandboxing;
private code, dataset, and model hosting;
accounting;
legal services; and
auditing.

These providers receive information where reasonably necessary to perform their assigned functions, protect the Services, or comply with applicable legal obligations.

AlgoAlpha’s infrastructure and providers may change over time. This Privacy Policy identifies relevant provider categories and selected user-facing providers rather than publishing every component of our technical stack.

TradingView, Discord, and Other Connected Platforms

AlgoAlpha may process or transmit your TradingView, Discord, or other connected-platform username or account identifier to:

verify entitlement;
provide or remove product or community access;
administer subscriptions;
provide support;
operate an integration; or
prevent unauthorised access.

Connected platforms independently process information under their own privacy policies.

Connected Accounts and User-Directed Disclosures

We may disclose or transmit information where you:

enable an integration;
connect an account;
authorise an automated feature;
request a disclosure;
publish or share content;
invite another user; or
direct us to transmit information to another service.

Information disclosed at your direction may then be processed under the recipient’s own privacy policy.

Business Transfers and Future Registration

Information may be transferred to:

a future registered entity operating AlgoAlpha;
an affiliate;
a successor operator;
a purchaser;
an investor;
a merger partner;
an acquirer;
a financing party; or
another party involved in incorporation, restructuring, financing, insolvency, sale, or transfer of the Services or related assets.

Any transfer may include Personal Data and User Content, subject to applicable law and appropriate confidentiality or data-protection arrangements.

Legal, Government, and Law-Enforcement Requests

AlgoAlpha does not voluntarily provide Personal Data or User Content to governments or law-enforcement authorities merely because an informal request is made.

We may preserve or disclose information where we reasonably believe doing so is:

required by applicable law;
required by a valid court order, warrant, subpoena, or other legal process;
required by a competent regulator;
necessary to comply with a lawful government requirement;
necessary to investigate fraud, abuse, or a security incident;
necessary to establish, exercise, or defend legal claims;
necessary to enforce our agreements; or
permitted in an emergency involving a credible risk of death, serious physical harm, or substantial damage.

Where legally permitted and reasonably practical, AlgoAlpha may assess the validity and scope of a request, seek clarification, attempt to limit disclosure to information reasonably required, object to requests that appear unlawful or excessively broad, and notify the affected user.

AlgoAlpha may be legally prohibited from providing notice.

Data Retention, Account Closure, and Anonymisation

General Retention

AlgoAlpha does not apply a single fixed maximum retention period to every category of information.

Depending on the category and purpose, information may be retained for an indefinite period where permitted by applicable law and where AlgoAlpha considers it relevant to:

provide the Services;
maintain account, conversation, project, or saved-item history;
maintain connected features;
conduct Product Improvement;
train and evaluate models;
provide support;
protect security;
prevent fraud and abuse;
resolve disputes and chargebacks;
comply with accounting, tax, regulatory, or legal obligations;
preserve evidence; or
establish, exercise, or defend legal claims.

Retention may also depend on the sensitivity of the information, the status of an account, backup cycles, pending investigations, and the technical ability to identify the information.

The absence of a fixed retention period does not limit rights or retention restrictions that apply under mandatory law.

Active Accounts

While an account remains active, conversations, code, files, project history, saved items, interaction history, and related metadata may be retained indefinitely unless AlgoAlpha removes, anonymises, or otherwise processes them.

Account-Closure and Deletion Requests

Account-closure or deletion requests must be submitted to admin@algoalpha.io from the email address associated with the account.

Following a valid request, AlgoAlpha may:

close or disable the account;
remove information from user-facing interfaces;
detach and remove direct account identifiers and associated mapping keys from eligible User Content;
anonymise eligible User Content;
retain transaction, legal, safety, fraud, security, and dispute records where necessary or permitted;
retain restricted backup copies until overwritten or retired; and
retain Anonymised Data indefinitely for Product Improvement and other lawful purposes.

Account closure or deletion does not necessarily mean that every underlying record or item of User Content is destroyed.

Once information has been anonymised and can no longer reasonably be associated with your account, AlgoAlpha may be unable to identify, locate, return, or delete it in response to a later request.

Except where applicable law requires otherwise, account closure or deletion does not require AlgoAlpha to:

reverse completed model training;
alter existing model weights;
delete completed evaluations;
remove derived aggregate statistics;
identify anonymised information in historical datasets; or
delete records required or permitted for transaction, legal, security, fraud-prevention, or dispute purposes.

API and Safety Logs

API, tool, compiler, security, and monitoring records may be retained for as long as AlgoAlpha considers reasonably relevant to:

safety monitoring;
security investigation;
abuse prevention;
audit requirements;
billing;
customer support;
policy enforcement;
legal compliance; and
legal claims.

Payment and Transaction Records

Payment, refund, accounting, tax, dispute, and chargeback information may be retained for periods required or permitted by applicable law, payment-network rules, and payment-provider requirements.

Backups

Deleted, detached, or anonymised information may remain in restricted backups, archives, or disaster-recovery systems until the applicable backup is overwritten or securely retired.

Backup information will not ordinarily be restored to active use except where required for disaster recovery, security, system integrity, or legal compliance.

Security of Personal Information

AlgoAlpha uses administrative, organisational, and technical measures designed to protect Personal Data and User Content against:

unauthorised access;
unauthorised disclosure;
alteration;
destruction;
loss;
misuse; and
theft.

Depending on the system and information involved, these measures may include:

authentication and access controls;
least-privilege permissions;
encryption in transit;
encryption or comparable protection at rest;
credential-management controls;
restricted personnel access;
confidentiality obligations;
logging and monitoring;
network and application security;
secure cloud and hosting providers;
backups; and
incident-response procedures.

No online service, transmission method, storage system, or security control is completely secure. AlgoAlpha cannot guarantee absolute security.

AlgoAlpha will investigate suspected data breaches and notify affected users and relevant authorities where notification is required by applicable law.

International Data Transfers

AlgoAlpha is operated from Singapore and provides Services internationally.

Personal Data and User Content may be processed in Singapore and in other countries where AlgoAlpha’s providers, infrastructure, contractors, or business partners operate.

Those countries may have privacy and data-protection laws different from those in your location.

Where required by applicable law, AlgoAlpha will use contractual, organisational, or technical measures intended to provide an appropriate or comparable standard of protection.

These measures may include data-processing terms, access restrictions, encryption, vendor assessment, and recognised cross-border transfer mechanisms.

Communication with Site Visitors and Users

AlgoAlpha may communicate with you through email, account notices, in-app messages, website notices, Discord or other community channels, or another contact method you provide.

Service, Security, and Legal Communications

We may send communications reasonably necessary to provide or administer the Services, including:

payment receipts;
subscription confirmations;
renewal and price-change notices;
access information;
authentication messages;
security alerts;
support responses;
service interruption notices;
feature or product changes;
account restrictions;
legal notices; and
changes to the Terms & Conditions or this Privacy Policy.

You may not be able to opt out of communications necessary to maintain an active account, subscription, or Service.

Marketing Communications

Customers and users may receive marketing, product-update, educational, or promotional communications where permitted by applicable law.

You may unsubscribe through the mechanism provided in a message or by contacting admin@algoalpha.io.

Opting out of marketing does not prevent AlgoAlpha from sending necessary service, security, transaction, account, or legal communications.

Use of Cookies and Tracking Tools

AlgoAlpha websites and applications may use:

cookies;
local storage;
pixels;
analytics tags;
tag-management systems;
software development kits;
server-side tracking;
session identifiers; and
similar technologies.

These technologies may be used for:

essential website and account functionality;
authentication and session management;
remembering preferences;
security and fraud prevention;
analytics;
performance measurement;
diagnosing technical issues;
understanding feature usage; and
measuring aggregate referral and campaign performance.

AlgoAlpha does not display advertisements on its own website. AlgoAlpha may advertise its Services on third-party platforms, including X, and may measure whether an advertisement led to a visit, lead, checkout, or purchase. Advertising-related Google consent categories are disabled by default.

The website currently uses the following measurement providers:

Google Analytics to measure page views, navigation, referral sources, browser and device information, approximate location derived from IP, and general site usage;
Google Tag Manager to load and manage site measurement tags;
Rybbit Analytics, hosted at analytics.algoalpha.io, to measure page views and aggregate website usage; and
PostHog, when enabled for a deployment, to record page views and product usage events. PostHog session recording is disabled, and person profiles are created only for identified users.

When enabled for a deployment, the X Ads pixel may receive page, referral, lead, checkout, and purchase events for advertising attribution and campaign measurement. Referral parameters, including twclid, may be stored in browser storage and carried into checkout attribution.

Optional tracking behavior adapts to the visitor's region using country information supplied by the hosting or delivery network. In regions configured for opt-in consent, and whenever a region cannot be reliably determined, optional analytics and advertising measurement remain off until the visitor allows them. In other regions, aggregate analytics may load by default while advertising measurement remains off until allowed. Retention depends on AlgoAlpha's configured settings and the applicable provider's terms. AlgoAlpha reviews these services and settings as the website changes.

AlgoAlpha does not intentionally send complete conversations, source code, files, or form-field contents to general analytics or tag-management providers. AlgoAlpha-controlled application monitoring may nevertheless record those contents and detailed interaction events as described above.

The Privacy choices control available on the website lets you allow or refuse analytics and advertising measurement separately and change or withdraw those choices later. Withdrawing a category stops future loading after the page refreshes. You may also block or delete cookies and site storage through your browser settings or use browser privacy controls or content blockers. Disabling certain technologies may prevent parts of the Services from functioning correctly. You may contact admin@algoalpha.io with privacy questions or requests concerning analytics data.

AlgoAlpha does not sell User Content or use raw User Content for targeted advertising.

Depending on your location and applicable law, you may have the right to:

request access to Personal Data held about you;
request information about how Personal Data has been used or disclosed;
request correction of inaccurate or incomplete Personal Data;
request deletion, account closure, or anonymisation;
withdraw consent for future processing;
object to or restrict certain processing;
request a portable copy of eligible information;
opt out of future model-training use;
opt out of marketing communications;
appeal certain privacy decisions; and
complain to a competent privacy or data-protection authority.

To make a request, email admin@algoalpha.io.

Please identify:

the email address associated with your account;
the relevant Service or integration;
the information concerned; and
the action you are requesting.

We may request additional information where reasonably necessary to verify your identity, prevent fraud, or confirm your authority to act for another person.

Privacy rights are not absolute. We may deny or limit a request where permitted or required by law, including where information is reasonably necessary for:

security;
fraud or abuse prevention;
transaction or payment records;
accounting or tax obligations;
dispute resolution;
legal claims;
regulatory compliance;
protecting another person’s rights;
enforcing our agreements; or
detecting misuse.

Withdrawing consent does not affect processing that occurred lawfully before withdrawal.

Depending on the processing involved, withdrawing consent or requesting closure may prevent us from continuing to provide part or all of the Services.

A request concerning model training is subject to the prospective opt-out terms described in the Product and Service Improvement section.

Automated Safety and Access Decisions

AlgoAlpha may use automated systems to classify, restrict, flag, review, or block content or activity that may involve:

illegal activity;
malicious code;
unauthorised access;
credential theft;
fraud;
abuse;
threats;
security attacks;
prohibited content;
attempts to bypass safety controls; or
violations of our agreements.

Automated signals may result in a request being blocked, an account being restricted, or an interaction being escalated for human review.

You may request review by contacting admin@algoalpha.io, although AlgoAlpha is not required to reverse a restriction where it reasonably considers the restriction necessary or lawful.

Children and Minors

AlgoAlpha does not impose a universal minimum age through this Privacy Policy and does not specifically direct the Services to children.

A person who has not reached the age at which they can legally consent to the relevant processing or enter into the Terms & Conditions should use the Services only with the permission and supervision of a parent or legal guardian where required by law.

Some third-party account, payment, exchange, or platform providers impose their own minimum-age requirements.

If AlgoAlpha learns that Personal Data was collected from a child in violation of applicable law, we may restrict the account and delete or anonymise the information, subject to legal, security, transaction, and record-keeping requirements.

A parent or guardian may contact admin@algoalpha.io.

Third-Party Services and Links

The Services may contain links to or integrations with websites and services operated by third parties, including account providers, payment processors, AI providers, TradingView, Discord, exchanges, analytics providers, and infrastructure providers.

This Privacy Policy describes AlgoAlpha’s practices. It does not govern or replace the privacy policies of independent third parties.

You should review the relevant third party’s privacy policy before:

providing information directly to it;
creating an account with it;
enabling an integration;
granting permissions; or
using its service.

AlgoAlpha is not responsible for an independent third party’s privacy practices.

Privacy Policy Updates

AlgoAlpha may update this Privacy Policy at any time to reflect changes in:

the Services;
data-collection practices;
Product Improvement activities;
AI systems;
service providers;
security practices;
business structure;
applicable laws; or
regulatory requirements.

Unless a later effective date is stated, an updated version becomes effective when posted.

AlgoAlpha is not required to provide routine advance notice of every change. Material changes may be communicated through email, a website notice, an account notice, an in-app notice, a community announcement, or another reasonable method.

Where applicable law requires advance notice, renewed acceptance, or fresh consent, AlgoAlpha will provide the legally required process.

Where legally permitted, continued use of the Services after an updated version becomes effective constitutes acknowledgement of the updated Privacy Policy.

If you do not agree with an updated Privacy Policy, you should discontinue use of the Services and may request account closure by emailing admin@algoalpha.io.

Contact Us

Questions, complaints, privacy requests, consent-withdrawal requests, account-closure requests, access or correction requests, model-training opt-out requests, and legal notices relating to privacy may be sent to:

Privacy and Data Protection Contact
AlgoAlpha
Email: admin@algoalpha.io

Please provide sufficient information for us to identify the relevant account, transaction, interaction, integration, or request.

AlgoAlpha may request additional information where reasonably necessary to verify your identity or authority to make a request.