RepLogix Business Continuity & Disaster Recovery Plan

This plan applies to RepLogix's core services, including the web application, mobile app, database, and supporting infrastructure. It covers disruptions caused by system failures, natural disasters, cyber incidents, and third-party outages.

RTO = maximum acceptable downtime. RPO = maximum acceptable data loss. Actual recovery times depend on Base44 infrastructure capabilities.

• Base44 Platform: Application hosting, database, authentication, and file storage
• Stripe: Payment processing and subscription management
• Resend: Email delivery for notifications and invitations
• Twilio: SMS notifications
• Google OAuth: Authentication provider

RepLogix is hosted on the Base44 platform, which maintains SOC 2 Type II and ISO 27001 certifications. Infrastructure redundancy, replication, and physical security are managed by Base44 and its cloud providers. See the Base44 Security Trust Center for details.

• Database backups are maintained by Base44 infrastructure with encrypted at-rest storage
• Backups are stored within the United States
• Backup frequency and retention are governed by Base44's SOC 2 / ISO 27001 controls
• RepLogix also maintains a data export function allowing customers to export their data as CSV

• Backup restoration procedures are tested at least annually
• Restoration tests verify data integrity and completeness
• Test results are documented, including restoration time and any issues encountered
• Remediation actions are tracked if restoration issues are identified

System Failure:

• Monitor alerts and confirm the failure with Base44 infrastructure status
• Initiate failover or recovery through the Base44 platform
• Verify data integrity after restoration
• Communicate status to affected customers

Data Corruption:

• Identify the scope of corruption
• Restore affected data from the most recent valid backup
• Validate restored data with affected customers where possible
• Document the incident and root cause

Third-Party Outage:

• Confirm the outage with the third-party provider's status page
• Activate fallback procedures or communicate degraded service to customers
• Monitor for restoration and verify functionality when service returns

In the event of a prolonged outage, RepLogix maintains continuity through:

• Customer data can be exported as CSV, allowing manual continuity if the application is unavailable
• Communication channels (email, phone) remain available through third-party providers independent of the application
• Critical personnel have documented contact information available outside of the application
• Incident response procedures are activated to coordinate recovery (see Incident Response Plan)

• This BCDR Plan is reviewed and updated at least annually
• Disaster recovery procedures are tested at least annually
• Lessons learned from tests and actual incidents are incorporated into plan updates

For questions about this plan, contact: