Data Backup & Retention Policy
Data Backup
Tango’s application is deployed in a clustered environment, and application servers within the cluster are deployed in different physical Amazon data centers to provide failover (the process of switching between primary and secondary systems or system components) and load balancing to distribute application traffic among several services. In the event of a disaster, the entire application and database can be rebuilt within four hours of a disaster with minimal data loss. Tango database procedures include:
For components that leverage Oracle databases, weekly backup notifications are sent to the database administrator for both successful and failed full backups.
- Database transactions are continuously backed up and replicated to the disaster recovery site using Oracle Data Guard technology
- Tango Management Consulting, Inc.’s application layers can be rebuilt from source code control within an hour
- Incremental and full backups act as a secondary safeguard against data loss and are leveraged for development and support when needed
All other components utilize AWS RDS features for backups. The automated backup feature of Amazon RDS enables recovery of your database instance to any point in time within your specified retention period of up to 35 days. In addition, user-initiated full backups of the database Instance will be stored by Amazon RDS until you explicitly delete them.
Annual reviews and testing are conducted by senior management, IT and HR to review data backup and retention policies.
Data Retention
Customer Contracts dictate the length of time after contract termination or expiration before customer data is deleted. Unless otherwise specified, Tango’s standard policy is within 30 days in order to provide customers time to receive their data before deletion.