AstroEngine for TradingView: privacy

This extension sends no data anywhere except to the AstroEngine desktop app on the same computer, over 127.0.0.1 (this computer only). It has no server of its own, no analytics and no advertising, and it sends nothing to the AstroEngine team or to any other website. The one exception is your own demo broker: with a Copier switch on (see below), it sends the orders and account reads the app asks for to tv-demo.tradovateapi.com.

What it reads on tradingview.com and passes to your AstroEngine app

• The address of the TradingView tab.
• The numeric id and username of the TradingView account that is signed in (window.user.id and window.user.username only; never a token or session).
• What the app needs to draw skins and run your scripts: the chart's symbol, timeframe, studies and price bars, where the chart sits on the page, and the results of the scripts it runs.
• Broker connection details, from the browser's own timing of TradingView's requests to a Tradovate broker (tradovateapi.com): the broker's host name (which shows whether the account is a demo or a live one), how often TradingView asks for orders, and how many requests the broker refused (status 429) or failed (status 500 or above). This timing check does not read the contents of those requests or their answers, and never sends or changes anything at the broker. The app uses this to show the order-update rate.
• Your own broker replies, only while trade recording or a Copier browser switch is on: while you have linked this computer to your AstroEngine trader record and recording is on, the page reads (from a copy; it changes nothing and makes no request of its own) the replies your signed-in TradingView receives from the broker to its requests for accounts, orders, positions, executions and instruments, and passes them only to the AstroEngine app on this computer. Recording never places, changes or cancels an order, never reads your broker password or tokens, and passes nothing to the app while it is off. This extension sends nothing to any server; what the desktop app then does with them (it builds your closed-trade record, which it can upload to your AstroEngine trader account) is described by the app. With "Allow a browser tab to lead" or "Copy to accounts on a browser tab's login" on, the page reads those replies the same way for the copier, with recording off, and passes them only to the AstroEngine app on this computer.
• Orders on your demo accounts, only with a Copier switch on: three switches on the app's Copier page, "Allow a browser tab to lead", "Place my own orders from a browser tab" and "Copy to accounts on a browser tab's login", are off until you turn them on, and work on demo accounts only. With one on and Allow placing orders pressed in this extension's popup, the extension reads the sign-in (the Authorization header) of TradingView's own requests to tv-demo.tradovateapi.com, keeps it in memory for that tab, never passes it to the page or the app, and uses it to place, change and cancel orders, close positions and read those accounts as the app asks. The results go only to the AstroEngine app on this computer. No other broker address is open to it, so it never sees a live broker sign-in.
• Your TradingView sign-in, only when you press Share my TradingView sign-in: with the permission you grant at that press, and within 2 minutes of it, the extension reads the sessionid and sessionid_sign cookies of tradingview.com once and passes them only to the AstroEngine app on this computer, which uses them to add a firm login. The extension does not store them.
• Streamer mode: when you turn Streamer mode on in the app, the page hides or masks account values on screen (paint only). The extension passes the app only whether Streamer mode is on, its style and which items it could mask. Through a lock: from the extension release that adds this the app swaps the script for a smaller one that only masks (Streamer mode), so browser tabs stay masked while the app is locked. Known limit of older extension releases: the script is withdrawn while the app is locked, so a browser tab opened or reloaded during a lock is not masked until the app is unlocked and that tab is reloaded (the app's Streamer status says so for a tab that was open when the lock began).
• When you press Import study in the app: the study's saved Pine source, which the page fetches from pine-facade.tradingview.com. When you run a script that uses a published TradingView library the app has not stored yet: the library's Pine source. To find it, the page sends TradingView's compiler a two-line script that imports only that library, opens the library's public page on www.tradingview.com to read its id, and fetches its source from pine-facade.tradingview.com. These requests use your own TradingView session (your browser attaches your TradingView cookies to them; the extension does not read them), and the page hands the source to the desktop app. It happens only for a study you import or a library a script you run needs.
• Requests that scripts and modules you installed in the app make with tv.fetch (and, for modules, api.get): the page hands the request (address, method, headers, body) to your AstroEngine app through this extension, and the app makes the request, not the browser or this extension, with no TradingView cookies. The answer comes back to the page the same way.

The desktop app decides what to do with all of this and has its own privacy behaviour.

What it stores

In this browser only (chrome.storage.local): the pairing token that lets this browser talk to your AstroEngine app, this browser's id as the app knows it, the channel id the extension and the page script use to recognise each other, the hash of the page script that is registered, whether the app has asked for the order permission yet, and the one-use ids of order commands from the last few seconds, so that no command runs twice. Forgetting the browser in the AstroEngine app removes its token on the app's side; removing the extension removes everything stored here.

What it does not do

Out of the box it places no orders and changes no order or position; only the Copier switches above change that, and only on demo accounts. It never changes your balances or account details. It reads your own broker replies only while trade recording or one of those switches is on, as described above, and only for your own use. It never sees a live broker sign-in. It does not read your TradingView password or your broker password, it reads your TradingView sign-in only when you press Share my TradingView sign-in, and it reads no other website.