Continuity and Recovery Plan
Business continuity and disaster recovery in a single document, at the company's real scale — with targets that come from what is practiced, not from what sounds good.
Version 1.0 — effective September 1, 2026.
1. Backups
- Daily backup of the database, retained for 90 days, with restricted access.
- Restores are exercised routinely — restoring a backup is part of the team's normal workflow, not a drawer procedure tested once a year.
- All source code is versioned outside the production environment, and the systems can be rebuilt from it by documented procedure.
2. Disaster recovery
Loss of the environment is handled by a documented, step-by-step rebuild: provision the server, restore the latest database backup, publish the systems from versioned source — the database schema is upgraded automatically by the application itself on startup — and reissue the certificates, whose renewal is automatic in normal operation as well.
3. The targets, declared
| Metric | Commitment |
|---|---|
| Maximum data loss (RPO) | up to 24 hours — whatever came in after the last daily backup |
| Rebuild time (RTO) | up to one business day |
These numbers come from the environment's real design. We prefer honest targets to high-availability promises we do not practice — whoever depends on our systems deserves to plan with the true number.
4. During an outage
Management communicates, through the company's contact channels. An outage with suspicion of malicious cause switches tracks: the Incident Response Plan applies.
Version 1.0 — September 1, 2026.