Backups, snapshots and export

Deleting game history

A Before action snapshot is saved automatically before deletion. In Settings → Backups & data, From and Through use your local time and include both chosen days. The confirmation dialog shows how many games will be deleted; an empty range cannot be confirmed. Re-sync from the desktop app afterwards to upload your replays again. Step-by-step deletion guide.

Snapshots work with large game histories and download as compressed files. Your JSON export is a separate copy to keep, and cannot be uploaded as a restore point.

Types and retention

Older snapshots of each type are pruned. Download a copy you need to keep longer. This page restores snapshots still in your account, not files uploaded from your computer.

Take a snapshot

1. 1
   Open Settings → Backups & data.
2. 2
   Under Snapshots, press Take a snapshot. The row shows its type, age, compressed size and saved counts.
3. 3
   Add a useful label and press Save label. Download keeps a gzip NDJSON copy; Delete snapshot removes only that backup, leaving your current games unchanged.

A snapshot holds your games list, opponents, notes, custom builds, profile, ordinary settings and a historical overlay-token section. Current overlay credentials and their rotation/revocation state stay unchanged during restore, so an old snapshot cannot revive a leaked URL. Heavy game details and replay binaries are separate. Paired PCs, onboarding goals/checklist progress, notification choices, import history, coaching and community records stay outside restore. Old work queues are never revived.

Restore a snapshot

1. 1
   In Settings → Backups & data, find the snapshot and press Restore.
2. 2
   Wait for the verified preview. Check games kept, removed and added, plus custom builds and notes. Overlay-token credentials stay unchanged. If preview fails, Try again; Restore stays disabled. Confirm Restore only after checking these numbers. A fresh Before action snapshot is saved first.
3. 3
   Build orders, charts, replay-map data and original replay files for game IDs in both your current list and the snapshot are kept. Games absent from the snapshot and their files are removed. Restored games absent from your current data may need a desktop Re-sync to recover their files.

If backup storage is unavailable or an archive cannot be verified, restore does not change your current data. Existing uploaded replays are checked before restore. For derived-data problems, try Fixing wrong opponent counts.

If a restore stops part-way through, refresh its preview before trying again. The Before action snapshot remains a separate restore point. An upload batch already in progress when history is replaced may need to retry; use a fresh desktop Re-sync when you want to upload that history again.

Export your data

Open Settings → Export for a Full account archive in NDJSON (one record per line). It includes account records such as games, opponents, notes, custom builds, settings and overlay tokens; keep it private. Include game details adds build orders and charts and makes the file larger. Original replay binaries are separate: use a private replay pack or a game's download button.

The older Export my data JSON action remains a separate compatibility download without build orders or charts. Neither account export format can be uploaded as a restore point. Snapshots are the restorable copies described above; a redacted support bundle is for troubleshooting and is not an account archive. Exporting is optional before deleting your account; a cancelled or failed export does not confirm deletion.

Export build orders

Choose CSV for a spreadsheet or NDJSON for structured records. Each file covers up to 2,000 games. From and Through use your local time and include both chosen days; leaving both empty uses all games. Supply is blank when it was not recorded. There are three admitted requests per rolling hour; each actual page request counts, including downloads cancelled or failed after admission.

When more games remain, Download next page continues the captured order with a cursor that expires 24 hours after it was first issued; using it does not renew that deadline. A failed or cancelled next page keeps the same cursor for an explicit retry with unchanged format and dates. Each retry that reaches admission uses another request. Download build orders restarts at the first page. Changing account, format or dates clears the continuation; no page retries automatically.

Saving and cancelling

Save directly to a file when your browser offers a file picker. Other browsers support completed downloads up to 128 MiB; choose a smaller range or direct file saving for larger exports. Cancel export stops the current work; another export stays blocked while actual file and network cleanup finishes. Records are read in sequence, so changes during a download can affect the file: an export is not a transactionally frozen snapshot of the account.

When you delete something

• Delete game history and Delete my account remove the data from the live database and from replay storage straight away. Deleting your account also deletes your snapshots.
• Copies already inside the daily database backups aren't edited. They're deleted on their own when those backups reach the end of their retention period.
• There's no undo for deleting your account. Export your data first if you want to keep a copy. See the privacy policy for the details.