Create a full backup after an import or other major change, store a second copy away from the phone, protect access to the file, and test restoration. A restore test confirms that the backup can be used.
Set a backup schedule
- Reconcile important account balances.
- Create a full application backup in addition to a CSV export.
- Name it with an ISO date such as
squirio-backup-2026-09-03.zip. - Copy it to a destination separate from the phone.
- Retain several recent versions instead of overwriting the only copy.
CSV is useful for portability and inspection, while a full backup preserves application relationships needed for recovery. Keep both when the history is important.
Protect the backup file
An unprotected financial backup may expose balances, merchants, income patterns, and debts. Store it in a protected location, secure the account with strong authentication, and do not send it through ordinary messaging apps.
| Risk | Control |
|---|---|
| Phone lost | Keep a separate copy outside the device |
| Bad import or accidental edit | Retain multiple dated versions |
| Backup account compromised | Use strong authentication and restrict sharing |
| Corrupt or incompatible file | Test restoration after important updates |
Restore safely
Before restoring, copy the current data if possible. Check the backup date and source, follow the app's restore process, then inspect several accounts, budgets, goals, and recent transactions. Keep older copies until the restored data has been verified.
Review CSV import safety before bringing in statement data, and understand the responsibilities described in the offline security guide. The free tracker overview explains the full storage model.