Overview
DashFolio Automator is a Chrome extension that sets up Flex reporting on the Interactive Brokers Client Portal: it creates the Flex Queries DashFolio needs, ticks the report sections DashFolio uses (trades, dividends, cash movements, interest, fees) and saves the resulting Flex token and query IDs to your DashFolio account.
Done by hand, that configuration means dozens of checkboxes spread over several IBKR pages; the extension clicks through it for you. This page explains what data the extension touches, where it goes and where it never goes.
The short version: the only thing that ever leaves your browser is the Flex token and query IDs you came here to sync. It goes to your own DashFolio account and nowhere else. There are no analytics, no trackers and nothing runs in the background collecting anything.
What the extension stores on your device
The extension keeps the following in Chrome's local extension storage (chrome.storage.local, which is not synced to your Google account):
- The DashFolio profile names you choose and their API keys (format
dfk_...), which you generate yourself in DashFolio. - The Flex Web Service token and Flex Query IDs captured while the extension automates the IBKR portal for you, along with the token's validity dates.
- A short activity log of what the extension did (steps performed, errors), capped at 300 entries. Tokens and account numbers are masked in this log before being written.
This data never leaves your device on its own. Uninstalling the extension deletes all of it: Chrome removes an extension's local storage on uninstall.
What is sent to DashFolio and when
The extension only talks to the DashFolio server (dashfolio.ai), over HTTPS, authenticated with your own API key and only as a result of something you do:
- When you add or test a profile, it checks that your API key works.
- During the setup you start on the IBKR portal and when you click Sync to Dashboard, it sends your IBKR Flex Web Service token with its validity dates, plus the IDs and names of the Flex Queries that were created.
That is the whole payload. Its purpose is to let DashFolio fetch your IBKR reports on your behalf, which is the reason you installed this extension.
After the setup, the ongoing work happens between DashFolio and IBKR: DashFolio uses the token to fetch your reports directly from IBKR's Flex Web Service. The extension takes no part in that. It sits idle until you add another IBKR account or renew an expired token. Handling of your data on DashFolio's side is covered by the DashFolio privacy policy.
What the extension never sees
Your Interactive Brokers username and password. You log into the IBKR portal yourself; the extension automates clicks and form fields inside your already-authenticated session and only when you start a setup action from the panel. It never reads or captures what you type on the IBKR login page.
It also never reads your positions, balances or trade history. It ticks which sections IBKR will include in the reports and never opens the reports themselves; those are fetched later by DashFolio, on your account, using the token.
Diagnostic reports
If something goes wrong, the panel has a Support button that builds a diagnostic report (extension version, browser version, profile names, the masked activity log). Nothing is sent automatically: the report is shown to you first, copied to your clipboard, then you send it yourself through our contact page. If you don't press the button, no report exists.
What we don't do
We don't sell or share your data with anyone. We don't use analytics or advertising SDKs. The extension contains no remotely loaded code. It only runs on Interactive Brokers portal pages and is inert everywhere else on the web.
Deleting your data
- Locally: remove a profile in the panel, or uninstall the extension.
- On DashFolio: revoke the API key or delete the integration from your account; you can also reach us through our contact page and we'll remove it.
Changes and contact
If this policy changes in a way that matters, the "last updated" date above will change and the new version will be published at this address before it takes effect.
Questions: reach us through our contact page.