Files, updates & seats
Where the platform keeps things, how updates arrive, and how the seat on your plan moves between machines.
Where things are kept
Everything the terminal writes lives in %LOCALAPPDATA%\Chartveil on the machine it runs on:
| Folder | Holds | Worth backing up? |
|---|---|---|
config |
Your settings, workspaces, drawings, indicator templates, accounts, the exit strategy, custom indicators and the journal | Yes — small, and the part that is yours |
cache |
Recorded tick history and depth | No — large, and rebuilt from the feed |
logs |
What the problem report reads from, and crash.log if there has ever been one |
No |
Uninstalling leaves the folder in place on purpose; delete it yourself for a clean slate.
Moving to a new PC
Install from the dashboard, sign in with the same licence, and copy the config folder across if you want your desk exactly as it was. A single layout can travel on its own as a shared workspace. Nothing about your account is tied to the old machine.
Updates
The terminal checks on every launch. When a newer stable build is out it tells you before it opens, downloads the installer itself and hands over to it — press Install and it installs and reopens. Your settings, workspaces and journal are kept. If the download will not start, take the installer from the dashboard instead. Either way it takes a minute, so do it before the session rather than at the open.
The terminal only runs a build we currently serve, so a fix that matters is never left behind on one machine. What changed in each release is on the changelog.
Builds before 0.9.13 download the new installer and then fail to launch it. If you are on one of those, take 0.9.13 or later from the dashboard once; from then on Install update works from inside the platform.
Stable and beta builds both install to the same place, so running either installer switches you to that build, and one licence covers both.
Seats
Install on as many of your own computers as you like. The plan limits how many copies run at the same time — two on annual, one on monthly.
There is nothing to move and no slot to free up. If a copy is already open elsewhere, the new one tells you which machine has it and offers to take the seat over in one click. Relaunching on the same machine simply takes its own seat back, so a crash, a reinstalled Windows or a new laptop needs no help from us. If the dialog names a machine you do not recognise, tell us straight away — it means your key is being used by someone else.
Offline
Every panel is built from a live feed, so without a connection there is nothing to draw. The licence is forgiving: it checks in with us when the terminal opens, and if our server cannot be reached the build keeps working for two weeks on the last successful check before it asks again.
Reconnecting
Whatever was connected when you closed the platform — the chart feed and your broker sessions — reconnects at launch, and the journal catches itself up on the fills it missed. If the feed drops mid-session the client reconnects and resumes tick paging automatically, backfilling what it missed.