Data & backup policy
Last updated: 26 September 2026
This explains the product’s data boundaries and the backup questions to settle before operating a shop. It is not a promise of an automated backup or managed recovery service.
Authoritative records
Confirmed business records live on the application server and database. Local cached data and queued operations are provisional. Synchronization revalidates permissions, stock and financial balances; conflicts remain visible as Needs Review. Official exports require confirmed server data.
Before clearing a device
Do not clear browser data, reset a device or uninstall its browser while work is pending. Review sync status and confirm acceptance first. Cached records and exports are not substitutes for a complete restorable database and file backup. Device loss can lose unsynchronized work.
Agree a backup plan
Before launch, agree who backs up the database, product files, private issued-document archives and required configuration; where copies are stored; frequency and retention; encryption/access; monitoring; and who tests restoration. Keep copies separate from the primary hosting account where feasible. Never put credentials in public backups.
Recovery and incidents
No backup schedule, retention period, recovery time, recovery point or zero-data-loss guarantee is currently published as a standard service. These must be agreed for the deployment. Report suspected loss or unauthorized access promptly, preserve available evidence and avoid destructive cleanup until a recovery plan is agreed.
Exports and end of service
Agree data handover, supported export formats, hosting access, final backups and deletion responsibilities before service ends. Dataset exports may not include every application record or uploaded file. Keep any statutory business records for the period applicable to your shop with appropriate professional guidance.