Privacy Policy

1. Scope & Applicability

This Privacy Policy explains how TradeConsole ("TradeConsole," "we," "our," or "us") collects, uses, encrypts, stores, and protects information when you visit or use our web application, APIs, and related services (collectively, the "Service"), including at https://staging.tradeconsole.app/privacy. By accessing or using the Service, you acknowledge this Privacy Policy and agree to our Terms of Service (https://staging.tradeconsole.app/tos).

2. Information We Collect

2.1 Google Sign-In Identity Data

We authenticate users exclusively via Google Identity Services / OAuth 2.0 (OpenID Connect). When you sign in with Google, we receive your basic Google profile attributes:

• Your verified Google email address (used as your unique workspace identifier);
• Your display name and profile avatar URL (used solely to personalize your workspace header); and
• Your Google account subject identifier (sub) and email verification status.

2.2 User-Provided Brokerage Connection Credentials & Tokens

If you choose to link external brokerage accounts (such as Charles Schwab, Alpaca Markets Live or Paper accounts, Robinhood, or Interactive Brokers), you provide API keys, API secrets, or OAuth authorization tokens necessary to communicate directly with those brokerages on your behalf. TradeConsole never has access to your Google account password, and brokerage connections remain completely optional and revocable at any time.

2.3 Portfolio State, Preferences & User-Configured Workflows

To provide unified portfolio views and execute user-configured workflows, TradeConsole processes and stores within your isolated user namespace:

• Custom account nicknames/aliases, UI theme preferences, cash sweep reserve tickers, and user-defined risk guardrail limits;
• User-created Recurring Trade schedules and Smart Accumulation / Trimming campaign configurations and order-tracking ledgers;
• A rolling 30-day transaction summary ledger used solely to surface potential wash-sale proximity warnings across your linked accounts; and
• Email notification preferences and a history of trade/system alerts sent to your registered address.

2.4 Security Telemetry & Optional Diagnostic Logs

• Security & Rate-Limit Telemetry: Request timestamps, HTTP status codes, IP addresses, and sliding-window API rate-limit counters used strictly to protect the Service against abuse, unauthorized access, and denial-of-service traffic.
• User-Initiated Feedback & Error Reports: Only when you explicitly submit a bug report or feature request—and choose to attach logs—we collect the diagnostic log window you select. Sensitive fields (API keys, secrets, OAuth bearer tokens, passwords, and session cookies) are automatically redacted prior to storage.

3. Google API Services User Data Policy (Limited Use Disclosure)

• We request only the minimum OpenID Connect identity scopes (openid, email, profile) needed to sign you in and isolate your workspace.
• We never sell, license, or share Google user data with third-party advertisers, data brokers, or marketing networks.
• We never use Google user data or your brokerage portfolio data for serving advertisements or training generalized artificial intelligence / machine learning models.
• Human access to user data is prohibited except where explicitly authorized by you to troubleshoot a user-submitted support issue, or as strictly required for security abuse investigation or valid legal obligation.

4. How We Use Your Information

We use collected information strictly to:

• Authenticate your session, enforce per-user tenant isolation, and apply your membership tier quotas and safety guardrails;
• Retrieve real-time balances, positions, quotes, and order statuses from the brokerages you explicitly connect;
• Transmit self-directed orders, cash sweeps, security swaps, recurring orders, and campaign slices that you explicitly configure and authorize;
• Send optional transactional email notifications (such as welcome emails, fill confirmations, rejections, or token expiration alerts) that you can toggle in Settings; and
• Maintain platform security, prevent misuse, audit unauthorized access attempts, and comply with applicable law.

5. Cryptographic Security & Multi-Tenant Isolation

• Per-User Tenant Isolation: Every authenticated user's settings, tokens, campaigns, and ledgers are segregated into an isolated user shard/collection namespace keyed to their verified identity. One user can never view or access another user's credentials or portfolio data.
• Application-Layer Envelope Encryption: Sensitive brokerage credential and OAuth token vaults (user_config.json, schwab_token.json, robinhood_token.json) are encrypted at the application layer using authenticated symmetric encryption (Fernet AES-128-CBC with HMAC-SHA256) backed by keys stored in Google Cloud Secret Manager, in addition to Cloud Firestore encryption at rest.
• Transport & Browser Hardening: All network communication is encrypted via HTTPS/TLS, protected by strict Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), Cross-Site Request Forgery (CSRF) same-origin validation, and signed HttpOnly session cookies.

6. Cookies & Tracking Technologies

TradeConsole uses strictly necessary first-party security cookies only:

• ta_session: An HMAC-SHA256 signed, HttpOnly, SameSite=Lax cookie (`Secure` over HTTPS) maintaining your authenticated session; and
• ta_oauth_state: A short-lived cryptographic nonce cookie preventing Cross-Site Request Forgery during Google OAuth redirects.

We do not use third-party advertising cookies, cross-site tracking pixels, or behavioral profiling scripts.

7. Information Sharing & Third-Party Processors

We do not sell or rent your personal or financial data. Information is transmitted outside TradeConsole only in the following limited circumstances:

• Your Connected Brokerages: Order instructions and account queries are sent directly to the brokerage APIs (e.g., Charles Schwab, Alpaca Markets, Robinhood, Interactive Brokers) that you connect and authorize. Each brokerage processes your account under its own privacy policy and customer agreement.
• Cloud Infrastructure & Authentication Providers: We host the Service on Google Cloud Platform (Cloud Run, Cloud Firestore, Secret Manager, and Cloud Logging) and use Google Identity Services for sign-in, plus configured transactional email transport for user-enabled trade notifications.
• Legal & Safety Compliance: When required by enforceable subpoena, court order, or applicable law, or when strictly necessary to protect the security, integrity, or rights of TradeConsole, its users, or the public.

8. Data Retention, Disconnection & Deletion Rights

• One-Click Brokerage Disconnection: You may disconnect any linked brokerage at any time from Settings → Brokerage Connections. Disconnecting immediately deletes the stored API keys or OAuth tokens for that brokerage from your active vault.
• Account & Vault Deletion: We retain your workspace configuration while your account remains active. You may request complete deletion of your TradeConsole account and all associated cloud vault records at any time through the in-app Send Feedback / Support channel or by contacting the workspace administrator.
• Regional Privacy Rights (CCPA/CPRA, GDPR & Equivalent Laws): Depending on your jurisdiction, you have the right to access, correct, export, restrict processing of, or delete your personal information, and to confirm that we do not "sell" or "share" personal information for cross-context behavioral advertising.

9. Children's Privacy

TradeConsole is intended exclusively for adults aged 18 and older who are legally permitted to hold brokerage accounts. We do not knowingly collect personal information from individuals under 18 years of age.

10. Changes to This Privacy Policy & Contact

We may update this Privacy Policy periodically to reflect architectural, security, or regulatory updates. Material updates will be reflected by an updated "Effective Date" at the top of this page. For privacy inquiries, data deletion requests, or security reports, signed-in users may use the in-app Feedback & Support portal or contact the platform administrator associated with this deployment domain.