Skip to content
MiseCentral
Platform Overview Work Intelligence Product Tour Technology Profile Integrations Implementation Enterprise Administration
Solutions Overview Capabilities Overview Recipes Production Operations Inventory Purchasing Quality Traceability Food Safety Labor Planning Company Brain
All Industries Restaurants Hospitality Catering Production Retail Food Distribution
Work Intelligence Trust
Resource Center Customer Stories ROI Pricing Support
About How We Operate Media Trust Center Procurement Contact
Sign In Book a Demo
Home · Security · Business Continuity Policy

Business Continuity Policy

Business continuity commitments.

Version
1.0
Effective
August 1, 2026
Last updated
August 1, 2026
Document ID
LEGAL-SUP-004
Download PDF Contact Legal Contact Privacy

On this page

  1. 1. Objectives
  2. 2. Scope
  3. 3. Business Impact Analysis
  4. 4. Continuity Strategies
  5. 5. Continuity Procedures
  6. 6. Testing and Maintenance
  7. 7. Customer Responsibilities
  8. 8. Limitations
  9. 9. Contact

All legal documents

Business Continuity Policy

This Business Continuity Policy describes how MiseCentral LLC ("MiseCentral," "we," "us," or "our") maintains continuity of the Services and supporting operations during disruptive events. This policy supplements the Disaster Recovery Statement, Service Availability Policy, and Agreement.

1. Objectives

1.1. MiseCentral maintains business continuity capabilities intended to:

(a) protect the safety and availability of personnel and systems; (b) continue or promptly restore delivery of the Services during infrastructure failures, cloud provider outages, cyber incidents, or facility disruptions; (c) preserve integrity of Customer Data during and after disruptive events; and (d) communicate with Customers regarding material Service impacts.

1.2. Customer remains responsible for continuity of Customer's own facilities, local operations, food-safety programs, and decisions that depend on advisory Operational Recommendations.

2. Scope

2.1. This policy covers MiseCentral's hosted Services platform, production infrastructure, core support functions, and security operations necessary to maintain the Services.

2.2. Professional Services engagements may be subject to separate continuity arrangements in Statements of Work.

3. Business Impact Analysis

3.1. MiseCentral identifies critical Service components, dependencies on Subprocessors and cloud regions, and personnel roles required for minimum viable operations.

3.2. Analysis is reviewed periodically and updated when architecture or Subprocessor arrangements materially change.

4. Continuity Strategies

4.1. Infrastructure Redundancy. Production architecture uses redundant components within primary cloud regions, including load distribution, automated failover where configured, and health monitoring.

4.2. Geographic Recovery. Disaster recovery capabilities may utilize secondary cloud regions as described in the Disaster Recovery Statement.

4.3. Data Protection. Backups and replication support recovery of Customer Data consistent with recovery objectives in the Disaster Recovery Statement.

4.4. Personnel. MiseCentral maintains remote-capable operations for engineering, support, and security functions. Critical roles have designated alternates.

4.5. Third-Party Dependencies. MiseCentral monitors Subprocessor status and maintains contingency plans for loss of critical vendor services.

5. Continuity Procedures

5.1. Upon detection of a disruptive event, MiseCentral activates internal incident management procedures aligned with the Incident Response Policy.

5.2. Response actions may include traffic rerouting, scaling resources, failing over to secondary infrastructure, restoring from backups, or temporarily disabling non-essential functions to preserve core operations.

5.3. Customer-facing communications follow the Service Availability Policy and Incident Response Policy.

6. Testing and Maintenance

6.1. MiseCentral tests backup restoration and disaster recovery procedures on a recurring basis appropriate to platform risk.

6.2. Tabletop exercises and scenario reviews evaluate coordination among engineering, support, security, and leadership teams.

6.3. Lessons learned from tests and actual events inform updates to continuity plans.

7. Customer Responsibilities

7.1. Customer should maintain local continuity plans for hospitality operations that may continue during Service interruptions, including offline procedures for critical food-safety and quality controls where applicable.

7.2. Customer should maintain current administrator contacts and export critical records according to Customer's regulatory requirements.

7.3. Customer should configure Connected Services and integrations with awareness of dependency risks.

8. Limitations

8.1. Business continuity measures reduce but do not eliminate risk of interruption. Force majeure events and failures outside MiseCentral's reasonable control may exceed planned recovery capabilities.

8.2. Recovery time and recovery point objectives are described at the platform level in the Disaster Recovery Statement and may vary by subscription tier or Order Form.

9. Contact

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

Service status inquiries: legal@misecentral.com

Version history

VersionEffectiveSummary
1.0August 1, 2026Initial publication of the Legal Library (LEGAL-01).

Previous versions remain available for reference and are never overwritten.

MiseCentral

The Adaptive Operating System for Hospitality—smoother operations, adaptive intelligence, and people in command.

Product

Product Tour Platform Work Intelligence Solutions Industries Pricing

Trust

Trust Center Legal Privacy Security Status Responsible AI

Company

About Resources Support Procurement Contact Book a Demo
© MiseCentral LLC. All rights reserved. · Terms · Privacy · Cookies · Trust Center · Trademark