Backup & Recovery
Home»Backup & Recovery
Backups, retention, and recovery
Exact recovery-point and recovery-time figures vary by service — rather than publish numbers that don't apply to every deployment, each is defined per service and documented for that engagement.
European storage objective
Backups are intended to remain on European infrastructure alongside the primary service, hosted on HostPowr.
Backup protection
Backups are access-restricted in the same way as production data — not left more exposed than the live system.
RPO (Recovery Point Objective)
Defined per service / deployment, based on the backup schedule agreed for that workload.
RTO (Recovery Time Objective)
Defined per service / deployment, based on the restore procedure agreed for that workload.
Restore procedures
Restores are performed by the technical team on request, following the procedure documented for the affected service.
Recovery testing
Planned as part of ongoing operational maturity — see the Security page for current control status.
The customer data lifecycle
How data moves from collection through to deletion, including the post-termination recovery window. For the bmaikr.com website, the export and deletion steps are a manual, documented procedure carried out through the CMS — not an automated system guarantee. A client-delivered platform may automate this differently, depending on its architecture.
- 01
Collection
Data is collected through the application, forms, or configured integrations required to deliver the service.
- 02
Processing
Data is processed by the application and, where a workflow requires it, by a controlled AI step — see AI Data Handling.
- 03
Storage
Data is stored on the infrastructure configured for the service.
- 04
Backup
Scheduled backups are taken according to the service’s backup configuration — see Backup & Recovery.
- 05
Active service
Data remains in active use for as long as the service is running.
- 06
Export / recovery window
After termination, BMaiKR’s documented operational procedure is to keep data available for approximately one week so the customer can request or export it. For the bmaikr.com website itself, this is a manual step carried out through the CMS, not an automated system function.
- 07
Deletion
After the recovery window closes, the relevant data and service are deleted according to the applicable configuration. On bmaikr.com, this is performed manually rather than by an automated purge job; a client-delivered platform may implement this differently depending on its architecture.