Backups and recovery

Database backups

SOPCompass’s database runs on a Supabase project on the Pro plan. Supabase documents that Pro plan projects keep 7 days of daily backups. Those backups are managed by Supabase.

We don’t claim more than that:

• We don’t claim point in time recovery.
• We don’t keep a separate copy of the database outside Supabase.
• We don’t offer a guaranteed recovery time (RTO) or recovery point (RPO).

Files are not in those backups

Supabase states that database backups don’t include objects stored through Supabase Storage, only the database’s record of them. Images, screenshots and videos in SOPs are stored there, so a database restore wouldn’t bring back a file that was deleted from storage.

Recovering from everyday mistakes

Most recovery doesn’t need a backup:

• Version history. Each SOP keeps its latest 50 versions. Editors can open History and restore an earlier one. Changes made by approved AI proposals are saved to history before they are applied.
• Archive before delete. An SOP has to be archived before an owner or admin can delete it permanently, so one click can’t destroy it.
• Merges archive, they don’t delete. When Build with AI merges two SOPs, the one folded in is archived.

If something goes wrong

If you think data was lost through a fault on our side, email support@ironbridgeaiadvisory.com as soon as possible. A restore from backup affects the whole database, so it would be decided case by case, and only data within the backup window can be recovered.