Documentation Security and your data
Backups
What is backed up, how often and for how long: workspace details every day for 7 days, your records every day for 35 days. Attached files are not in a backup.
Sterodata's backups are taken by AWS, in the same Ireland region as the data. The configuration copies none of them to another region.
| What | How it is backed up | Kept for |
|---|---|---|
| Workspace details: tables and fields, views, pages, members, roles and sharing (MySQL on Amazon RDS) | An automated backup every day, between 03:00 and 04:00 UTC. | 7 days |
| Your records: the database file of each workspace (Amazon EFS) | AWS Backup, every day. | 35 days |
| Attached and uploaded files (Amazon S3) | Not backed up. | Only the live copy |
Attached files are not part of any backup, and the storage that holds them keeps no earlier versions. Keep your own copy of any file you could not do without.
The MySQL database is also protected against being deleted by mistake: deleting it is switched off, and removing it through its configuration would leave a final snapshot behind.
What backups are for
Backups are there to restore the service if something goes wrong underneath it. The app has no button to bring a workspace, a table or a record back from a backup.
For a mistake of your own, use what the app gives you:
- Undo straight after deleting records.
- The database's Trash for a deleted table or field, for 30 days (see Who changed what).
- The workspaces Trash for a deleted workspace, for 30 days (see Delete a workspace).
- An export to CSV or Excel, as your own copy (see Export your data).
After you delete something
Backups are not edited when you delete data. Something destroyed in the app stays in the backups taken before, until they reach the end of their 7 or 35 days and expire. See Deleting data.
Last updated 29 October 2026