Before changing phones
In Remend, open Settings → Backup & Restore and create an encrypted .remendbackup file. Save it to iCloud Drive, Google Drive, or another document provider you can open on the destination phone. Keep the password separately; Remend cannot recover it.
Set up the destination
Install Remend, establish the destination installation’s owner with Apple on iPhone or Google on Android, then restore the backup. Reconnect Apple Health or Health Connect because health permissions and health records are never included in the file.
Moving between iPhone and Android
Apple and Google can produce different Remend identities, especially when Sign in with Apple uses a private relay address. The encrypted backup still moves supported local Remend data, but it does not move credentials, health permissions, partner access, or store membership evidence.
If the destination resolves to a different Remend identity, apply the organisation code again. An individual subscription stays with the Apple App Store or Google Play account that sold it. Manage the original subscription in that store and avoid starting overlapping coverage on the destination platform.
What the current backup carries
Backup version 1 carries your profile and preferences. Future Remend product models will extend the typed, versioned backup. Photos, raw or derived connected-health data, credentials, membership evidence, partner links, and permissions remain excluded.
Uninstalling and deleting are different
Uninstalling removes Remend data stored inside that phone, but not your server identity or backup files. In-app account deletion removes the server identity and the local store after confirmation. Backup files remain wherever you saved them until you delete them there.