EnigmaSuite

Security policy · BCP-12

Backup, Business Continuity and Disaster Recovery Policy

Document
BCP-12
Version
1.0
Effective
November 18, 2026
Next review
November 2027
Owner
Engineering Lead
Approved by
Executive Management

1. Purpose and scope

This policy sets how Enigmatech Mexico SAPI de CV ("Enigmatech") backs up the EnigmaSuite Platform and restores it after a failure, a security incident or a disaster, so customers can keep operating and their data, including data received from partner platforms such as Amazon, remains available and protected. It applies to the production database, file storage, application servers, configuration and secrets. It supports the Information Security Policy.

2. What is backed up

ComponentBackupFrequencyRetention
Production database (PostgreSQL, managed provider)Provider-managed backups, encrypted at rest with AES-256Daily, with continuous write-ahead-log archiving where enabledRotated within 35 days
Geographically separate copy of the databaseEncrypted copy stored in a cloud region different from the primary regionDailyRotated within 35 days
File storageProvider redundancy across separate facilitiesContinuousFollows the record it belongs to
Application code and infrastructure configurationVersion-controlled repositories, with the full historyEvery changePermanent
Application releasesThe previous release is kept on the server before each deploymentEvery deploymentUntil the next deployment
SecretsManaged secrets vault and the providers' own redundancyEvery changeUntil rotated

All backups are encrypted, are reachable only by the named engineers who run production, and are never copied to endpoints or non-production environments.

3. Recovery objectives

ScenarioRecovery time objective (RTO)Recovery point objective (RPO)
Failed deployment15 minutes (automatic rollback)0
Loss of the application server4 hours0 (no customer data lives only on the application server)
Corruption or loss of database data8 hours24 hours, or minutes where continuous archiving is enabled
Loss of the primary cloud region24 hours, restoring from the geographically separate copy24 hours

Access to buyer personal information needed to ship pending orders is restored first.

4. Disaster recovery procedure

  1. The Incident Commander declares the disaster under the Incident Response Policy and names the recovery team.
  2. The team decides the recovery path: roll back, rebuild the application server from code and configuration, restore the database to a point in time, or restore in another region from the geographically separate copy.
  3. The restore is made to a clean environment, its integrity is checked against record counts and checksums, and deletions made after the backup (for example, buyer personal information past its retention period) are applied again before the system returns to service.
  4. Secrets are rotated if the cause could have exposed them.
  5. Customers are kept informed through the Platform and by email, and platform partners are notified as their terms require.
  6. A post-incident review records the timeline, the objectives met and the improvements needed.

5. Testing

6. Business continuity

7. Review

This policy is reviewed at least once a year and after every disaster recovery event or significant change to the architecture.