Checked 2026-11-10
Is my trading journal data backed up?
Yes, twice a day. At 05:10 and 17:10 UTC every public table is written out row by row, each row encrypted with AES-256-GCM under the same key that protects broker tokens, and the copy is kept for 14 days with a restore script to put it back. The database host's point-in-time recovery is not switched on today, and the system watchdog flags any day the newest copy is older than 26 hours.
What is copied
Every table in the application schema — trades, broker connections, plans, rules, settings, evaluations, the audit log — except three operational tables that are re-derivable or pure logs: cron_heartbeats, cron_run_log, price_bars_cache. The copy is rows only: not database roles, extensions or the write-ahead log, which is why it is a data backup and not a full database snapshot.
How it is protected
Each row is encrypted before it is written to the backup file (AES-256-GCM, the same key that protects stored broker tokens), so the copy never holds a readable email address or token. It is stored outside the database host, in a private build system, and expires after the retention window. Restoring needs the server's key, which is why the copy is useless on its own.
How you would get it back
A restore script (scripts/restore-logical-backup.mjs) decrypts the copy and writes the rows back parents-first — users before connections before trades — into a target database that already has the schema, and it refuses to call a restore complete while any table is left. It has a dry-run mode that only counts, which is how the first copy was checked on the day the backup shipped.
What is checked every day
The system watchdog reads the backup state once a day: the newest copy must be under 26 hours old or it raises a critical finding and emails the operator. A day with only these copies and no host-side backup raises no finding — on the current plan that is the expected state, and the numbers stay readable on the admin backup status; a host-side backup that was switched on and then stops raises a warning.
What is not in place
Point-in-time recovery — the database host's own continuous backup — is a plan-level feature that is not switched on today. Until it is, these twice-daily copies are the backup that exists, which means a disaster could lose up to about twelve hours of entries. You can always take your own copy: the data export in Settings writes your trades to a file you keep, and the security page describes what else protects it.
Questions traders ask
Can I take my own backup?
Yes. The full data backup in Settings writes your trades, plans, daily preps, weekly reviews and prop evaluations, with your rules, settings and recent audit log, to a JSON file you keep (up to three downloads an hour); a trade-log PDF and a closed-trade CSV are there too.
Who can read the backup file?
Nobody without the server's encryption key: every row is AES-256-GCM ciphertext. The file is stored in a private system and expires after the retention window.
Is this the same as the audit log?
No. The hash-chained audit log records every change to a trade so the record is tamper-evident; the backup is a copy of the rows themselves, audit log included. One proves history, the other restores data.
Sources
Related
- Security and data handling
- Status page
- When does a broker connection expire
- Why doesn't my trading journal P&L match my broker statement?
- What is a prop firm consistency rule, and how is it calculated?
- Which brokers sync automatically with TradeFlow Quantum, and what does each sync actually import?
- How should a trading journal group multi-leg options trades?
- What happens when I hit a prop firm's daily loss limit: do I fail, or just stop for the day?
- What is a trailing drawdown, and what is the difference between end-of-day and intraday trailing?
- When does a broker connection expire, and how will I know?
- Which broker CSV formats does TradeFlow Quantum recognise before upload?
- Can I import my Tradervue export into TradeFlow Quantum?
- Which prop firms lock the trailing drawdown, and where?
- How many losing days can a prop firm evaluation take before it fails?
- What is the profit target as a share of the account at each prop firm?
- What is the minimum number of trading days to pass a prop firm evaluation?
- Can I share my prop evaluation progress without showing my P&L?
- What happens to my trading journal if I cancel TradeFlow Quantum?
- Can I connect my prop firm account (Topstep, Apex, FundedNext) to a trading journal?
- Can I import Robinhood trades into a trading journal?
- How does a prop firm evaluation fail? The rules that end one, and the ones that only delay a pass
- Is there a free trading journal?
- Does TradeFlow Quantum sync Alpaca automatically?
- Does TradeFlow Quantum sync Charles Schwab automatically?
- Does TradeFlow Quantum sync Tradier automatically?
- Does TradeFlow Quantum sync Tastytrade automatically?
- Does TradeFlow Quantum sync TradeStation automatically?
- Does TradeFlow Quantum sync Tradovate automatically?
- Does TradeFlow Quantum sync Questrade automatically?
- Does TradeFlow Quantum sync OANDA automatically?
- Does TradeFlow Quantum sync E*TRADE automatically?
- Does TradeFlow Quantum sync Coinbase automatically?
- Does TradeFlow Quantum sync Interactive Brokers automatically?
- Does TradeFlow Quantum sync Fidelity automatically?
- Does TradeFlow Quantum sync Robinhood automatically?
- Does TradeFlow Quantum sync Webull automatically?
- Does TradeFlow Quantum sync NinjaTrader automatically?
- Does TradeFlow Quantum sync Sierra Chart automatically?
- Does TradeFlow Quantum sync MetaTrader 5 automatically?
TradeFlow Quantum is a $15/month trading journal: 10 direct broker connections that work during the 7-day trial, nightly sync for paid accounts, a prop-evaluation copilot, and a P&L-free weekly discipline grade. Descriptive analytics only — nothing in the analytics edits your trades.
Start your 7-day free trial →