Data retention & recovery

Your org's data on Turtini is protected by a three-layer recovery system. Different layers cover different scenarios.

Point-in-time recovery — last 7 days:
Every Firestore write is journaled continuously. If a record is corrupted, miswritten, or accidentally deleted, we can rewind the database to any moment in the last 7 days. This is the primary recovery path for "oops" scenarios — covers the vast majority of real recovery needs.

Weekly snapshots — last 90 days:
Every Sunday, the entire database is snapshotted to long-term storage (the gs://turtini-firestore-backups bucket, retained 90 days). This covers data older than the 7-day PITR window but within a quarter — useful for forensic recovery or longer-rollback scenarios.

File version history — last 30 days:
Files you upload to Turtini (logos, documents, photos, attachments) are versioned. If a file is overwritten or deleted, the previous version is recoverable for 30 days from the moment it was replaced.

What's NOT covered:
• Stripe state (payments, subscriptions, Connect account state) — Stripe is the source of truth for those; restoring our database may require a reconciliation pass against Stripe
• External integrations (Gmail, Google Calendar, Cloudflare DNS, etc.) — those systems retain their own data independently

How to request a restore:
Email [email protected] or contact your account rep with the time of the incident and what was affected. We'll assess whether the issue is recoverable via PITR (fastest) or requires a snapshot restore. Most restores complete within 1–2 hours.

This retention is metered alongside other platform usage (it costs us GCP storage; we pass that through at +15% like every other infrastructure cost). Small orgs typically see less than $0.50/month for retention; charges accumulate into the same $5 invoicing threshold described in the Pay-as-you-go article.