Backup & Disaster Recovery Policy

1. Introduction & Objectives

Welcome to Nidamiye (referred to as "Nidamiye", "we", "us", or "our"), a property management and rent-tracking software utility owned and operated by Groundwork Technologies.

To ensure the continuous availability of our rent-tracking utility and guard against accidental data loss, hardware malfunctions, or unexpected outages, we maintain a comprehensive backup and disaster recovery program. This policy outlines our operational parameters to keep your landlord workspace resilient and online.

2. Backup Frequency and Methods

Our database architectures run automated backup jobs to maintain constant snapshots of production states:

• Daily Backups: Full backups of database contents are created automatically every 24 hours.
• Point-in-Time Recovery (PITR): Write-Ahead Logs (WAL) are streamed to separate storage blocks constantly, enabling us to restore database states to precise minute intervals if necessary.
• Application Configurations: Source code deployment assets and build configurations are versioned and stored redundantly across cloud code repositories.

3. Backup Storage and Encryption

Backups contain sensitive data and are protected to the same high security standards as our active production systems:

• Backup Encryption: All backup snapshots are encrypted at rest using AES-256 cryptographic standards.
• Isolation: Backup archives are stored in decoupled, read-only cloud storage segments separate from the active application server environments. This protects backup data from potential application-level compromises.
• Redundancy: Backups are mirrored across multiple physical data storage zones within the cloud infrastructure provider’s network to guarantee access during localized server outages.

4. Recovery Objectives (RPO & RTO)

We establish clear performance targets for data restoration to measure the effectiveness of our resilience processes:

• Recovery Point Objective (RPO): Our target RPO is 4 hours. This means that in the event of a catastrophic system failure, the maximum amount of transaction or landlord configuration updates that could be lost is 4 hours of data.
• Recovery Time Objective (RTO): Our target RTO is 8 hours. This is the maximum targeted duration to restore active application services and dashboards to full operational capacity following a major database or infrastructure failure.

5. Disaster Recovery Process

If a primary infrastructure failure or region-wide hosting outage occurs, our engineering operations team follows a structured disaster recovery procedure:

• Incident Declaration: On-call engineers identify and declare a primary infrastructure event based on monitoring alarms.
• Failover: Server routes are dynamically pointed to staging or replica server zones in secondary cloud locations.
• Data Restoration: If primary databases are corrupted, database administrators deploy the most recent verified backup archive and replay logs to align data.
• Verification: Core API routes, security controls, and payment reconciliation systems are verified for integrity before opening user access.

6. Business Continuity Plan

Our business continuity strategy aims to maintain core operations during extended outages. This includes establishing secondary communication channels, maintaining off-site support structures, and ensuring that our development and operations teams can continue supporting landlords from remote locations.

7. Testing and Validation

Disaster recovery plans are only useful if they are verified to work. Nidamiye conducts periodic drills to validate recovery workflows:

• Backup Verification: Automated scripts verify the integrity and file size of backup archives daily to prevent blank or corrupted logs.
• Simulation Drills: Restores are simulated in staging environments annually to verify RTO/RPO metrics and train personnel on recovery workflows.

8. Monitoring and Incident Logging

We implement automated status checks to monitor system health:

• Heartbeat Checks: Third-party monitoring nodes query our API gateways every 60 seconds to detect platform latency or downtime.
• Alert Systems: Outage states automatically trigger pager alerts to on-call infrastructure engineers 24/7.

9. Customer Communication During Incidents

We value transparency and commit to keeping landlords informed during major disruptions:

• Status Page updates: In the event of downtime, updates will be posted to status.nidamiye.com detailing the issue, progress, and expected resolution time.
• Email Alerts: For issues extending beyond 4 hours, direct notification emails will be sent to registered landlords detailing mitigation steps.