Business Continuity & Disaster Recovery
Backup, resilience and recovery approach.
- Version
- 1.0
- Effective date
- 17 August 2026
- Last updated
- 17 August 2026
- Document owner
- the Groundmaster project, with responsibility assigned to its legal and compliance function
- Applicable jurisdiction
- Portugal, European Union
- Permanent URL
- https://www.groundmaster.pt/legal/continuity
1.Approach
The Platform runs on managed cloud infrastructure with redundancy at the hosting, application and storage layers. Continuity relies on managed replication, automated backups, infrastructure that can be rebuilt from versioned configuration, and documented recovery procedures.
2.Backups
| Element | Approach |
|---|---|
| Database | Automated managed backups on a regular cycle, encrypted at rest, with point-in-time recovery where supported by the managed service |
| Uploaded documents | Stored in managed, redundant object storage and included in backup coverage |
| Configuration and application code | Held in version control so environments can be rebuilt deterministically |
| Backup retention | Rolling retention; expired copies are removed automatically |
| Restoration testing | Periodic verification that backups can be restored |
3.Recovery objectives
Recovery objectives are set to restore service and to limit data loss to the shortest practicable period consistent with the backup cycle of the underlying managed services. Specific numeric recovery time and recovery point commitments are only binding where stated in a signed agreement.
4.Scenarios covered
- failure of an application instance or a hosting region component;
- database corruption or accidental destructive change requiring restoration;
- loss of a service provider or the need to replace one;
- security incident requiring isolation and rebuild;
- loss of key personnel access, mitigated by documented procedures and controlled recovery access.
5.Communication during disruption
During a significant disruption, affected customers are informed of the nature of the issue, the expected impact and the status of recovery, with updates until service is restored and a summary afterwards for major events.
6.Customer responsibilities
- maintain periodic exports of records the organisation must retain;
- keep offline or alternative procedures available for time-critical activities;
- keep administrative contact details current so notifications reach the right people;
- ensure sufficient administrator coverage to manage access during an incident.
Change history
| Version | Date | Change |
|---|---|---|
| 1.0 | 17 August 2026 | Initial continuity and recovery statement. |
Questions about this document can be sent to groundmaster.web@gmail.com. Formal legal, privacy, security and regulatory requests should follow the routes described in the legal requests page. Fields shown as bracketed placeholders are pending confirmation by the operating legal entity and do not constitute a statement of fact.