Your data lives on your device
Rackd is local-first. Training data starts on your device, and sync is optional.
Backup and sync solve different problems. A backup is a file you keep. Sync is an optional mirror between devices when the current release supports it.
A backup is a one-way export. Use the export action shown in Rackd, save the file somewhere you control, and keep it as a snapshot of the training record at that point in time.
A backup does not need a live sync service. It is useful before a reinstall, device move, or data change. Restore it only through the import flow shown by the release you are using.
When Cloud Sync is available, it connects the local records on devices signed in to the same account. Turn it on only through the current app flow. It is optional and should not be treated as a prerequisite for local training.
Sync is a live mirror, not a point-in-time backup. If a record is changed or removed on one device, that change may travel to the other devices after sync. Keep an export when you need a fixed snapshot.
If you train on one device and want a safety copy, make a backup and keep the file somewhere you trust.
If your installed release exposes sync and you train across devices, follow its account and sync instructions. The release gate, account state, and current terms control what is available.
Rackd is local-first. Training data starts on your device, and sync is optional.
This article described an old per-device generation credit. It is retained as a dated correction, not as current usage guidance.
Rackd is local-first. If your release exposes optional sync, use the same account on each device and keep a backup as well.