Trust & reliability
Disaster Recovery Policy
How Global Traffic Domains backs up, protects, and restores your data.
Automated daily backups
30-day point-in-time recovery
Encrypted at rest and in transit
How our backups work
Your data lives in a managed PostgreSQL database with continuous write-ahead log archiving. A full automated backup snapshot is taken every day, and every change between snapshots is streamed to backup storage so the database can be rebuilt to any second in the retention window.
After every snapshot the system runs an automatic integrity check: each tracked table is fingerprinted, a checksum is computed, and the stored snapshot is read back and re-verified. A snapshot that fails verification is flagged and an alert is sent to our operations inbox immediately.
Encryption and data protection
Backups are stored in secure, encrypted storage. Data is encrypted in transit (TLS) and at rest. Access to backup and restore controls is restricted to authenticated administrators and every backup and restore event is written to an immutable audit log.
We never sell, rent, share, or expose backup data. Backups exist for one purpose only: restoring your account data if something goes wrong.
Point-in-time recovery
Point-in-time recovery (PITR) means we are not limited to "last night's backup". We can return the database to the exact moment before an incident — for example, one minute before an accidental bulk delete — so the damage is undone while everything preceding it is preserved.
Retention and restore capability
Restore points are retained for a minimum of 30 days. Within that window any moment in time can be selected as a restore target. Restores are previewed before execution, require double confirmation from an administrator, and are logged with the timestamp restored to, the administrator who initiated it, the duration, and the outcome.
How we handle incidents
- Accidental deletion. We identify the time of the deletion and recover to the moment immediately before it, restoring the removed records.
- Corrupted data. Integrity checks and checksum comparisons locate the last known-good restore point, which becomes the recovery target.
- System failure. The database is rebuilt from the most recent verified snapshot plus archived transaction logs, with the platform's redundant infrastructure handling failover.
- Emergency restores. Any restore automatically alerts our operations inbox, is announced in-app, and is recorded in the restore history for review.
Contact
Questions about data protection or a suspected data-loss incident? Email support@mrjpsaiapps.site