Privacy Policy
1. Data We Collect and How We Use It
MyTradingGuard is designed to operate as a local risk-management layer. We collect only the minimum data necessary to provide the service:
- No Personal Information: We do not collect names, email addresses, or any form of Personally Identifiable Information (PII). The extension operates entirely without a user account.
- Rule Configuration: Your trading rules (time windows, loss limits, trade counts, etc.) are stored locally in
chrome.storage.localon your device. This data never leaves your browser. - Trading Session Data: Intra-day trade counts, realized P&L, and event logs are stored locally in
chrome.storage.localand are automatically cleared at the start of each trading session (18:00 ET boundary). This data is never transmitted externally. - Broker Authentication Tokens: MyTradingGuard never asks for, sees or stores your broker username or password: you log in to your broker inside TradingView as usual, and the extension only observes the session token TradingView itself sends. When you connect a supported broker account through TradingView (e.g. Tradovate), the Chrome extension reads the broker's authentication token from the headers of TradingView's requests to the broker API, and your account ID from their address or, for an order, from its body, via the browser's built-in
chrome.webRequestAPI. A request body is read only for requests that send data (POST, PUT, PATCH) to the broker API, never for a sign-in or token request (whose body could hold your user name or password), and only the account ID is kept: the body is never stored, logged or sent anywhere. These credentials are stored exclusively inchrome.storage.session— a RAM-only store that is automatically cleared when the browser closes and is never written to disk. They are used to make broker REST calls only when the extension needs to (re)initialize your live account state — at Service Worker startup if credentials are present, when fresh credentials are first captured after a TradingView login, when you switch brokers, or when reconnecting after a session interruption. After any such (re)initialization, all subsequent data (balance updates, trade history, positions) arrives passively by reading the responses to TradingView's own broker API calls — the extension makes no further network requests of its own. For other brokers the extension operates in a fully passive mode: it does not read any authentication token and relies entirely on observing TradingView's own broker responses. These credentials are never sent to MyTradingGuard servers and are never shared with any third party. They are automatically cleared when the browser closes, when you disconnect from the broker (after 5 minutes of inactivity), or when you uninstall the extension. - Position Data: To enforce the Max Order Size rule and to allow safe position closing at all times, the extension reads your current open position size (net contracts or lots) from the broker data your trading platform’s own page receives. This data is held in memory only and is never written to disk or transmitted externally.
- Economic Calendar Data (High Impact News rule): When you enable the “High Impact News” rule, the extension makes a single read-only GET request to ForexFactory’s public economic calendar CDN (
nfs.faireconomy.media) to fetch this week’s scheduled high-impact economic events (e.g. CPI, NFP, FOMC releases). This request is triggered only a few times per trading day — at Service Worker startup when the rule is active, when you first enable the rule, on the 18:00 ET trading-day boundary, and on transient-failure retries; with on-disk caching of the response this typically results in at most one network request per trading day. No API key, no authentication, and no user data, trading data, or device identifiers are transmitted — it is an anonymous, unauthenticated HTTP GET for publicly available schedule data. The response (event titles, dates, and impact levels) is stored locally inchrome.storage.localand used solely to determine whether to block orders during ±5‑minute windows around high-impact events. If the rule is disabled (which is the default), no request is ever made. - Anonymous Product-Usage Analytics: The extension sends anonymous product-usage events to Google Analytics 4 via the Measurement Protocol (e.g. "order blocked", "rule changed", "extension installed"). An event carries at most the rule involved and, when you change a rule, its new numeric setting (for example a maximum number of trades or a loss limit). No personal data, account identifiers, balances, P&L, orders or symbols are ever included in these events. A persistent anonymous UUID (
client_id) is stored inchrome.storage.localfor session continuity; it cannot be linked to your identity. The same anonymous events include error reports: when the extension's own code fails, it reports where (the extension file and line, never a web page address), the kind of error, a short error message with every number, address, identifier and quoted text removed, and the extension and Chrome versions. Each distinct error is sent at most once a day, and no more than 20 a day. Once a day the extension also sends that protection is on, and once when a supported broker is first connected, each with that broker’s name (as recognised from your trading platform’s own traffic). Once, it also sends which kind of trading page you first opened with protection on (for example TradingView), and, while you use the side panel, the setup wizard step you reached and the prop firm preset you applied (the firm, account and stage, from the extension’s own list), and, for the invitation to review the extension on the Chrome Web Store, each time it is shown and the answer you give, with what brought it (five days of use or a fifth blocked order) and which invitation it was. When you use “Share your Discipline”, it also sends that the card was opened and shared, with which of its six badges and how (a social network’s post window, copy, download or your system’s share sheet) — never the card’s numbers or text. If you open the side panel on a cTrader or DXtrade site that MyTradingGuard does not support yet, the panel says so and offers an “Ask for support” button: only if you press it is the host name of that site alone (for example “trade.example.com”, never a page address, path or content) sent, once, so the site can be supported in a later version. Nothing about the site is sent if you do not press it. The extension does not read the trading platform’s stored settings for statistics. If you tell us, under the setup wizard’s list of prop firms, that your prop firm is not listed, the name you type is sent as one more anonymous event, once per name: only a firm’s name is accepted (letters, a few digits and a little punctuation, at most 50 characters), so an e-mail address, a link or a number cannot be sent. You can opt out at any time by disabling the "Usage Data" toggle in Settings → Usage Data. When opted out, no analytics requests are made. - No External Transmission of Trading Data: All trading data is processed locally on your device. No trading data, credentials, rule configurations, or account balances are ever uploaded to our servers or shared with third parties. The only exception is what you choose to share yourself, described just below.
- Share your Discipline: The image of your discipline card and the short post that goes with it (for example how many impulse orders were blocked today, or how many trading days in a row nothing was blocked) are made on your device, in the Chrome extension and in the macOS app. They leave it only when you choose where to send them: copied to your clipboard, saved as a file, handed to your system’s share sheet, or opened in a new tab in the post window of the social network you pick (X, Facebook, Reddit or WhatsApp), with the text already filled in. You can change or delete that text, and nothing is published unless you publish it there yourself: MyTradingGuard never posts for you, never signs in to any social network and receives nothing from it. What the network does with a post you publish is governed by its own privacy policy.
- Limited Use: All data collected is used exclusively to provide the core functionality: evaluating your trading rules in real time and blocking orders that would violate them.
- Incognito Mode: The extension does not store credentials, trade events, or broker state from tabs opened in Chrome's Incognito mode. Order rule-checking may still function in incognito but no data is persisted.
2. Security & Encryption
We implement professional-grade security measures to protect your local session and financial integrity:
- Credential Isolation via webRequest: Broker authentication tokens are captured directly inside the Service Worker via the browser's built-in
chrome.webRequest.onSendHeadersAPI. They never enter the page's JavaScript context and are never passed throughwindow.postMessage, making them invisible to any script running on the TradingView page. - In-Memory Processing: Broker authentication tokens are stored exclusively in
chrome.storage.session— a RAM-only store managed by Chrome. They are never written tochrome.storage.local(disk) and are automatically cleared when the browser closes. - Content Security Policy: The extension declares a strict Content Security Policy (
script-src 'self') to prevent injection of external scripts into extension pages.
3. Browser Permissions
The Chrome extension requests only the permissions strictly necessary to function, and installs without any permission warning: every permission that shows one is optional and requested only when you turn on the feature that needs it.
- storage: To save your rule configuration and daily trading state locally.
- alarms: To check for the daily session boundary (18:00 ET reset), detect broker inactivity and install a waiting update while the market is closed; once a minute, to warn you while a position is open and a high-impact release or the end of your trading window is minutes away (from what the extension already holds, with no request); and, only while the High Impact News rule is on and the calendar download has just failed, to retry it (at most 3 times a day). No other network request is made by the alarms.
- notifications (optional): Requested when you click "Enable Protection". To alert you with a browser notification when an order is blocked, and to warn you when a position is still open 5 minutes before a high-impact release or 10 minutes before your trading window ends.
- sidePanel: To display the dashboard in Chrome's Side Panel while you trade.
- offscreen: A Chrome extension's background worker cannot play audio, so a hidden page of the extension plays a short alert sound when an order is blocked. The sound is generated locally; nothing is downloaded or sent. You can turn it off in Settings → Sound Alerts.
- webRequest (optional): Requested when you click "Enable Protection", in the same single prompt as tradovateapi.com. To read the supported broker's Bearer token from outgoing request headers (
Authorization) directly inside the Service Worker — for example, a Tradovate token. The token never enters the page's JavaScript context. The same read-only observation of the broker API notices an order that reached the broker without being checked (to warn you) and follows an account switch made inside TradingView, from the account ID in the request (see Broker Authentication Tokens above: never a sign-in request, only the ID is kept). Requests are never blocked, changed or redirected. Until you grant it, the extension does not observe any request; for unsupported brokers no token is captured. - Host access — tradovateapi.com (optional): Requested when you click "Enable Protection". Used to read the official broker REST API (realized P&L, trade history, positions) for a small number of (re)initialization calls per session — at Service Worker startup, after a fresh TradingView login, on broker switch, or when reconnecting after a session interruption. After any such call completes the extension operates passively, reading TradingView's own broker responses without issuing further requests. It is also the only address webRequest observes (see webRequest). For other brokers no outbound request to this host is made.
- Host access — nfs.faireconomy.media (optional): Requested only when you switch on the High Impact News rule; if you decline, the rule stays off and no request is ever made. Used only while the rule is enabled — a single anonymous read-only GET request fetches this week's economic calendar from ForexFactory's public CDN. No user data, no authentication, no cookies are transmitted.
- activeTab: When you open the side panel on a tab, the panel can read that tab's address — only to recognise TradingView or a supported site of Hyperprop, cTrader, DXtrade or Bybit and offer to protect it. On any other secure (https) page it runs once, in that tab, a recognition function packaged in the extension that reads only the addresses of the page’s own scripts, stylesheets and requests, to tell whether it is a cTrader or DXtrade site. Nothing else on the page is read and nothing is stored; only the host name of a cTrader or DXtrade site not supported yet is sent, and only when you ask for support for that site, as described under Anonymous Product-Usage Analytics.
- Host access — app.hyperprop.com (optional): Requested only when you choose Hyperprop as your trading platform (Settings → Platform, or the "Protect Hyperprop" button the panel offers when you open it on Hyperprop); choosing another platform gives the access back. MyTradingGuard monitors one platform at a time: this access lets the same order-checking scripts run on the Hyperprop web trading platform instead of TradingView. They read the responses the platform's own page already receives (positions, P&L, fills, and your account's firm, stage, starting balance of the day and drawdown limit) and never call the platform themselves; nothing is sent anywhere. Where your account fails is kept only in memory for the browser session (
chrome.storage.session), to fit a prop firm preset to your account. - Host access — tradingview.com &
scripting(optional): Requested only after you explicitly click "Enable Protection" — in the same single prompt as tradovateapi.com and notifications.scriptingplaces the extension’s own packaged scripts (no remote code) on the platform you monitor — TradingView, or the web trading platform you chose — so that each order is checked before it leaves the browser; an allowed order leaves unchanged. - Host access — cTrader Web sites (optional): app.ctrader.com, ct.spotware.com, ct.tradersway.com, ct.ftmo.com, app.the5ers.com, app.acg-markets.com, ct.goatfundedtrader.com, app.funderpro.com, ct.brightfunded.com, app.fundedtradermarkets.com and app.holaprime.com. Requested only when you choose cTrader as your trading platform (Settings → Platform); choosing another platform gives the access back. The same order-checking scripts run there and read the messages the platform’s own page receives on its trading connection (orders, positions, fills, account); they never send anything to cTrader themselves, and nothing is sent anywhere.
- Host access — DXtrade sites (optional): trader.blueberrymarkets.com, dx.tradeify247.co, dxtrade.alphacapitalgroup.uk, dxtrade.instantfunding.io, trade.brightfunded.com and demo.dx.trade, the DXtrade sites of brokers and prop firms. Requested only when you choose DXtrade in Settings → Platform (all of them) or click the panel’s button to protect the one you have open (that one); choosing another platform gives the access back. The scripts read the responses and messages the platform’s own page receives and never call its API; nothing is sent anywhere.
- Host access — Bybit (optional): www.bybit.com, www.bybit.eu, www.bybit.kz, www.bybit-tr.com and www.bybitglobal.com, Bybit’s own trading site and its regional ones. Requested only when you choose Bybit in Settings → Platform (all of them) or click the panel’s button to protect the one you have open (that one); choosing another platform gives the access back. The scripts read the order requests and the position updates the site’s own page receives and never call Bybit’s API; nothing is sent anywhere.
The extension does not request the tabs permission (which would show "Read your browsing history"). Access is limited to the specific domains listed above. Requires Chrome 120 or later.
4. User Control & Data Deletion
You have full and exclusive control over your data. Since all data is stored locally, you can remove it at any time by:
- Clearing the extension's storage via
chrome://extensions→ MyTradingGuard → Details → Clear data. - Uninstalling the extension, which permanently removes all locally stored data.
5. Chrome Web Store Compliance
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
- Data collected by the extension is not sold to third parties.
- Data is not used or transferred for purposes unrelated to the extension's core functionality (trading discipline enforcement).
- Data is not used or transferred to determine creditworthiness or for lending purposes.
- The single purpose of MyTradingGuard is to act as a local risk management tool that enforces user-defined trading rules on specific broker platforms.
6. macOS Desktop App
The macOS app follows the same principle: everything stays on your Mac.
- Rules and daily data: your rule configuration, intra-day trade counts, realized P&L, the event log and the dashboard state are stored in the
.mytradingguardfolder in your home directory, readable only by your macOS user. The app's technical log is kept in~/Library/Logs/MyTradingGuard. Nothing is uploaded. - Broker credentials: the broker's authentication token and your account ID are stored in your macOS login Keychain (encrypted by macOS), never in a plain file.
- Local proxy: the app runs a proxy that listens only on your own Mac (127.0.0.1) and opens TradingView Desktop through it. TradingView's own traffic (charts, market data, the website) passes through it untouched and is not decrypted. The rest of what TradingView Desktop exchanges is decrypted on your Mac so that the app can recognise your broker's trading API, whoever the broker is; it acts only on that API (orders, positions, executions and account state, to check your orders) and lets everything else through unchanged. Nothing it reads is stored outside your Mac or sent anywhere. To read that broker traffic locally, the app creates a certificate authority on your Mac whose private key never leaves it, and TradingView Desktop is started in a mode that accepts the local proxy's certificates. The proxy itself verifies each broker's real certificate before forwarding anything.
- Economic calendar: with the High Impact News rule enabled, the app downloads the public ForexFactory calendar (no user data is sent).
- Anonymous usage analytics: the same anonymous events as the Chrome extension, sent to Google Analytics 4. A random identifier is stored in
~/.mytradingguard/ga_client_id. These include the same anonymous error reports: when the app fails, it reports where (the file and line of its own code — never a full path, which would contain your user name), the kind of error, a short message with every number, address, identifier and quoted text removed, and the app and macOS versions. A crash or freeze of the app is reported the next time it starts, from the crash report macOS gives the app (MetricKit): the type of crash and the app's own code addresses only. Each distinct error is sent at most once a day, and no more than 20 a day. Once a day, while it is running, the app also sends that protection is on, with the name of the supported broker it is connected to, if any. Turn off Usage Data in Settings to stop them. - Deleting your data: quit MyTradingGuard, move it to the Trash, delete the
.mytradingguardfolder in your home directory and theLibrary/Logs/MyTradingGuardfolder, and remove thecom.mytradingguarditem from the Keychain Access app.
7. This Website
The pages of this website use Google Analytics to count visits anonymously.
The feedback form on the home page is optional. If you use it, the email address and message you type are delivered to us by email through the EmailJS service, and Google reCAPTCHA is used to protect the form against spam. We use what you send only to read and answer your message.
The short survey shown after uninstalling the Chrome extension sends, as an anonymous Google Analytics event, only the option you choose, the comment if you write one, the version number of the extension you removed and, if you were sharing anonymous usage data, one word saying how far you had got with it (for example “panel” if you had opened it, “orders” if orders had been checked).
8. Contact Us
For technical inquiries regarding this Privacy Policy or our security implementation, please contact us at:
Email: info@mytradingguard.com