Disaster Recovery Statement

This Disaster Recovery Statement describes MiseCentral LLC's ("MiseCentral," "we," "us," or "our") disaster recovery architecture and objectives for the Services. This statement supplements the Business Continuity Policy, Service Availability Policy, and Agreement.

1. Purpose

1.1. MiseCentral maintains disaster recovery capabilities to restore the Services and Customer Data following major infrastructure failures, region-wide cloud outages, catastrophic data corruption, or destructive cyber incidents affecting production systems.

1.2. This statement describes platform-level objectives. Enterprise Order Forms may specify enhanced recovery commitments where available.

2. Architecture Overview

2.1. Primary Region. Production Services operate in a designated primary cloud region within the United States using managed cloud infrastructure.

2.2. Backups. Customer Data in production databases and object storage is backed up on a recurring schedule. Backups are stored separately from primary production systems within the same cloud provider ecosystem.

2.3. Secondary Recovery. MiseCentral maintains the capability to restore Services in a secondary cloud region for disaster scenarios where the primary region is unavailable for an extended period.

2.4. Configuration and Code. Application configuration, infrastructure definitions, and deployment artifacts are version-controlled and recoverable independently of production runtime state.

3. Recovery Objectives

3.1. Recovery Time Objective (RTO). Platform-level target RTO for restoration of core Services following a qualifying disaster event is twenty-four (24) hours. Actual recovery time depends on event scope, data volume, and validation requirements.

3.2. Recovery Point Objective (RPO). Platform-level target RPO for Customer Data is four (4) hours, meaning backup frequency is designed so that restorable data is generally no more than four hours old at the time of failure. Real-time synchronous replication is not guaranteed for all data types unless specified in an enterprise Order Form.

3.3. Validation. MiseCentral validates restored environments before returning them to production use, including integrity checks and security review.

4. Disaster Declaration and Activation

4.1. MiseCentral leadership or designated incident commanders declare a disaster recovery event when primary production is unavailable or corrupted beyond normal incident recovery within a reasonable period.

4.2. Activation triggers failover or restoration procedures, customer communications, and enhanced monitoring.

5. Customer Data Restoration

5.1. Restoration prioritizes integrity and security over speed. MiseCentral restores Customer Data from the most recent clean backup consistent with the RPO.

5.2. Data created after the last recoverable backup point may not be restorable. Customer should use export capabilities for critical records according to Customer's regulatory requirements.

5.3. Operational Evidence, audit logs, and advisory output history are restored consistent with available backup scope.

6. Testing

6.1. MiseCentral performs recurring backup restoration tests in non-production environments to verify recoverability.

6.2. Full regional failover tests are conducted periodically or through controlled simulations, with results informing plan updates.

6.3. Test outcomes and corrective actions are tracked internally. Summary information may be provided to enterprise Customers under confidentiality upon request.

7. Customer Responsibilities

7.1. Customer is responsible for maintaining independent archives of records required by food-safety, quality, traceability, or regulatory obligations beyond MiseCentral's recovery objectives.

7.2. Customer should document integration dependencies and local offline procedures for critical hospitality operations during extended outages.

7.3. Customer-initiated destructive actions, including bulk deletions through product controls, may not be reversible through disaster recovery except where deletions have not yet propagated through backup rotation.

8. Exclusions

8.1. Disaster recovery does not cover:

(a) recovery from Customer's misuse or unauthorized configuration changes; (b) data loss in Customer-managed or Connected Service systems; (c) events excluded under the Service Availability Policy or SLA; or (d) force majeure events that prevent recovery within stated objectives despite commercially reasonable efforts.

9. Communication

9.1. During disaster recovery activation, MiseCentral communicates status through the Service Availability Policy channels and direct notice to Customer administrators for material impacts.

10. Contact

MiseCentral LLC Attn: Security 8 The Green, Suite A Dover, DE 19901 United States security@misecentral.com