Privacy Policy

1. Introduction

TradeGuardX ("we", "our", or "us") respects your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our browser extension, web application, and related services. Please read this policy carefully.

2. Information We Collect

We collect the following types of information:

• Account information: Email address and authentication credentials when you create an account. Authentication is handled by Supabase; we do not store your password directly.
• Trading account metadata: Display name, prop firm or broker identifier, equity mode (live or funded), starting balance, current balance, account currency, and timezone for the trading accounts you add.
• Trade events: Open, modify, and close events captured by the browser extension on supported broker tabs — symbol, side, quantity, entry/exit prices, stop loss, take profit, P&L, and timestamps.
• Risk rule configuration: The risk rules you configure (daily loss limits, per-trade risk, hedging prevention, max trades per day, etc.) and their parameters.
• Pairing and session tokens: When you pair the browser extension with your account, we issue a session token that the extension stores in your browser's local storage and sends to our API as proof of authorization.
• Broker host: The hostname of the broker your trading account is paired to (e.g., my.exness.com). Used by the extension to determine which page to monitor and by our backend to scope rule evaluation.
• Subscription and payment information: Subscription tier and billing identifiers. Payment card details are processed by Dodo Payments and never stored on our servers.
• Technical data: Browser type, extension version, and device information necessary for the service to function.

3. Browser Extension — Data Practices

The TradeGuardX Chrome extension is scoped to a defined list of supported broker domains declared in its manifest. On other websites it does not load its monitoring scripts. On supported broker tabs:

• It reads the page DOM to detect Buy/Sell buttons, open positions, and order parameters needed to evaluate your configured risk rules.
• It does not read or transmit page content unrelated to trading (account numbers, personal messages on the broker site, etc.).
• It only activates on the broker hostname your trading account is currently paired to. On other supported brokers, the extension stays dormant until you pair an account on that broker.
• It stores configuration, the pairing session token, broker selectors, and a small ring-buffer of recent trades in chrome.storage.local. This data lives only in your browser unless you sync it to our backend by trading.
• When you trade, it sends trade events and account snapshots to our API so they appear in your journal and so server-side rules can be evaluated across devices.

4. What the Extension Does and Does Not Do

To set clear expectations about the scope of the browser extension:

• The extension does not execute trades, modify orders, or interact with broker APIs. It only observes trading activity and enforces user-defined rules within the browser interface.
• All executable code used by the extension is bundled within the extension package. No external scripts are dynamically loaded or executed at runtime.
• The extension only runs on explicitly supported broker domains listed in the extension manifest. It does not access all websites or any site outside that list.

5. Error Reporting

To diagnose crashes and bugs, the extension and web application send error reports to Sentry (sentry.io). Reports are stored in Sentry's EU region (ingest.de.sentry.io). Each report includes:

• A JavaScript stack trace of the error.
• The extension version and surface (popup or content script).
• The broker hostname the error occurred on (e.g., my.exness.com), so we can isolate broker-specific regressions.
• Click and navigation breadcrumbs leading up to the error.

We do not send console log breadcrumbs (which can include account IDs, P&L, or session tokens that brokers log to console), and we strip query strings from any URLs in the report. Error reporting only initializes on broker tabs the user has paired; the SDK is loaded but stays inactive on unpaired sites.

6. How We Use Your Information

We use collected information to:

• Provide, maintain, and improve our services
• Evaluate your risk rules against your trades and notify you of violations
• Generate AI insights, narratives, and behavior tags for trades you save to your journal (uses the Anthropic API)
• Process subscription payments and send related communications
• Send you updates, security alerts, and support messages
• Respond to your requests and comply with legal obligations
• Diagnose bugs and crashes via aggregated error reports

7. Data Storage and Security

We implement appropriate technical and organizational measures to protect your personal data. Account data is stored in our PostgreSQL database hosted on AWS. Extension-only data (session token, selector cache, ring-buffer of recent trades) is stored locally in your browser via chrome.storage.local. We do not sell your personal information to third parties.

8. Third-Party Services

TradeGuardX integrates with the following third parties. Their handling of your information is governed by their respective privacy policies:

• Supabase: Authentication and user identity.
• AWS: Application hosting and database storage.
• Dodo Payments: Subscription checkout and payment processing.
• Sentry (EU region): Crash and error reporting (see section 4).
• Anthropic: AI generation for trade narratives, behavior tags, and journal insights. Only the trade context you choose to analyze is sent.

9. Your Rights

Depending on your location, you may have the right to access, correct, delete, or port your personal data, and to object to or restrict certain processing. You can disconnect the browser extension from your account at any time from the extension popup, which revokes its session token. To delete your account or exercise other rights, contact us using the details below.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy on this page and updating the "Last updated" date. Your continued use of the service after changes constitutes acceptance.

11. Contact Us

For questions about this Privacy Policy or our data practices, contact us at: