Draft status and service availability
This document is a AlgoTrader service draft for legal review, not an activated agreement or confirmation of regulatory approval. The legal operator, applicable jurisdictions, provider agreements, processing arrangements and release-specific obligations require separate review. Browsing or restoring this text does not activate payments or trading.
1. Operators and scope
AlgoTrader is responsible for information it processes for its website, strategy publication, account functions, merchant billing and support. Collective2, Stripe and your broker have their own processing roles and applicable notices. The actual agreements and data flows determine those roles.
The legal operator, contacts, provider arrangements and release-specific privacy obligations require confirmation before this draft becomes effective. AlgoTrader branding does not replace another legal entity or transfer all privacy obligations to it.
2. Original service-provider privacy documents
Service-provider processing
Read the service provider’s original notices for its own service. Its descriptions of session replay, advertising tools, retention and privacy contacts apply to its processing, not automatically to the AlgoTrader website. Provider policy dates and legal entity names are not replaced by our brand or this document’s update date.
An AlgoTrader privacy preference does not submit an opt-out to the service provider, change a broker’s records or cancel a provider service. Use the relevant provider’s own rights and preference process where its processing is involved.
3. Information in AlgoTrader’s scope
| Category | Examples and purpose |
|---|---|
| Account identity and authentication | Email, verified account identifiers and sign-in/security records needed to identify an account and protect access. Never include authentication secrets in support requests. |
| Research and preferences | Saved strategy choices, watchlists and requested account preferences used to provide the website functions. |
| Commercial records | Applicable service, payment and agreement references and status needed for support, reconciliation and legal records. Hosted processors handle payment credentials rather than AlgoTrader receiving complete card numbers. |
| Technical and support information | Relevant request/device information, errors, security events and information you choose to submit. A diagnostic report is reviewed, copied or downloaded manually; it is not an automatic collection of your trading account. |
| Provider integration | Trading-profile and strategy identifiers, encrypted connection credentials, selected broker/account references, approvals, AutoTrade status and access records needed for the requested service. Broker passwords are not accepted by this portal. |
| Merchant billing and reconciliation | Stripe customer, checkout, subscription and invoice references, verified payment events, service periods, review records and the execution service credit/access confirmations. Full payment-card credentials are handled by Stripe checkout. |
4. Sources of information
Information can come from you, your use of the website, its authentication and security functions, and providers that return the references or statuses needed for the service you request. Public strategy model data is distinct from your brokerage account information.
Do not send another person’s information, private strategy source, API keys, complete statements or unrelated account balances to support without a necessary and lawful reason.
5. Purposes and applicable legal bases
We process relevant information to supply requested account functions, provide support, secure services, prevent abuse, keep appropriate records and meet applicable legal obligations. Where a law requires a legal basis, the applicable purpose and relationship determine it, including contractual necessity, legal duties, properly assessed legitimate interests or consent where required.
Optional marketing and future optional tracking require the applicable choice or consent; they are not made necessary by subscribing to the service. Selecting a strategy is not consent for every unrelated use of account information.
6. Recipients and provider boundaries
Relevant information may be supplied to the actual infrastructure, authentication, payment, support or AutoTrade providers needed for the requested functions, and where lawful for security, disputes or legal obligations. The released integration must identify its provider entities and sharing arrangements.
The service provider’s receipt and onward processing are governed by its applicable role and notices. AlgoTrader does not claim to appoint a DPO, use the service provider’s advertising partners or apply the service provider’s recording-retention period merely by linking its policy. No advertising sale or sharing is configured in the current AlgoTrader customer app.
7. Security and access
Access controls and appropriate technical and organizational safeguards are used for the information within our scope. No storage or transmission method is completely secure. Protect your mailbox, authentication factors and broker account.
Generate report does not automatically send diagnostics or grant broker access. Review the report and mask secrets and unrelated personal details before choosing what to send.
8. Retention and deletion
Keep information only for periods justified by the service, security, billing, complaint, legal or recordkeeping purpose. Different records may require different retention, including lawful preservation and limited suppression records. This document does not invent a fixed global retention period.
The effective service must identify relevant retention and backup-deletion arrangements. A request to delete AlgoTrader data does not immediately erase independent provider/broker records or legally required records. The service provider’s own retention descriptions remain in its policy.
9. International processing
AlgoTrader and its providers may process information in countries different from your own, including the United States. Where applicable law requires transfer safeguards or a representative, the effective service must establish the applicable arrangements and explain how to obtain relevant information.
This document does not claim a certification, transfer agreement, regulator approval, storage region or privacy representative that has not been confirmed. Ask the relevant operator about its processing and safeguards.
10. Privacy rights and requests
Depending on applicable law, rights may include access, correction, deletion, portability, restriction, objection, withdrawal of consent and a complaint to the relevant authority. Contact help@algotrader.ninja for AlgoTrader’s processing; proportionate identity checks and lawful exceptions may apply.
For the service provider’s or a broker’s own processing, use the contact and rights process in its notice. A privacy request, marketing opt-out, renewal cancellation and broker-position decision are separate actions. State each request explicitly and never send passwords or one-time codes.
Request receipt is not completion. The request must be reviewed for scope, identity, applicable deadlines and lawful retention, with an assigned owner and recorded outcome. the execution service, Stripe and broker requests may require their separate processes.
11. Strategy data and automated functions
Published rankings and model statistics are general research information, not a personalized suitability determination. Strategy selection and available sizing remain customer decisions. Automated provider execution requires the separate agreements and explicit permissions of the AutoTrade service.
A website account or privacy preference does not authorize automated trading. Do not treat model positions or an estimated capital figure as a decision about your own financial circumstances.
12. Changes, age and contact
The service is intended for adults. Material processing changes must be dated and receive notice or consent where required. An edited document alone does not authorize a new purpose. This is an unpublished the execution service draft; operator identity, applicable contacts and release-specific processing arrangements require confirmation. Use the published support contact for AlgoTrader processing and the provider’s own contacts for provider processing.