Backups and Data Protection
QuantAssure is in an early pilot, so the recovery targets below are deliberately modest. They are targets we work to on a best-effort basis, not a contractual commitment.
Where your data is hosted
QuantAssure runs on Quant Cloud on AWS in the ap-southeast-2 (Sydney) region. That covers the dashboard, the MCP server, the pipeline workers that collect your data, and scheduled jobs. See Sub-processors and data residency for the full list of services and where each one runs.
What is backed up
| Data | Where it lives | Backup |
|---|---|---|
| Organisation records: findings, assets, policies, risks, evidence, audit logs, reports | Managed MySQL database on Quant Cloud (AWS, Sydney) | Automated backups under Quant's operational policy, kept for 30 days |
We do not currently promise point-in-time recovery or copies in a second region. Backups stay in Australia.
Retention
Database backups are kept for 30 days . After that they are removed by the platform.
Recovery targets for the pilot
| Target | Value | Meaning |
|---|---|---|
| RPO (recovery point objective) | 24 hours | In a restore, you could lose up to the last 24 hours of changes. |
| RTO (recovery time objective) | 1 business day | We aim to have the service restored within one business day of starting recovery. |
Restore testing
We run and record restore tests into a separate environment, never into production. A full database restore was last tested on 16 November 2026. It completed and was verified well within the recovery time objective.
Your own exports
You can also take your own copy of key records at any time. See Reports for CSV and JSON exports.