Your books, safe by architecture
The honest data-safety story is architecture, not promises. Here is where your books actually live and why that shape is resilient.
Two copies by design
The cloud holds the authoritative books; every device holds a working local copy for speed and offline. A dead laptop loses nothing — sign in elsewhere and sync rebuilds it.
Sync as continuous backup
Changes flow to the server continuously, not on a nightly prayer. The distance between 'now' and 'last safe copy' is minutes, not days.
Controls as safety
Permissions limit who can change what; period locks make filed history immutable; the audit trail makes every change attributable. Most data disasters are human — these are the seatbelts.
A backup you have never restored is a hypothesis
The failure mode that actually bites is not the absence of backups but the absence of tested ones — a job that has been silently failing for months, or an archive nobody can open. Restoring a copy occasionally is the only way to know.
Test the restore, not the backup log.
Different risks need different copies
Hardware failure, ransomware, accidental deletion and a bad edit are four different problems, and one nightly copy does not answer all of them. Off-site protects against fire and theft; versioned history protects against a change nobody noticed for a week.
Access control belongs in this conversation too: the fastest way to lose data is to give more people the ability to destroy it than the job requires.
What SeroBooks does with this
Data lives on the server with the local database acting as a working copy, so a lost or failed till is a device problem rather than a data problem — sign in elsewhere and the business is there. Documents carry idempotency keys so reconnection after an outage never duplicates a sale.
Permissions limit who can delete anything, and the audit trail keeps superseded entries rather than erasing them.
See it in your own numbers.
Free to start, on Windows, Mac, iPad and Android. No credit card.