Privacy Policy
Last updated: 10 November 2026
Blindspot is a trading journal and analytics service at blindspotjournal.com. This policy explains what personal data we collect, why, where it lives, and what your rights are. The short version: we collect what the service needs to work and nothing more — no advertising, no tracking, no analytics cookies, and we never sell your data.
1. Who is responsible for your data
The data controller is the operator of Blindspot, based in the United Kingdom:
BlindspotUnited Kingdom
privacy@blindspotjournal.com
The operator's name and postal address are available on request via the email above where genuinely needed (for example for formal legal correspondence).
2. What we collect
- Account data — your email address and a hashed version of your password. We never store your password in readable form.
- Google sign-in — if you sign up or sign in with Google, Google sends us your email address, your name and your Google account id; we keep the email address and the account id to recognise you next time, and nothing else from your Google account.
- Trading data you upload or enter — broker fill exports, the trades derived from them, profit and loss figures, and anything you add in the journal: notes, tags, screenshots, playbooks, and comments.
- The files you import — a copy of each broker export you upload on the Import page. Files you import are kept for 14 days so we can diagnose import problems, then deleted automatically. If you delete an import, its file and trades are deleted; we keep a record that the import happened (file name, size, row counts and time) to help with support.
- Security logs — when you sign in (or someone tries to), we record the event with the email used, IP address, and browser identifier, so we can detect abuse and you can be protected from unauthorised access.
- How you found us — when you create an account we record which of our pages you signed up from and, if another website or a campaign link brought you here, that site's address (without any search terms) and the campaign name. It helps us understand which guides and sites bring people to Blindspot.
- Broker connection credentials — only if you connect Tradovate for automatic sync: the API credentials you enter and the access tokens Tradovate issues. They are stored encrypted and used only to fetch your own fills, positions and account data from Tradovate on your behalf (and, if you switch on auto-close, to send the closing order).
- Feedback you send us — when you report a problem or send an idea or a question from the app: what you write, a screenshot if you attach one, whether we may contact you about it, and the details the form shows you before sending (the page you were on, the app version, your browser and operating system, your timezone and the broker type of the selected account). No trades or notes are attached. We use it to answer you and to improve Blindspot, and it is deleted with your account.
- Support chat — when you use the Support bubble in the app: the messages you write and the assistant's answers. To answer, the assistant can look up your accounts (name or account number, whether they sync and the last sync error), your recent imports (file name, row counts, import errors and the timezone they were read in) and the summary statistics your Dashboard shows for "All accounts", which include an account someone shared with you if you chose to count it there; it never sees your password, broker credentials, trades or notes. Support chat messages and what the assistant looked up are processed by Anthropic, our AI provider, to answer you, and kept for 90 days. If you press "Talk to a human", the conversation becomes a support request that our team reads and answers.
- Strategy Lab submissions — only if we gave you access to the Strategy Lab: the title, instrument and strategy idea you submit and the backtest results, which an AI model (Anthropic's Claude) turns into a backtest without seeing your trades or account data; our admins can read them, and they are deleted with your account.
- Technical server logs — like almost every website, our servers keep short-lived request logs containing IP addresses.
- Performance monitoring — to find errors and slow pages, the application records traces of the requests it handles: the address requested (including record ids, with tokens and passwords removed), timings, the shape of database queries (without the values), and the connecting IP address. They go to a monitoring server we run ourselves in the United Kingdom, not to a third-party analytics service.
We do not use analytics services, advertising networks, or tracking cookies. Your browser stores the tokens that keep you signed in, which are strictly necessary for the service to function, and a few display preferences (such as the dashboard period and calendar units) so the app opens the way you left it. None of it is used to track you. The app also installs a small service worker so it can be added to your home screen.
3. Why we process it (legal bases)
- To provide the service (performance of a contract) — storing your trades and journal entries and computing your analytics is the product.
- To keep the service secure (legitimate interests) — security and server logs, abuse prevention.
- To contact you about the service (performance of a contract / legitimate interests) — e.g. password resets or important service announcements, and a weekly summary of your own trading week, which you can turn off in Settings or with the unsubscribe link in each email. We do not send marketing email.
4. Sharing within the app
Blindspot lets you grant read-only access to your journal to another registered user — for example a mentor or trading partner — who can then view your trades and leave comments. Sharing is entirely under your control: nothing is visible to anyone else unless you explicitly share it, and you can revoke access at any time.
If you share a Strategy Lab result by link, anyone with the link can see that result, including your idea as you wrote it, until you stop sharing it.
5. Apps and tools you connect
Some features send data to, or receive data from, services you choose to use. Nothing here happens unless you set it up, and you can switch each one off at any time.
- AI assistants (ChatGPT, Claude, Cursor and other MCP clients) — if you connect an assistant (Settings → Integrations → AI assistant access), it can read the journal data it asks for: accounts, trades, notes, tags, statistics, journal entries and the price bars around your trades. If you grant write access, it can also tag trades, edit notes, attach playbooks and write journal entries when you ask it to. What the assistant receives is then processed by its provider (for example OpenAI or Anthropic) under that provider's own terms and privacy policy, not ours. The assistant never receives your Blindspot password or broker credentials. Revoke a token or disconnect an app in Settings and its next request is refused; resetting your password disconnects every app.
- Tradovate — see "Broker connection credentials" above. Tradovate is a separate company and its own privacy policy covers the data it holds about you.
- The browser extension — an optional extension for the Tradovate web trader (and, if you turn it on, TradingView connected to Tradovate) that sends what that tab shows to your Blindspot account. It has its own section below.
- Phone and desktop alerts — if you turn on position alerts, the alert text (the position's direction, size, instrument and price, how long it has been losing, the size of the move and, for auto-close, the result and open profit or loss) is pushed through ntfy.sh, a public notification service, to the topic name you choose. Anyone who knows the topic can read those alerts, so treat it like a password.
To compute price excursions (MAE/MFE) we also download public market price bars, for example from Yahoo Finance. Those requests contain only a contract symbol and a time window, never anything about you.
6. The browser extension
Blindspot: Tradovate sync is an optional browser extension for Chrome, Edge, Brave and Firefox. You install it yourself, and it does nothing until you paste in a token you generate in Blindspot (Settings → Integrations → Browser extension). It runs only on the Tradovate web trader (trader.tradovate.com) and, if you turn its TradingView switch on, on TradingView (www.tradingview.com), and talks only to blindspotjournal.com.
- What it reads — the data the open Tradovate web trader tab itself receives over its connections: live market prices, your open positions, working orders, cash balance and account names, and your fills (the fill id, account, contract, side, quantity, price, time and fees). When it connects it asks the tab's own connection, twice and read-only, for the fills of the current trading session and, for a fill whose contract the tab has not named, the contract's details (its name), also read-only. It reads nothing else on the page, no other tab or website, no cookies, and never your Tradovate password. It never places, changes or cancels an order.
- What it sends, and where — the latest price per contract (at most once a second), your positions and orders, and your fills, to your own Blindspot account only, over HTTPS to blindspotjournal.com, authorised with your extension token. Two of the three have a switch in the extension's options (positions and orders; fills); prices are what the extension is for. Nothing goes to anyone else: no analytics, no error reporting service, no advertising.
- TradingView — off until you turn on "TradingView (Apex/Tradovate broker)" in the extension's options; your browser then asks you to allow the extension on www.tradingview.com. When on, and while TradingView's chart page is connected to your Tradovate account, the extension reads the replies that page itself gets from Tradovate's TradingView service (tv-demo.tradovateapi.com or tv-live.tradovateapi.com): your accounts, balance, open positions, working orders, prices and fills. Every other request of the page passes unread, and nothing else on TradingView is read. To catch each fill, when an order of yours has just filled the extension asks that same Tradovate service for that instrument's fills, the same read-only request TradingView's page makes, using the login the page already holds for it, at most once a second. That login stays inside the TradingView page: it is never stored, never shown and never sent to Blindspot or anywhere else. What the extension reads there goes to your Blindspot account exactly like the Tradovate tab's, under the same switches. Turning the switch off gives the permission back.
- History import — off until you turn it on. When on, and only when you click "Import my history" in the extension's options, the extension asks Tradovate's reporting service for your own Fills report for the dates you choose, the same report the web trader's Reports page offers, and sends that file to Blindspot, where it is imported exactly like a Fills CSV you upload yourself. To make that request the extension uses the session token the web trader logged its own connection in with, inside the Tradovate page only: that token is never stored, never shown and never sent to Blindspot or anywhere else, and while the switch is off it is not read at all.
- What it stores on your device — in the browser's extension storage: your extension token, the Blindspot URL and the switches; with TradingView on, the time each open TradingView position was opened (account, instrument, side) and when one last closed, never reused after 10 minutes; and, while the browser runs, the status its options page shows (last send time, counters, the last error, the state of a history import). Removing the extension deletes all of it.
- What Blindspot keeps — the latest price per contract (overwritten as new prices arrive, not kept as history), the latest positions and orders per account, and your fills as trades in your journal, under the same rules as every other trade (section 8). A Fills report sent by the history import is kept 14 days like any imported file. The server's short-lived request logs note each push and the extension's version, for support.
- How to stop it — revoke the token in Blindspot (the extension gets "token wrong or switched off" and sends nothing more), turn a switch off in the extension's options, or remove the extension from the browser. Changing your Blindspot password switches the token off too. Revoking or removing does not delete the trades already in your journal; delete those in the app if you want them gone.
The extension's source is short plain JavaScript without dependencies and is published with it; the Chrome Web Store listing's data disclosure describes the same facts in the store's categories. Tradovate is a separate company and its own privacy policy covers the data it holds about you.
7. Where your data lives
The application and its database run on a server in the United Kingdom. Traffic passes through a front proxy in Germany which terminates TLS and forwards requests; it does not store your data. We use a small number of infrastructure providers (processors):
| Provider | Role | Location |
|---|---|---|
| Pulsant Ltd | Application and database hosting | United Kingdom |
| IONOS SE | Network front proxy (TLS termination) | Germany |
| Interserver, Inc. | Off-site backup storage | United States |
| Anthropic, PBC | AI assistant answering support chat messages | United States |
| Amazon Web Services (SES) | Sending transactional email (e.g. password resets) | United States / EU |
Transfers to Germany are covered by UK adequacy regulations for the EU. Amazon Web Services participates in the EU–US Data Privacy Framework and its UK Extension. Backup copies stored off-site are encrypted and automatically deleted after 30 days.
8. How long we keep it
- Your account and trading data — for as long as you have an account.
- Imported files — 14 days from the upload, then deleted automatically (also when you delete that import, or your account).
- After deletion — deleting your account (Settings → Account → Danger Zone) immediately and permanently removes your account, trades, journal entries, screenshots, comments, the feedback you sent, and the security log entries tied to you from the live systems. Residual copies in backups expire automatically within 30 days.
- Support chat conversations — 90 days, then deleted automatically (also when you delete your account).
- Server request logs and performance traces — kept briefly for operational and security purposes, then rotated out.
9. Your rights
Under UK data protection law you have the right to access, correct, export, delete, and restrict or object to the processing of your personal data. Blindspot gives you the two big ones self-serve, with no need to ask us:
Export (Settings → Accounts & Data → Export Data) downloads your complete data — trades, notes, tags, screenshots, comments and journal entries — in JSON. Deletion (Settings → Account → Danger Zone) permanently erases your account and everything in it.
For anything else, email privacy@blindspotjournal.com and we will respond within one month. You also have the right to complain to the UK Information Commissioner's Office at ico.org.uk.
10. Children
Blindspot is a tool for futures traders and is not intended for anyone under 18.
11. Changes to this policy
If we change this policy we will post the new version here and update the date at the top. If a change materially affects how your data is handled, we will email you before it takes effect.
Questions? See also our Terms of Service, or write to privacy@blindspotjournal.com.