Document Management Policy
Rules for creating, uploading, organizing, versioning, approving, deleting and retaining documents in HABORA.
- Version
- 1.0
- Published on
- July 1, 2026
- Last updated
- July 1, 2026
- Next scheduled review
- July 1, 2027
1. Purpose
This Policy establishes rules for the creation, upload, organization, versioning, alteration, approval, deletion and retention of documents in HABORA.
2. Scope
It applies to contracts, amendments, certificates, property records (matrículas), reports, receipts, attachments, images, spreadsheets, reports, ESG documents, financial documents and files linked to properties.
3. Upload
Users may only upload documents when authorized. The upload must record user, date, property, module, document type, file name and status.
4. Link
Documents must be linked to the company, property, contract, module, responsible user and access permissions.
5. Versioning
Relevant changes must preserve previous versions when technically possible, recording the responsible party, date, reason and comparison when available.
6. Approval
Critical documents may require review or approval by an authorized user before producing operational effects.
7. Deletion
Deletion should preferably be logical, with logs, reason and the possibility of restoration where applicable. Permanent deletion must observe retention and legal obligations.
8. Document AI
AI may assist reading, extraction, classification and reports, without replacing human review and without automatically altering documents without confirmation.
9. Digital signature
When signature integrations are available, signed documents must preserve evidence, status, signatories, dates and final files.
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.