Privacy Policy
Effective version 2.3. Trade Cycle Bot, [email protected], is responsible for the Trade Cycle Bot commercial portal.
Data we process
We may process name, surname, email, account identifiers, password hashes, verification status, IP addresses, user agent, security/audit logs, subscription and invoice identifiers, PayPal payer/subscription identifiers and, if enabled, Stripe customer/subscription identifiers, installation ID, server domain/IP, service identifiers, license status, software version and technical service-status information. Payment credentials, full card numbers and CVV are processed by PayPal and/or the enabled payment provider and are not stored by TCB.
Optional Performance Analytics
Performance Analytics is disabled by default and requires an explicit opt-in from the TCB installation. When enabled, the installation may send information about finalized closed trades to the Trade Cycle Bot Portal. A closed-trade record may include the installation identifier, trading pair, opening and closing timestamps, quantity, actual capital exposed, average buy and sell prices, sold value, gross and net realized profit, buy and sell fees, economically deductible buy fees, borrowing interest, other recorded transaction costs, number of buys/fills, DCA level, entry/exit classification, software/calculation version and whether the trade was created in test mode. The Portal may also receive closed-day reconciliation totals such as trade count, exposed capital and realized net profit by quote currency.
Performance Analytics does not require or transmit exchange API secrets, full account balances, open positions or raw exchange order identifiers. Trade Cycle Bot generates a pseudonymous trade identifier for delivery and duplicate protection. Pseudonymized installation/trade data can still constitute personal data when it can be linked back to a customer.
Performance calculations
For Performance Analytics, trade return is calculated against the actual capital exposed to that finalized trade rather than the customer's total exchange balance or configured account capital. Aggregated return is calculated from total realized net profit divided by total capital exposed for the selected records. The current day may be shown as provisional until the reporting day has closed and been reconciled. Different quote currencies are kept separate unless an explicit conversion methodology is introduced.
Purposes
We use data to create and secure accounts, authenticate users, process subscriptions, provision and administer service, prevent abuse, provide support, synchronize documentation, manage licenses, recover terminated installations during the retention period, comply with law and establish or defend legal claims. When Performance Analytics is enabled, we additionally use closed-trade data to provide bot-level, daily, monthly, annual and grouped performance reporting, verify delivery/reconciliation, diagnose calculation quality and improve performance-analytics functionality.
Consent and control
Performance Analytics reporting is optional. The customer may disable it from the TCB installation at any time, which stops future closed-trade transmissions. Disabling reporting does not by itself erase data previously received by the Portal. The customer may request deletion, and where the account interface provides the option may delete stored Performance Analytics data for an installation after re-authentication, subject to any mandatory legal retention that applies.
Third-party processors and transfers
Service operation may involve PayPal, optional Stripe services, cloud/VPS providers, DNS/CDN providers such as Cloudflare, transactional email providers and other hosting/monitoring vendors. Their locations and subprocessors may involve international transfers subject to applicable safeguards.
Trading credentials
Exchange API credentials may be stored on the customer's TCB server in encrypted form where the installed version supports it. We recommend exchange IP whitelisting and minimal API permissions. The commercial portal does not require exchange secret keys for account registration, subscription billing or Performance Analytics.
Retention
Account, billing and audit records are retained for the period reasonably required for service, security, accounting and legal obligations. Performance Analytics data is retained while reasonably required to provide the requested analytics and related integrity/reconciliation functions, and may be deleted on request where applicable. After service termination, a backup containing server data may be retained for up to six months for recovery and then permanently deleted. Billing records may be retained longer when law requires it.
Security
We use technical and organizational security measures including password protection, secure sessions, encrypted transport, installation-token authentication, access controls and idempotent delivery/receipt handling. No security measure eliminates all risk.
Rights
Subject to applicable law, users may request access, correction, deletion, restriction, objection or portability and may withdraw consent where consent is the legal basis. Requests can be sent to [email protected]. Mandatory accounting, fraud-prevention or legal-retention obligations may limit deletion.
Changes
Material changes are versioned and may require renewed acknowledgement.