Privacy Policy
This policy explains what information Trader Desk collects, why we use it, where it is stored, and the service providers that may process it.
1. About Trader Desk
Trader Desk by Chad Trades ("Trader Desk," "we," "us," or "our") is a Chrome extension and trading workflow platform that provides trade-discipline tools, journaling, performance tracking, market-planning resources, training, and related features.
By using Trader Desk, you acknowledge the data practices described in this Privacy Policy.
2. Information We Collect
The table below identifies the categories of user data Trader Desk may collect or process, why the data is used, where it is stored or processed, and the third parties that may receive or process it.
| Data | How / Why We Use It | Storage / Processing | Who May Receive It |
|---|---|---|---|
| Account information Email address, Trader Desk user ID, authentication/session information, account tier and subscription status. | Create and authenticate your account, keep you signed in, determine Free/Pro access, provide account support and operate the service. | Cloud backend and authentication systems; limited session/configuration information may also be stored locally in Chrome extension storage. | Supabase. For website Free signups, email/account signup information may also be sent to MailerLite for Trader Desk email onboarding and account-related marketing communications. |
| Trading journal and performance data Trading account name, trade date, P/L, risk, R:R, direction, setup, timeframe, grade, mistake tags, notes, process answers, process score, rule-following fields and related journal information. | Save your journal, sync it across Trader Desk, calculate statistics, streaks, process scores and performance analytics, and display your trading history. | Stored in Supabase; some journal information may be cached locally in Chrome extension storage for product functionality. | Supabase. This data is not sent by Trader Desk to advertising networks or data brokers. |
| Journal screenshots | Attach charts/screenshots to journal entries so you can review trades later. | Stored with Trader Desk journal records in Supabase and may be cached locally by the extension. | Supabase. |
| Trader Desk settings and preferences Selected trading account, timezone, trading hours, default risk, setup/mistake tags, personal trading rules, Trade Lock state and related configuration. | Remember your settings, operate Trade Lock and personalize the disclosed Trader Desk workflow. | Primarily Chrome extension local storage; cloud-backed settings may also be stored in Supabase. | Google Chrome / Chrome Extension APIs for local extension storage and Supabase when a setting is cloud-synced. |
| Tradovate page interaction data Only information needed to detect relevant trading activity and apply/display Trade Lock on supported Tradovate pages. | Detect when the Trader Desk trade workflow is active and provide the user-requested Trade Lock / Trading Complete experience. | Processed by the extension in the browser. Relevant Trader Desk state may be stored locally and journal information you submit may be synced to Supabase. | Tradovate remains the trading website you are using; Google Chrome / Chrome Extension APIs run the extension; submitted Trader Desk journal/state data may be processed by Supabase. Trader Desk does not collect general browsing history or monitor unrelated websites. |
| Subscription and billing information Subscription status, plan, transaction/customer identifiers and billing-related status. Payment-card details are entered into and handled by Paddle. | Start, manage, verify, cancel and restore Pro access and maintain billing records. | Processed by Paddle; subscription/access status may also be stored in Supabase. | Paddle and Supabase. Trader Desk does not directly store full payment-card numbers in the Chrome extension. |
| Website signup and onboarding information Email address and signup type when you create an account through the Trader Desk website. | Create your Trader Desk account, identify Free vs. direct Pro signup, and send onboarding/product emails where applicable. | Supabase and, for applicable email onboarding, MailerLite. Trader Desk web pages are hosted by Netlify. | Supabase, MailerLite, and Netlify as applicable to the request. |
| Technical and security information IP address, request timestamps, browser/device information, authentication activity and service logs that infrastructure providers may generate. | Host, secure, troubleshoot, prevent abuse and maintain Trader Desk. | Processed in service/infrastructure logs according to the provider involved. | Supabase, Netlify, Paddle, and other named providers only when you interact with their portion of the service. |
3. How We Use User Data
Trader Desk uses user data only to provide or improve its disclosed user-facing functionality. Specifically, we use it to authenticate accounts; save and sync journal entries; calculate trading statistics and progress; operate Trade Lock; remember settings; control Free/Pro access; provide Trader Desk content and resources; process subscriptions; provide onboarding and product communications; secure and troubleshoot the service; and respond to support, account, or privacy requests.
Trader Desk does not use user data for personalized advertising, ad retargeting, credit-worthiness decisions, unrelated commercial profiling, or sale to data brokers.
4. How and Where User Data Is Stored
On your device: Trader Desk uses Chrome extension local storage for settings, preferences, active-account information, Trade Lock state, session/configuration data and cached Trader Desk information needed for the extension to function.
In the cloud: Supabase provides Trader Desk authentication, database and backend infrastructure. Cloud-synced account records, trading-account records, journal entries, journal screenshots, subscription/access status and related Trader Desk records may be stored or processed there.
Billing: Paddle processes checkout and payment information. Trader Desk may store subscription status and provider/customer identifiers needed to determine Pro access, but the Chrome extension does not directly store full payment-card numbers.
Website/email infrastructure: Netlify hosts Trader Desk web pages. MailerLite may process email addresses and related signup/onboarding information for users entered into Trader Desk email onboarding or marketing communications.
Data transmitted between Trader Desk and supported backend services is sent over HTTPS. Local extension information remains in Chrome storage until it is cleared by you/Chrome or removed with the extension, subject to browser behavior.
5. Third Parties We Share Data With or Make Data Available To
Trader Desk does not sell user data. We disclose or make user data available only to the following service providers when needed for the stated Trader Desk functionality:
- Supabase — authentication, database, backend infrastructure and cloud storage. May process account data, journal/trading data, screenshots, settings, subscription/access status and technical logs.
- Google Chrome / Chrome Extension APIs — runs the extension and provides local extension storage and browser functionality needed by Trader Desk.
- Tradovate — the supported trading website on which Trader Desk's content script provides Trade Lock functionality. Trader Desk interacts with the Tradovate page in your browser; it does not use this permission to monitor unrelated websites.
- Paddle — checkout, payment processing, subscription billing and subscription management. Paddle receives payment and billing information you provide during checkout.
- Netlify — hosts Trader Desk websites/web interfaces and may process normal web request/server information such as IP address, browser information and request logs.
- MailerLite — email onboarding and marketing communications for applicable Trader Desk website signups; may receive email address and related signup information.
- YouTube / Vimeo — Trader Desk may open or embed training video content hosted by these services. If you load or visit that content, those providers receive the normal information associated with your request under their own privacy practices.
- Zoom — Trader Desk may link users to the Live Desk/live trading room. If you choose to open or join a Zoom session, Zoom receives information associated with that interaction under its own privacy practices.
- Discord — Trader Desk may link users to the Market Minutes community. If you choose to open or join Discord, Discord receives information associated with that interaction under its own privacy practices.
- TradingView — Trader Desk may display or link to chart resources hosted by TradingView. If you choose to load or visit those resources, TradingView receives information associated with that request under its own privacy practices.
We may also disclose information when required by law, to protect the security, rights or safety of Trader Desk or its users, or as part of a lawful merger, acquisition, financing, reorganization or sale of the service. We do not otherwise share Trader Desk user data with unrelated third parties.
6. Sale and Advertising Use of Data
Trader Desk does not sell personal information, trading journal information, browsing activity, or trading data to third parties.
Trader Desk does not transfer user data for personalized advertising, retargeting, credit-worthiness decisions, or unrelated commercial profiling.
7. Human Access to User Data
Trader Desk user data is not routinely reviewed by humans. Authorized access may occur when reasonably necessary to provide support requested by a user, investigate security or abuse, maintain the service, comply with legal obligations, or resolve account issues.
8. Data Retention and Deletion
Cloud-synced Trader Desk information may be retained while your account remains active and for as long as reasonably necessary to provide the service, keep legitimate business records, resolve disputes, comply with legal obligations, and protect the service.
Local extension information may remain on your device until it is cleared by you or your browser or removed with the extension.
You may request access to, correction of, or deletion of your Trader Desk account information and cloud-stored journal information by contacting info@chadbartlett1.com. We may need to verify your identity before completing a request.
9. Security
We use reasonable administrative and technical safeguards intended to protect information handled through Trader Desk. Data transmitted to supported backend services uses encrypted HTTPS connections. No method of electronic storage or transmission can be guaranteed to be completely secure.
10. Chrome Web Store Limited Use
Trader Desk's use and transfer of information received from Google Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
Information accessed through Chrome permissions is used only to provide or improve Trader Desk's disclosed user-facing functionality. Trader Desk does not use or transfer Chrome user data for personalized advertising, does not sell Chrome user data, and does not use Chrome user data for purposes unrelated to Trader Desk's disclosed functionality.
11. Children's Privacy
Trader Desk is not intended for children under 13, and we do not knowingly collect personal information from children under 13.
12. Changes to This Policy
We may update this Privacy Policy as Trader Desk features, service providers, or data practices change. The current version will be posted on this page with an updated effective date.
13. Contact
For privacy questions, data requests, or account-related privacy concerns, contact:
Trader Desk / Chad Trades
info@chadbartlett1.com