Your data lives on your device
Rackd is local-first. Training data starts on your device, and sync is optional.
Rackd is local-first. Every set and workout starts on the device where you log it. A second-device workflow depends on the account and sync surfaces available in the release you installed.
Make a backup if the app offers the export flow. A backup gives you a file you control, which is useful even when sync is available.
If Cloud Sync is shown in Settings, sign in with the same account on each device and follow the status shown there. If you do not see a sync control, it is not on for your account yet.
Let the first device finish its current sync before you add another one. On the second device, sign in through the app's current account flow and wait for the status to settle before making edits.
If both devices have local changes, keep the backup you made first. Use the conflict or merge controls shown by the release, rather than assuming which copy should win.
The safe order is backup, install, sign in if the current release supports it, then confirm the record before removing the old device. The local copy on the old phone remains useful until you know the new one is complete.
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.
Backup is a file you keep. Sync is an optional mirror between devices. They solve different problems.