Disaster Recovery Plan

Disaster Recovery Plan

Last updated: 7 April 2026

This page provides a high-level summary of Mercatus Ltd.’s disaster recovery approach for client, partner, and due diligence purposes. It is not a publication of detailed internal recovery playbooks or infrastructure-sensitive procedures.

1. Objective

Mercatus maintains disaster recovery measures intended to support the restoration of critical systems, data, and operational capabilities following disruptive events, including technology failures, cybersecurity incidents, cloud or hosting outages, and other material interruptions.

2. Recovery Priorities

Recovery activities are prioritised according to the criticality of affected services, business impact, information sensitivity, and client delivery requirements. The objective is to restore essential operations in a controlled and secure manner.

3. Recovery Measures

  • restoration procedures for critical systems and services;
  • backup and recovery arrangements for important business data;
  • use of hosted and cloud-based services with resilience and availability controls where relevant;
  • security controls intended to support safe recovery following incidents;
  • internal escalation and coordination for operational restoration.

4. Cyber and Operational Incidents

Where disruption is linked to a cybersecurity or operational incident, recovery activities are coordinated with incident response processes, including containment, assessment, restoration, and appropriate internal and external communications where required.

5. Third-Party Dependencies

Where Mercatus services rely on third-party platforms or providers, those dependencies are considered as part of recovery planning. Recovery may involve coordination with relevant vendors, platform providers, and service partners, depending on the affected systems.

6. Testing and Review

Disaster recovery arrangements are reviewed periodically and may be refined following operational changes, testing activities, incidents, or lessons learned.

7. Confidentiality of Detailed Procedures

For security reasons, Mercatus does not publish detailed disaster recovery runbooks, infrastructure mappings, recovery sequences, or similar sensitive operational materials on its public website. Additional detail may be shared under the appropriate due diligence or confidentiality process where required.

8. Related Continuity Information

For a broader summary of service resilience and continuity governance, please also see our Business Continuity & Disaster Recovery page.

9. Contact

For disaster recovery, resilience, or due diligence questions, please contact info@mercatusoutsourcing.com.