Anchor by Aurelo
Skip to document
Anchor Logo
Operations

Anchor Business Continuity & Disaster Recovery (BCDR) Plan

This Business Continuity & Disaster Recovery (BCDR) Plan describes the operational strategies used by Aurelo Technologies to help maintain and restore the Anchor platform during disruptive events. It outlines recovery ob

Version 1.0.0Effective 17 July 2026Updated 17 July 202612–15 minutes
On this page

In Summary

This Business Continuity & Disaster Recovery (BCDR) Plan describes the operational strategies used by Aurelo Technologies to help maintain and restore the Anchor platform during disruptive events. It outlines recovery objectives, backup practices, incident management, and customer responsibilities.


Table of Contents

  1. Purpose
  2. Scope
  3. Business Continuity Objectives
  4. Disaster Recovery Strategy
  5. Recovery Priorities
  6. Recovery Targets
  7. Backup Strategy
  8. Incident Management
  9. Third-Party Dependencies
  10. Customer Responsibilities
  11. Testing & Review
  12. Contact
  13. Related Documents

1. Purpose

This document explains the operational practices used to improve the resilience and recoverability of the Anchor platform.


2. Scope

This plan applies to the Anchor platform, supporting infrastructure, authentication services, and operational systems managed by Aurelo Technologies.


3. Business Continuity Objectives

Anchor aims to:

  • Minimize service disruption
  • Restore critical services efficiently
  • Protect customer information
  • Maintain operational communications
  • Continuously improve recovery procedures

4. Disaster Recovery Strategy

Recovery planning includes:

  • Cloud-based infrastructure
  • Verified backups
  • Infrastructure redundancy where appropriate
  • Incident response procedures
  • Documented recovery processes

5. Recovery Priorities

Priority order during recovery:

  1. Identity and authentication
  2. Core platform availability
  3. Event management
  4. Ticketing and donations
  5. Administrative services
  6. Analytics and reporting

6. Recovery Targets

Operational targets include:

ObjectiveTarget
Recovery Time Objective (RTO)Target defined operationally based on service impact
Recovery Point Objective (RPO)Target defined operationally based on backup schedules

These objectives are operational goals and are not contractual guarantees.


7. Backup Strategy

Anchor maintains backups appropriate for the services provided.

Current retention practices include:

  • Active account data until deletion
  • Soft-deleted accounts for 30 days
  • Transaction records for up to 7 years
  • Security logs for up to 12 months
  • Automated backup rotation

8. Incident Management

Major incidents follow documented procedures covering:

  • Detection
  • Assessment
  • Containment
  • Recovery
  • Customer communication where appropriate
  • Post-incident review

9. Third-Party Dependencies

Business continuity depends in part on trusted providers including:

  • Amazon Web Services (AWS)
  • Google Cloud
  • Oracle Cloud
  • DigitalOcean
  • Paystack
  • Amazon SES
  • Resend

10. Customer Responsibilities

Customers should:

  • Maintain secure credentials
  • Enable Multi-Factor Authentication where available
  • Keep contact information current
  • Report service issues promptly
  • Maintain their own copies of important exported data where appropriate

11. Testing & Review

Recovery procedures are reviewed periodically and updated as the platform evolves.


12. Contact

Support: support@technologies.aurelo.cc

Legal: legal@technologies.aurelo.cc


13. Related Documents

  • Service Level Agreement (SLA)
  • Enterprise Security Whitepaper
  • Compliance Overview
  • Responsible Disclosure Policy
  • Privacy Policy