Backups
The database is copied once a day, in full and as one consistent snapshot. The file is encrypted before it leaves the server. We describe exactly what the backup covers, what it does not cover, how long we keep it and what to do when data has disappeared.
What goes into the backup and how often
Once a day, at night, we save the entire contents of the database: customers, measurements with their items, quotes, contracts, annexes, complaints, service requests, warranty cards, company settings, user accounts and the event log. The backup covers the data of all showrooms within the account.
The backup is created as one consistent snapshot of the database from the same moment, not table by table. The difference is practical: when copying one table after another, a contract saved at the start could end up in the file without items added a minute later. Such a backup looks correct and only breaks when you restore it. There is no such problem here — everything comes from one moment.
How the backup is protected
The file is encrypted before it leaves the server — with the AES-256 algorithm and a key derived from a password. Without that password the contents are unreadable, including to the provider of the storage where the backup is kept.
We keep the encryption password outside the system the backup belongs to. The application has no access to it and cannot decrypt its own backups. This is deliberate: taking over the application then gives no access to historical data.
The backup directory is outside the area served by the web server — the files are not available at any web address, even to someone who knows their names.
How long we keep backups
- Daily backups
- The last fourteen days, day by day. The oldest disappears when a new one appears.
- Monthly backups
- The last six months — the backup from the first day of each month, kept independently of the daily rotation.
In practice this means the last two weeks can be restored to within a day, and the preceding six months — to within a month. We do not keep older backups.
When data has disappeared
We restore from a backup at the request of the account administrator. Useful information in the request: what the loss concerns, roughly when the data was still correct and when you noticed it was missing. These three pieces of information determine which backup we use.
Restoring is not self-service. Only people on our side have access to the backups and the key — that is part of what protects them.
What a backup does not cover
- Up to a day's work. A backup is made once a day, so restoring takes the data back to the last nightly backup. Changes made after it have to be entered again.
- It does not restore files. Photos and attachments are outside the database backup — see the note at the top of the page.
- It is not a business continuity plan. A backup protects against data loss and corruption, not against an interruption in access to the system.
- It does not replace care when editing. Restoring from a day ago is often costlier than a moment of attention when saving — especially with contracts, where saving replaces the previous items.
