Creating Encrypted Backups & Migrating Girvi to a New Phone
Protect your shop data with AES-256-GCM encryption and learn how to safely restore your records during a phone upgrade or device change.
Step-by-Step Instructions
Navigate to Backup & Restore in Profile
Open the Profile tab from the bottom navigation and tap 'Backup & Restore'.
Understand the Two Encryption Modes
Choose between 'Device Key' (Android Keystore hardware-bound, for same-phone safety) and 'Password Key' (PBKDF2 100,000 iterations + AES-256-GCM with 'PBK2' header, for cross-device migration).
Set a Strong Backup Password for Migration
When preparing to switch phones, select 'Password Key' and enter a strong passphrase. This enables the backup file to be decrypted on any other Android device.
Generate ZIP Archive & Export Off-Device
Tap 'Create Backup'. The app packages your database entities and all sandboxed CameraX photos into an encrypted archive. Use Android Share Sheet to save to Google Drive, email, or a USB drive.
Configure Automated Daily Backups
In Settings, toggle 'Auto Daily Backup' and set your preferred time (e.g. 10:00 PM). WorkManager runs silent nightly backups automatically.
Expected Outcome
A complete, tamper-proof encrypted archive is safely preserved off-device, ensuring zero data loss if your phone is lost, damaged, or upgraded.
Important Points & Common Pitfalls
- Using 'Device Key' encryption when transferring records to a new phone (Device Keys cannot leave the physical Keystore chip).
- Forgetting the custom backup password; authenticated AES-256-GCM encryption mathematically cannot be bypassed without the key.