← Trade Studio

Privacy Policy

Last updated: 23 July 2026 · Controller: Jasper Kilian Moore, Am Weberholz 11, 41469 Neuss, Germany, moorejasper060@gmail.com

Trade Studio V2 is local-first. Trading authority remains on your computer. The closed-beta cloud services provide identity, access, constrained AI, and optional Morning Desk features; they do not connect to your broker.

What stays on your device (we never receive it)

• Broker/exchange credentials, orders, positions, trading logs, complete bot state, and protective-exit state. These never enter the website, Account Worker, Intelligence Worker, Admin view, or cloud telemetry.
• Your complete local account configuration and validated BotSpec revision history. These remain in Trade Studio V2's per-user app folder (%APPDATA%\TradeStudioV2 on Windows or ~/Library/Application Support/TradeStudioV2 on macOS).

Closed-beta account and support data

• Google identity data: stable Google account ID, email, display name, and optional profile image, plus session and security-token hashes.
• Beta application, invitation, access/plan/quota state, app version and last-seen time, feedback you submit, and audited admin changes.
• Security/operations metadata such as request identifiers, rate-limit decisions, and bounded failure categories. These events do not contain prompts, BotSpecs, broker data, positions, orders, or local logs.

AI Copilot and Morning Desk

• When you use Copilot, your prompt, market constraints, and any declarative draft you choose to refine are sent through the Intelligence Worker to Anthropic. We store the monthly usage count, not the prompt or full BotSpec.
• Morning Desk stores your timezone, schedule, watchlist/bot symbols, email-delivery choice, generated briefing, and—only when you opt in—bounded bot-status and risk-state context. Positions, quantities, cost basis, orders, credentials, and complete bot state are rejected.
• Symbols are used to request market facts from Finnhub. The source packet is sent to Anthropic for bounded explanatory prose. If you enable email, the rendered briefing and your account email are sent to Resend.

Purposes and legal bases

We use account and feature data to process your beta application, provide the service, secure sessions, enforce limits, support users, and investigate faults. Depending on the activity, the legal basis is steps requested before or performance of the beta service (GDPR Art. 6(1)(b)), consent for optional personalization/delivery (Art. 6(1)(a)), legitimate interests in service security and abuse prevention (Art. 6(1)(f)), or a legal obligation (Art. 6(1)(c)). You may withdraw optional consent in the Morning Desk profile.

Processors

• Cloudflare — website/Worker delivery, D1/KV storage, rate limiting, and operational logs.
• Google — sign-in, when you choose Google authentication.
• Anthropic — constrained Copilot and optional briefing prose.
• Finnhub — source-bound market facts for selected symbols.
• Resend — account/service email and optional briefing delivery.

Billing and Stripe are disabled for the closed beta. Before any paid launch, this notice will be updated for the final processors and contracts. Providers may process data outside the EEA under an applicable adequacy decision, Standard Contractual Clauses, or another lawful transfer mechanism.

Retention

Rendered briefings and delivery rows are kept for 90 days; hosted-feature usage for the current and previous 12 months; privacy-safe failure events for 30 days; expired or revoked invite metadata for 90 days; rejected applications and closed feedback for 180 days; and admin audit events for two years. Active account/profile data remains while the account is active. Legally required billing/tax retention will apply only if billing is later enabled.

Your rights (GDPR)

You may request access, correction, deletion, restriction, portability, and object to processing, and may withdraw consent where processing is based on it. Contact moorejasper060@gmail.com. You may also complain to a supervisory authority (in Germany, your state Data Protection Authority). The desktop Account screen provides a safe downloadable copy of local bot records and available hosted account, application, feedback, profile, usage, briefing, delivery, and failure-event data. Contact us if you need help with an access or portability request.

Cookies, account deletion, and automated decisions

The website uses a secure, HttpOnly refresh cookie for signed-in account sessions. There is no advertising tracker or analytics cookie in the current V2 website. You can delete your cloud account from the desktop using the exact confirmation phrase; cloud identity, application/feedback, session, briefing, usage, and profile data are deleted or pseudonymized while local trading data stays untouched.

AI output does not approve access, place trades, or make a legally significant decision. Beta access and suspension are controlled by Jasper through audited admin actions.