Legal

5.10 BUSINESS CONTINUITY & SERVICE RESILIENCE FRAMEWORK

4 min read

Effective Date: August 15, 2026


1. PURPOSE

The Platform maintains a Business Continuity and Service Resilience framework designed to support the ongoing availability of critical services during disruptive events. The Platform uses commercially reasonable efforts consistent with industry standards to maintain structured processes intended to reduce operational impact, protect data integrity, and support service restoration within internally defined recovery objectives.

Continuity strategies are designed to support operational resilience but are not intended to guarantee uninterrupted service availability. While continuity planning reduces risk, no continuity strategy can eliminate all potential service interruptions. Governance procedures are designed to support a defensible response to unforeseen operational events.

2. SCOPE

This Framework applies to systems, infrastructure, personnel dependencies, and operational processes that materially support the delivery of the Services. Continuity planning is prioritized based on risk assessments that evaluate the potential operational, financial, legal, and reputational impact of service disruption.

3. GOVERNANCE & RESPONSIBILITY

Business continuity responsibilities are assigned to designated personnel with defined escalation paths to support coordinated incident response and recovery efforts. The Platform maintains internal procedures reasonably designed to:

  • Identify critical operations;

  • Define response leadership;

  • Support decision-making during incidents; and

  • Coordinate internal and external communications.

4. RECOVERY OBJECTIVES (RTO & RPO)

Recovery objectives are internally defined to guide restoration priorities. While these represent operational targets rather than guaranteed commitments, the Platform structures its architecture to align with the following:

  • Recovery Time Objective (RTO): The target duration of time within which a business process must be restored after a disaster.

  • Recovery Point Objective (RPO): The maximum targeted period in which data might be lost from an IT service due to a major incident.

The Platform does not guarantee that these targets will be met in all circumstances. In the event of a conflict between this Framework and a signed Service Level Agreement (SLA), the terms of the SLA shall prevail only to the extent of the conflict.

5. RISK-BASED CONTINUITY STRATEGY

The Platform applies a risk-based approach to continuity planning, focusing resources on services whose disruption could materially adversely affect Users or business operations. Risk evaluations consider infrastructure dependencies, data criticality, third-party providers, cybersecurity threats, and workforce availability. Continuity strategies are intended to be proportionate to the nature and scale of the identified risks.

6. INFRASTRUCTURE RESILIENCE

The Platform utilizes infrastructure architectures intended to support service stability and fault tolerance. Measures may include redundancy across multiple Availability Zones (AZs), environment isolation, and controlled failover capabilities.

The Platform relies on third-party cloud infrastructure providers; as such, the Platform does not maintain physical custody of the underlying hardware and cannot guarantee the continuous availability of any specific infrastructure provider.

7. DATA PROTECTION & BACKUP PRACTICES

Backup processes are implemented to support data recovery in the event of corruption, loss, or operational disruption. The Platform follows industry-standard backup principles, including:

  • Scheduled Backups: Automated cycles for production databases.

  • Replication Mechanisms: Real-time or near-real-time data mirroring across geographically distinct regions.

  • Integrity Verification: Procedures to ensure backups are restorable.

  • Access Control: Restricted access to backup repositories.

8. INCIDENT RESPONSE INTEGRATION

Business continuity planning operates in coordination with the Platform’s incident response processes. Where recovery efforts conflict with security requirements or forensic integrity, the Platform may prioritize system security and data protection over immediate service restoration.

9. THIRD-PARTY DEPENDENCIES

The Platform relies on third-party providers for infrastructure (e.g., AWS/Google Cloud). These third-party providers operate under their own resilience and continuity frameworks. While providers are selected for their reliability, the Platform does not control third-party continuity practices and cannot guarantee the performance or continuity of third-party infrastructure. Third-party disruptions may materially affect service availability.

10. COMMUNICATION DURING DISRUPTIONS

The Platform maintains communication processes intended to provide Users with material service updates during significant operational incidents when reasonably feasible. The Platform reserves the right to withhold specific details of an incident where disclosure could compromise security or ongoing recovery efforts.

11. TESTING & CONTINUAL IMPROVEMENT

Continuity capabilities are reviewed periodically and may include structured tabletop exercises or scenario analysis. Testing is intended to validate procedures and does not represent a guarantee of performance during an actual disaster.

12. WORKFORCE CONTINUITY

The Platform maintains internal practices intended to support operational continuity during events affecting personnel availability, including cross-functional knowledge sharing and secure remote access controls.

13. SERVICE CONTINUITY LIMITATIONS

This Framework is designed to reduce the likelihood and impact of operational disruption; however:

  • Uninterrupted service cannot be guaranteed.

  • Recovery timelines are not contractual commitments.

  • This Framework does not create any entitlement to financial credits, refunds, or compensation.

Users are encouraged to maintain their own continuity measures and independent backups.

14. FORCE MAJEURE AND UNCONTROLLABLE EVENTS

To the maximum extent permitted by applicable law, the Platform shall not be responsible for data loss, corruption, delay, or retention failure resulting from events beyond its reasonable control, including events affecting the Platform or its service providers, including but not limited to natural disasters, acts of government, war, terrorism, cyberattacks of extraordinary sophistication, widespread internet failures, power grid disruptions, or failures of critical third-party infrastructure.

15. NON-CONTRACTUAL NATURE

This Framework is provided for transparency purposes and does not create contractual obligations, fiduciary duties, heightened standards of care, or warranties unless expressly incorporated into a separate written agreement. This Framework does not constitute legal advice.