FAQ

Short answers to the things people ask most. The app is under active development, so if something here and the repository disagree, the repository is the most current source.

Is my trading data private?

Yes. Everything you create is stored in a local SQLite database (data/journal.db) on your own machine. There's no hosted account, and nothing is uploaded unless you deliberately deploy or share it. Your broker exports, uploads, and API keys are gitignored so they don't get committed by accident.

Does it cost anything?

The app is free and open source under the MIT License — no subscription, no signup. Two optional integrations use your own keys: a free Massive key for chart candles, and — if you use the AI coach — your own language-model API key, which you pay your provider for directly.

Do I need to be a developer to use it?

No — but you'll use a terminal briefly to install it. If you can copy and paste a few commands, you can get it running; day to day it's a normal app in your browser. You'll need Node.js 20+. If you'd rather look first, start with the live demo.

Which brokers can I import from?

ThinkorSwim/Schwab account statement exports work best (fill-level detail). DAS-style and TraderVue-style trade-summary CSVs are also supported as medium-confidence imports. Other brokers may need a small adapter — see Importing your trades.

Does the AI coach see or send my trades anywhere?

Only when you ask it to, and only to a provider you chose. Nothing is sent automatically: if you haven't configured a model API key, no trade data ever leaves your machine. When you do configure a key (OpenAI today; more providers planned) and request a review, the trades, notes, and tags for that session are sent to that provider under your own key — never through our servers. Every draft the coach writes comes back for you to edit before it saves. Because the project is open source, you can read exactly what gets sent and when.

Where do the charts get their data?

Charts use TradingView's open-source Lightweight Charts for display, and candle data comes from Massive (a free plan is enough). Your broker import provides the entry/exit markers; Massive provides the market candles behind them. Skip the key and the app still runs — you just won't fetch new candles until you add one.

Can I lose my journal?

Your entries live in data/journal.db, which is separate from the app's code, so updating doesn't overwrite them. The best protection is a simple habit: copy the data/ folder somewhere safe now and then.

Can I run it on my own server?

You can — it's your code and your data. Just remember that deploying it moves your journal off your local machine, which is a deliberate trade-off against the local-first default. The hosted demo runs this same app with demo data and read-only settings.

How is this different from my broker's built-in journal?

Two things: it's journal-first (the story of your day leads, not a table of numbers), and it's yours (private, open source, and — as the roadmap fills in — shaped around your own rules and vocabulary rather than a fixed template).