Skip to content

Source truth: - Vision and Product Principles - Source Documents - Encrypted Company Data - Managed Local PostgreSQL Launch Deployment - Sensitive Company Data, Key Recovery, and Backup Protection - Company-Scoped PostgreSQL Backup and Atomic Restore

Backup and Restore

Reliable backup and restore are part of accounting safety.

  • Regularly back up company data and configuration.
  • Include managed evidence artifacts with their database records.
  • Before production use, verify that the supported encrypted backup, recovery-key, and restore workflow is available and tested.
  • Test restore procedures before relying on them.
  • Treat restore capability as essential to recover from errors or corruption.
  • Keep the customer recovery secret separate from the database, managed evidence, support bundles, and backups. Losing every recovery-secret copy makes protected data unrecoverable.
  • PostgreSQL application composition enables full-TIN and sensitive W-9 retention only after the live database exactly matches the supported application-schema and company-snapshot catalogs. A mismatch keeps retention blocked.
  • The protected backup boundary captures the company database records, managed sensitive evidence, and company key envelope as one authenticated encrypted unit. Restore replaces only the matching company UUID, preserves later audit events, and does not reactivate captured role assignments without a separate protected review.
  • No backup UI or operating-system recovery-secret store is included yet. Operational deployment must preserve the customer recovery secret separately and invoke the protected application boundary through an approved interface.