Quip Backup Policy

Live Data Replication

All persistent customer data is stored on Amazon RDS instances configured for Multi-AZ deployment. Multi-AZ (Multiple Availability Zones) means Amazon maintains a standby copy of the database in a second geographic availability zone. In the event of a primary zone outage, traffic automatically fails over to the standby replica with minimal disruption. Quip also maintains its own complete replica of all databases in an additional, separate region as an extra layer of redundancy.

Incremental Backups

Quip maintains continuous, point-in-time incremental backups of all live databases. These backups capture changes as they occur and allow Quip to restore data to any point within the past 24 hours in the event of a partial outage or data issue. Incremental backups are no more than 5 minutes behind the live data at any given time.

Example: If a data corruption event occurs at 2:00 PM, Quip can restore the affected data to its state as of 1:55 PM using an incremental backup — limiting data loss to at most 5 minutes of changes.

Daily Snapshots

In addition to incremental backups, Quip takes full daily snapshots of all production databases. These snapshots are stored outside of RDS on Amazon S3 file storage and are replicated across multiple geographic regions for additional protection.

Key details about daily snapshots:

• Retention: At least 2 weeks of full system snapshots are retained at all times
• Coverage: Snapshots include all customer data and are sufficient to restore the entire Quip site in the event of a catastrophic failure
• Recovery use: Snapshots are used when incremental backups are insufficient, such as for complete site restoration after a major incident

Review of Procedures

Quip's backup policies are reviewed and updated by the Head of Engineering on a regular basis to ensure they remain aligned with industry standards and customer requirements.