IB Lab. Journal for TradingView

Privacy Policy

Last updated: 2026-08-16

Summary

This extension stores only your own settings (the chart-snapshot capture toggle below) and runs no analytics of its own. Extraction happens entirely locally, in your browser. Clicking Add to Journal can send data off your device to up to two places: while chart-snapshot capture is enabled in the extension's settings (the default), a chart-snapshot render request to TradingView's own servers (see below); and, on every click regardless of that setting, the trade data — including that snapshot's link, when the capture succeeded — in the URL when an app.iblab.io tab is opened/updated. (Under the Chrome Web Store's definitions both of those count as collecting "website content" — the store listing's data disclosure declares it accordingly.)

What the extension accesses

• It runs only on tradingview.com pages.
• When you open the popup, it reads the Long/Short Position drawings you placed on the active chart (entry, stop, target, symbol, direction, the drawing's time range) and, to determine entry/exit timing and outcome, the chart's own already-loaded candles.
• While chart-snapshot capture is enabled in the extension's settings (the default), when you click Add to Journal on a position card, it first asks TradingView's own in-page charting API to render a server-side snapshot of the chart exactly as it currently looks (whatever is on screen at that moment — a drawing scrolled off-screen is not captured). That request runs in your existing TradingView browser session (under your TradingView account, if you are signed in) — the extension has no separate TradingView credentials of its own — and TradingView returns a link (https://www.tradingview.com/x/<code>/) that is publicly viewable by anyone who has it, TradingView-side, not something this extension or IB Lab controls. Every successful capture uploads a NEW public snapshot; a failed or timed-out capture is never retried, and the click simply proceeds with no snapshot link, silently. With chart-snapshot capture turned off, no snapshot request is sent at all, and the click proceeds with no snapshot link — the same blank-field outcome as a failed capture.
• It then opens (or reuses/focuses) a tab at https://app.iblab.io/journal?prefill=<payload> — the trade's data, base64url-encoded, in the URL, including that snapshot's link when the capture above succeeded. This happens only on that explicit Add to Journal click.
• Once that Journal tab actually opens, the extension's own job is done — from that point on the page is processed by the IB Lab web app like any other page view (including its own product analytics seeing the page URL, same as any page on app.iblab.io). The EXTENSION itself sends nothing further once that tab has opened; what the web app you just navigated to does with its own page load is that app's own privacy policy, not this one's.

What it does NOT do

• It sends data to up to two destinations, both only on the explicit Add to Journal click: TradingView's own servers (the chart-snapshot render on that click, while chart-snapshot capture is enabled in the extension's settings — the default; outside that click the extension only reads the chart in-page through TradingView's own API) and your journal at app.iblab.io (the trade data, sent on every click regardless of that setting). It does not send data to any other destination. Aside from that: Chrome itself may sync your extension settings (the capture toggle) across your Chrome profiles when Chrome Sync is on — that syncing is Chrome's own feature, governed by your own Chrome settings, the same as any other extension setting kept in Chrome's sync storage — the extension itself transmits nothing there.
• It does not use analytics, tracking, or cookies of its own.
• It does not store trade data, page content, or browsing history between popup sessions — the only thing it stores between sessions is your own extension settings (the chart-snapshot capture toggle), in Chrome's sync storage.
• It does not read or access pages other than TradingView and (only to find/reuse an open tab, see Permissions below) app.iblab.io/journal.

Permissions

• activeTab — to confirm the current tab is a TradingView page before requesting position data from it.
• storage — stores your own extension settings (the chart-snapshot capture toggle above) in Chrome's sync storage; no browsing data, page content, or trade data is ever stored here.
• Host access to tradingview.com — to read your position drawings and chart candles, and to trigger TradingView's own server-side chart-snapshot render, via TradingView's in-page charting API. Used solely for the features described above.
• Host access to app.iblab.io — Chrome grants host permissions per ORIGIN, not per path, so this grant technically covers the whole app.iblab.io origin, not just /journal. The extension USES it only to find and reuse an already-open IB Lab journal tab (chrome.tabs.query/chrome.tabs.update) when you click Add to Journal, instead of opening a duplicate tab every time. No page content is ever read from app.iblab.io.