OttoTrader Privacy Policy

Controller and contact

Zlatech Soft SRL operates OttoTrader and is the controller for the personal data described here. The business address currently published by OttoTrader is Libertatii 18, Casin, Bacau, Romania. Contact: [email protected].

Account, billing and support records

• Email, display name, authentication/session metadata, plan, subscription, marketplace ownership, seller status and records of terms acceptance.
• Billing name, address, country, customer type, tax identifiers where supplied, Stripe customer/payment references, invoices, refunds and payout status. Stripe collects card credentials; OttoTrader does not request your full card number or security code.
• Support messages, withdrawal notices, complaints and privacy requests, their contact details and related investigation or resolution records. Do not include exchange secrets or identity documents unless a verified support process specifically requires them.

Desktop and connected features

• Account/device linkage, installation identifiers, entitlement checks, heartbeat and recovery state, exchange-context metadata, and security or diagnostic events may reach the backend. Installation and trial-abuse records can persist separately from account sessions.
• Remote Trading Center sends the trading snapshots and commands needed for the feature, which can include strategy names, positions, balances, P&L and order status. TradingView webhook integrations receive the configured signal payload and processing status.
• Optional desktop cloud backup uploads workspace and runtime state. Backups are encrypted by the server using a server-managed key; this is not end-to-end encryption. Exchange credential storage is handled separately on the device. Unattended recovery can keep additional runtime credentials in the operating-system key store.
• MCP Research routes user-authorized instructions, strategy definitions and research results between the selected desktop and your chosen AI client. It also stores connection grants, tool/status metadata, research context and grounding snapshots. Transport security does not mean all server records are end-to-end encrypted. Protected marketplace definitions are held server-side to operate licensed strategies.
• Your chosen exchange and AI provider receive data for the workflows you enable and apply their own terms and privacy practices. Exported AI Instructions are shared with an AI provider only when you submit them. The research relay is not intended to receive API secrets, passwords, wallet seeds or authority to place live orders.

Purposes and legal bases

• Contract: create and secure accounts, supply chosen subscriptions, licenses and connected features, deliver purchases, process support and withdrawal requests.
• Legitimate interests: prevent fraud and trial abuse, secure the platform, investigate incidents, moderate listings and defend claims. These interests are balanced against your rights; you can object where this basis applies.
• Legal obligation: required accounting, tax, consumer-rights and lawful disclosure records.
• Consent: optional public-page analytics. Refusing or withdrawing analytics permission does not prevent account use. Accepting contract terms or reading this policy is not consent to advertising.
• Required account and billing fields enable the requested service; without them we may be unable to open an account or process a purchase. Optional feature data is processed when you use that feature. Automated security and entitlement checks can restrict access; contact support to contest an incorrect result and request human review.

Recipients and service providers

• Supabase supports authentication and hosted database infrastructure; Render and Vercel provide API/web hosting, delivery and operational logs. Our configured email provider delivers account and service messages.
• Stripe handles checkout, recurring billing, payment records and seller onboarding/payouts. Payment or seller verification information submitted directly to Stripe is also subject to its own privacy policy. FGO may process invoice data when the fiscal-invoicing integration is enabled.
• Cloudflare Turnstile handles anti-abuse challenges when configured. With analytics permission, Vercel Web Analytics and Speed Insights measure public-page use/performance, and Google Analytics does so if a measurement ID is configured.
• Public seller profiles, listing materials and reviews are visible to other visitors. Buyers receive buyer-safe reports, not sellers’ private Full Reports or source logic. Staff and service providers access other records only for their operational role; lawful requests may require disclosure to authorities.

Browser storage and analytics choices

Essential browser storage supports sign-in, temporary MFA/authentication continuation and your consent preference. Optional measurement is off until you allow it, is excluded from private account/authentication pages, and can be disabled through Privacy choices in the footer. No marketing pixels are deployed.

Retention and deletion

• Account, ownership, billing and support records remain while needed to supply the service, resolve a request or dispute, prevent abuse or meet legal recordkeeping duties. Closing an account does not automatically erase invoices, seller obligations or fraud-prevention records. Request deletion or a record-specific retention explanation from support.
• Current backend cleanup defaults include terminal Remote Trading Center command history after 30 days, readiness checks after 7 days, authentication rate-limit buckets after 30 days, trial-risk events after 365 days, and processed Stripe webhook/operational event logs after 180 days. These are scheduled cleanup thresholds, not guarantees of deletion at an exact moment.
• Research cleanup bounds large relay results to 6 hours, incomplete grounding uploads to 24 hours, and MCP audit history to 90 days. Other active research context, completed grounding snapshots and protected strategy records follow their feature lifecycle; they are not all short-lived relay payloads.
• Terminal TradingView event payloads are compacted after 60 days, while identifiers and status may remain for deduplication; unresolved events are retained for reconciliation. These limits do not erase the underlying exchange records.
• Cloud backups, support and compliance cases, invoices and ownership records have different lifecycles. Provider backups and logs may take additional time to expire. Legal preservation needs may require longer retention; we do not promise instantaneous deletion from every system.

Your rights and complaints

Where applicable, you may request access, correction, erasure, restriction, portability or object to processing. Withdraw optional analytics consent at any time without affecting earlier lawful processing. Use account privacy requests or email [email protected]. We may ask for proportionate identity verification.

GDPR requests are normally answered within one month. A permitted extension of up to two further months will be explained within the first month. If we cannot fulfill part of a request, we will explain the legal reason and available complaint routes. You may complain to the Romanian supervisory authority (ANSPDCP) or another competent authority, including where you live or work.

International processing and updates

Romania is our operating jurisdiction. Infrastructure, payments, support and your chosen integrations may process data outside the EEA. Where applicable, transfers require an adequacy decision or appropriate safeguards such as approved contractual clauses. Contact us for the safeguards and recipient information relevant to your data; this policy does not promise EU-only storage.

We update this notice when practices change and will seek a new choice for materially changed optional tracking. The page date identifies this version.