Imperial Eminence Cyberguard Corporation · The Ivory Index

Business Continuity & Disaster Recovery Policy

Tier V — Security Program · Ref: IECC-T5-002 · Version 1.0 · Effective 14 June 2026

Article I — Purpose & Scope

This Business Continuity and Disaster Recovery Policy ("BCP/DR") ensures that IECC can continue critical operations and recover from disruptive events, whether technical, operational, or personnel-related. It covers The Ivory Index Software operations, customer-facing services, and internal business functions.

Article II — Business Impact Analysis

Article III — Disaster Scenarios & Responses

Scenario A — Primary Development Device Failure ("Laptop Dies")

• Prevention: Source code mirrored to remote repository (GitHub/GitLab) after every commit; no single-device dependency for code
• Recovery: Clone repository to replacement device; restore development environment from documented setup guide; estimated recovery: 4–8 hours
• Customer impact: None if incident resolves within 24 hours; support response times may be extended

Scenario B — Cloud Provider Outage ("Cloud Provider Dies")

• Prevention: Software is local-first; core product does not depend on IECC cloud services for functionality
• Recovery: Failover to alternative cloud region or provider; estimated activation: 2–4 hours for pre-configured failover
• Customer impact: Web-based services affected; desktop Software unaffected

Scenario C — Data Corruption ("Database Corrupts")

• Prevention: Daily automated backups with 30-day retention (cloud services); point-in-time recovery enabled where supported
• Recovery: Restore from most recent clean backup; validate data integrity before resuming service; estimated RTO: 4 hours; RPO: 24 hours
• User local data: IECC cannot recover locally-stored User data; Users are advised to maintain their own backups of ~/.theivorry/

Scenario D — Key Personnel Unavailability ("Founder Disappears for 30 Days")

• Prevention: All critical credentials and access documented in encrypted password manager accessible to designated backup contact
• Documented handover items: Cloud provider access; domain registrar; code signing certificates; customer support platform; financial accounts
• Escalation path: Designated backup contact assumes operational authority; external counsel notified if unavailability exceeds 14 days
• Customer communication: Support response times extended; Customers notified via website banner within 48 hours of confirmed extended unavailability

Scenario E — Cybersecurity Incident

Covered by the Incident Response Policy (IECC-T4-003). This BCP/DR focuses on operational continuity post-incident.

Article IV — Recovery Objectives

Article V — Testing & Review

• BCP/DR procedures are reviewed annually and following any invocation of the plan
• Recovery procedures for Scenario A and B are tested at least once per year
• Backup restoration is tested quarterly for cloud services
• Results of tests are documented; gaps are remediated within 30 days

Article VI — Contact

Business continuity enquiries: legal@imperialecc.com.

Drafted with the assistance of

Voidlex

Imperial Legal Intelligence · IECC Suite · v2.6

This document was prepared with the assistance of Voidlex, a legal document drafting tool developed by Imperial Eminence Cyberguard Corporation (IECC). Voidlex is a drafting aid only. It does not constitute legal advice, does not practice law, and does not guarantee the legal enforceability of this document in any jurisdiction. Users are strongly encouraged to seek independent legal counsel before relying on this document for commercial, regulatory, or enforcement purposes.

Governing Law — All Disputes Cayman Islands · Grand Court of the Cayman Islands

IECC Registered Operations Planned Cayman Islands registration · pre-incorporation stage

Drafting System Voidlex v2.6 · Imperial Eminence Cyberguard Corporation

TRIBUNEH · IECC Legal Division