Governance and Compliance

Business Continuity and Disaster Recovery Policy

Guidelines for operational continuity, disaster recovery and response to events that impact availability.

Back to Compliance
Governance and ComplianceIn effectReading time: 10 minutes
juridico@haborahub.com.br
Version
1.0
Published on
July 1, 2026
Last updated
July 1, 2026
Next scheduled review
July 1, 2027

1. Purpose

This Policy defines guidelines for operational continuity, disaster recovery and response to events that may impact HABORA's availability.

2. Scenarios

The policy considers infrastructure failures, provider unavailability, security incidents, data loss, operational error, integration failures, network interruptions and extraordinary events.

3. Strategy

HABORA will seek to adopt backups, redundancy, monitoring, response plans, communication with customers, prioritization of critical services and restoration procedures.

4. RTO and RPO

Recovery time and recovery point objectives may vary according to technical maturity, the contracted plan and infrastructure. Enterprise contracts may define specific metrics.

5. Prioritization

Recovery will prioritize authentication, platform access, the database, documents, critical alerts, security, essential reports and data integrity.

6. Communication

During relevant incidents, HABORA may inform affected customers about impact, progress, forecast, mitigation and normalization.

7. Testing

Backup and restoration procedures should be tested periodically when technically possible.

8. Lessons learned

Relevant incidents should generate root cause analysis, corrective actions, control improvements and documentation updates.

Contact

Questions, legal requests, privacy requests, formal communications and requests related to this policy should be sent to juridico@haborahub.com.br.

Updates

This policy may be revised to reflect legal, regulatory, technical, commercial or operational changes. The current version will remain available in the HABORA Compliance area. Material changes may require new acceptance by users, where applicable.

Related documents