Korven One Business Continuity & Disaster Recovery Plan

Korven One is committed to maintaining operational resilience and ensuring continuity of critical services during disruptive events. This Business Continuity and Disaster Recovery Plan (BCDR) establishes the framework used to prepare for, respond to, recover from, and mitigate operational disruptions affecting Korven One systems, services, customers, partners, and financial operations.

This Plan applies to:

• Payment Infrastructure
• Wallet Infrastructure
• Merchant Services
• Developer Platform
• Treasury Operations
• Settlement Operations
• Remittance Services
• Cloud Infrastructure
• Employees
• Contractors
• Critical Vendors
• Banking Partners

Korven One aims to:

• Protect customer funds
• Maintain critical operations
• Restore services quickly
• Minimize financial losses
• Protect customer data
• Maintain regulatory readiness
• Preserve customer trust

Korven One follows the following principles:

• Operational Resilience
• Customer Protection
• Data Integrity
• Service Availability
• Rapid Recovery
• Risk Reduction
• Continuous Improvement

The following functions are considered critical:

Tier 1 Critical

• Payment Processing
• Ledger Operations
• Wallet Balances
• Treasury Operations
• Settlement Processing
• Authentication Systems

Tier 2 Important

• Merchant Dashboard
• Developer Portal
• Analytics
• Reporting

Tier 3 Non-Critical

• Marketing Website
• Blog
• Documentation Portal

Recovery priorities shall follow this classification.

Recovery Time Objective (RTO)

Maximum acceptable downtime:

• Tier 1: 4 Hours
• Tier 2: 24 Hours
• Tier 3: 72 Hours

Recovery Point Objective (RPO)

Maximum acceptable data loss:

• Financial Systems: 15 Minutes
• Operational Systems: 1 Hour
• Non-Critical Systems: 24 Hours

This Plan may be activated when events significantly impact:

• Availability
• Security
• Financial Operations
• Customer Access
• Treasury Operations

Activation authority may be assigned to executive leadership or designated response teams.

In the event of a major AWS disruption, Korven One may:

• Activate secondary recovery procedures
• Failover critical services where available
• Prioritize payment and ledger services
• Communicate service status updates

Critical systems should be designed for high availability where feasible.

If database corruption occurs, Korven One may:

• Isolate affected systems
• Suspend impacted operations
• Restore verified backups
• Validate ledger integrity
• Perform reconciliation reviews

Recovery actions shall be documented.

If a datacenter becomes unavailable, Korven One may:

• Activate backup infrastructure
• Redirect traffic
• Restore critical services
• Verify transaction integrity

Priority shall be given to customer fund protection.

Examples:

• Unauthorized Access
• Malware
• DDoS Attacks
• Infrastructure Compromise

Korven One may:

• Isolate affected systems
• Restrict access
• Activate incident response procedures
• Increase monitoring
• Notify relevant stakeholders

In the event of ransomware, Korven One may:

• Disconnect affected systems
• Preserve forensic evidence
• Restore clean backups
• Validate financial records
• Conduct security reviews

Customer funds shall remain the highest priority.

If a major outage occurs, Korven One may:

• Activate incident management procedures
• Prioritize critical services
• Provide customer communications
• Escalate operational response teams

If a banking partner experiences disruption, Korven One may:

• Suspend affected settlement operations
• Activate alternative banking procedures where available
• Notify impacted users
• Monitor treasury exposure

Treasury operations shall review liquidity impact.

If a payment rail becomes unavailable, Korven One may:

• Route transactions through available channels
• Delay settlement activities
• Restrict affected transaction types

Business continuity teams shall assess operational impact.

Examples:

• Earthquakes
• Hurricanes
• Flooding
• Severe Weather Events

Korven One may:

• Activate remote operations
• Prioritize employee safety
• Protect customer data
• Maintain essential services

Examples:

• Internet Disruptions
• Political Instability
• Infrastructure Failures
• Telecommunications Outages

Korven One may:

• Activate contingency procedures
• Increase operational monitoring
• Protect treasury operations
• Maintain communication channels

Korven One shall maintain:

• Automated Backups
• Encrypted Backups
• Backup Verification Procedures
• Periodic Restoration Testing

Backups shall be stored securely.

Korven One may periodically perform:

• Backup Restoration Tests
• Failover Testing
• Incident Simulations
• Tabletop Exercises
• Treasury Recovery Exercises

Testing results may be documented and reviewed.

Korven One may communicate with:

• Customers
• Merchants
• Developers
• Banking Partners
• Service Providers
• Regulatory Authorities

Communication procedures shall be coordinated and documented.

Employees involved in continuity planning must:

• Follow response procedures
• Participate in training
• Report incidents promptly
• Support recovery efforts

Korven One may depend on:

• Cloud Providers
• Banking Partners
• Identity Verification Providers
• Payment Processors
• Communication Providers

Business continuity planning shall consider third-party risks.

Korven One management shall oversee:

• Business Continuity Planning
• Disaster Recovery Planning
• Recovery Testing
• Risk Reviews
• Incident Reviews

Periodic reviews shall be conducted.

Following disruptions or testing activities, Korven One may:

• Review lessons learned
• Improve recovery procedures
• Update controls
• Enhance resilience

This Plan may be updated periodically. Updates will be published through Korven One governance procedures.

Korven One Business Continuity Team

• Email: bcdr@korvenone.com
• Email: security@korvenone.com
• Email: treasury@korvenone.com
• Support: support@korvenone.com
• Website: https://korvenone.com

The official version of this Plan is the English version. Translations may be provided in:

• Haitian Creole
• French
• Spanish

In case of conflict, the English version shall prevail.