Accounts & Sync

An account is what lets you open the app on a second machine and find your work there. It is a small amount of server state, not a copy of your data warehouse.

Creating one

Sign in with a magic link (a single-use link valid for 15 minutes), with email and password, or with Google if the operator has enabled it. Passwords are stored only as salted PBKDF2-SHA256 hashes keyed with a server-side secret; the link and the OAuth exchange are single-use and bound to the browser that requested them. Verification and deletion emails are transactional only — there is no marketing list.

What syncs

Synced (light records):

  • test records, with their drawings, journal entries and tags;
  • app and chart settings, watchlists, replay alerts;
  • dataset metadata — the description of a dataset, not its contents;
  • strategies and portfolio definitions.

Never synced:

  • candles and tick data. They stay in your browser's storage. They are re-downloadable from the data source you used, which is why copying them through a server would cost you bandwidth and buy you nothing.

Sync is part of some plans, each with its own sync storage (see the pricing page), and every account has a limit on the number of synced items; candles never count. The app warns you near the limit; at the limit, new or larger items stay on your device and stop syncing until you delete old tests. Nothing on your device is ever deleted for you. When your plan ends, sync stops and the synced copy is kept on the server for 30 days, then deleted — buy a plan with sync before then and it carries on where it left off.

The first sync

Nothing leaves your device until you answer one question the first time you sign in on it: upload this device's data, keep it local only, or — if your account already has data — choose per kind of data (tests, settings, alerts, strategies, portfolio tests) whether to merge, take the cloud copy, or keep this device separate. You can change the answer later from the account menu ("What syncs from this device").

How conflicts resolve

Each record carries a server revision. A device only sends records it changed, and only on top of the revision it last saw. If the same test changed on two devices before they synced, neither copy overwrites the other: the item appears in the conflict picker (the account menu, or the "sync conflicts" pill), showing both versions, and you choose which to keep. The other version stays in the cloud's history for 30 days. Records a device has not changed are updated from the cloud automatically.

Sessions are limited to three devices — signing in on a fourth signs out the one used least recently — with idle and absolute expiry; you can revoke a single session from the account page.

Offline

The app is local-first: your datasets and tests open without waiting on a server, because they were never coming from one. When the link drops, the sync indicator reports offline — changes stay local; your edits are kept and sent on the next successful sync, and an incoming change never silently overwrites a newer local edit — it becomes a conflict you resolve.

That is not an offline-mode promise. Cached files make reloads faster; nobody here claims the app starts with no network at all, and server features (cloud data browsing, billing, signing in on a new device) need the API.

Deleting your account

Deletion is requested from the account menu and confirmed through an email link. Access ends immediately (every session and pending link is revoked); the account's server records are purged 30 days later, and payment records are anonymized at once and kept 5 years. The same email can register again. Deletion does not touch the data in your browser — that is yours to export or clear with Backup & Restore.