Business Continuity Plan Summary
Public summary of how critical platform operations are protected and restored after disruption.
- Document type
- Information policy
- Category
- Platform and data operations
- Version
- 2026-08-24
- Effective
- August 24, 2026
- Issued by
- Ohana Capital AG
On this page9 sections
1. Purpose
This Business Continuity Plan (BCP) Summary describes how Ohana Capital AG (“Ohana Capital”) intends to maintain or restore critical platform operations after a disruption. It is a public summary for customers and stakeholders. Operational detail is maintained internally and may be updated as systems evolve.
2. Scope
The plan covers critical capabilities such as:
- Account authentication and access controls
- Market-data and order-workflow interfaces
- Portfolio, ledger, and risk records
- Operator and support communications
- Core databases, application hosting, and supporting infrastructure
Non-critical marketing or secondary content may be restored after primary services.
3. Objectives
Primary objectives are to:
- Protect customer data and system integrity
- Restore authenticated access as quickly as practicable
- Preserve accurate financial and audit records
- Communicate status during material outages
- Reduce the impact of infrastructure, vendor, or facility failures
Recovery priorities and target times are set internally according to service criticality and available redundancy.
4. Continuity approach
4.1 Infrastructure resilience
Production systems are designed with redundant hosting, managed databases, backups, and monitoring. Configuration and deployment practices are intended to support recovery from host, region, or dependency failure.
4.2 Data protection
Databases and critical stores are backed up on a scheduled basis. Restore procedures are tested periodically. Access to backups and production systems is restricted to authorized personnel.
4.3 Vendors and dependencies
Critical third-party services (for example hosting, authentication, email, market data, or analytics) are monitored. Material vendor disruption may trigger failover, degraded mode, or temporary suspension of affected features.
4.4 People and escalation
Incident response roles include technical response, communications, and escalation to senior management. Support and operations teams follow runbooks for common failure modes.
5. Customer impact during an incident
During a disruption, some or all of the following may occur:
- Delayed sign-in or temporary inability to place or modify instructions
- Stale or unavailable market data
- Delayed support responses
- Temporary suspension of funding, withdrawal, or product workflows
Orders, balances, and risk controls may be unavailable or limited until systems are restored and data integrity is confirmed.
6. Communications
Material service incidents may be communicated through the website, in-platform notices, email, or support channels, depending on the nature of the event and available systems.
7. Testing and review
Continuity arrangements are reviewed and tested on a risk-based schedule. Findings may lead to updates to architecture, runbooks, vendor arrangements, or this summary.
8. Limitations
No continuity plan can eliminate all risk of interruption. Force majeure, widespread infrastructure failure, cyber attack, regulatory action, or cascading vendor outages may delay recovery beyond target objectives.
Questions about this document?
Contact Ohana Capital AG and include the document title and version in your message.
