Data & Storage

Two storage systems exist in this product and they hold different things. Knowing which is which prevents most data surprises.

Your browser (default, and primary)

Datasets, tests, drawings, journals, settings — all of it lives in your browser's IndexedDB. That is why the app opens without waiting on a server, and why a machine that is offline still replays.

Chunked writes. Large files are parsed and written in chunks, so a multi-year import does not need to hold the whole series in memory at once.
Compact candles. A candle costs roughly 48 bytes, so a year of M1 candles for one instrument is around 11 MB.
Binary tick chunks. Tick-derived datasets are stored deflated in per-day binary chunks with a month bitmap, which is what makes multi-year tick replay feasible in a browser at all.
Autosave. Every trade, drawing and replay step is debounced-autosaved, flushed every 10 seconds during playback and flushed again when the tab is hidden or closed. A refresh in the middle of a test resumes where you were.

Storage is not infinite. When the browser refuses more data, the app surfaces the quota error and asks you to clear space rather than failing quietly mid-import.

The cloud data bucket (BYOD)

Cloud data browsing lists your objects in the operator's bucket, per API key: one object per year per dataset, listed and read in bounded pages, with byte-range reads used for previews. Deleting or clearing a key in the provider console revokes access immediately; the app never stores more than the key material it needs to list and read.

Synced records — tests, settings, strategies — are a separate, small server-side store. Candles and ticks are never in it.

Backing up

Settings → Backup & Restore exports a single JSON file. Candles are optional in the export (a 1.5 M-candle dataset streams chunk-by-chunk rather than being assembled in memory), and restore runs in Merge or Replace mode.

Export a backup before clearing browser data, before moving machines, and before anything you cannot redo. A browser "clear browsing data" is, for this app, a delete button.

Moving between browsers

Two supported paths:

Export a backup, import it on the other machine, then re-import the datasets (or re-download them from your source).
Sign in with an account: light records arrive with sync; datasets still have to be imported or re-downloaded locally.

Erasing

Clear one dataset from the Data Library, or everything via browser storage controls.
Replace everything in one action with Replace mode on restore.
Account deletion removes server records on the documented schedule; it never had your candles.