Backup Policy

1. Purpose

To ensure critical data can be restored after loss, corruption, or an incident.

2. Scope

Source code, project and client assets, configuration, and business-critical data.

3. Approach

• Source code is maintained in version control with full history.
• Client and project assets are stored in redundant, backed-up cloud storage.
• Cloud databases use the managed backup features of our platforms (e.g. Supabase).

4. Frequency & retention

• Critical data is backed up at least daily.
• Backups are retained long enough to recover from a delayed-detection incident.

5. Testing

Restores are tested periodically to confirm backups are usable.

6. Review

This policy is reviewed at least annually.