Effective Date: May 15, 2026
| Category | Default retention | Notes |
|---|---|---|
| Operator account data (profile, configuration, settings) | Duration of Account + 90 days post-termination | Extendable under legal hold |
| Billing records | 7 years from last transaction | Tax and accounting law |
| Consent records and evidence vault | Customer-configured; default 7 years from capture | Business+ may configure windows where supported |
| Security and audit logs | 12–24 months from event | Anti-abuse, incident investigation |
| Support communications | 3 years from last interaction | Service improvement, dispute resolution |
| AI conversation logs (compliance assistant, support chat) | Up to 90 days, then purged or aggregated | Safety, abuse detection, model evaluation |
| Edge cache and transient state | TTL-limited (seconds to hours) | Operational performance |
| Backups | Standard rotation, typically 30–90 days | Then overwritten |
| Aggregated / de-identified analytics | Indefinitely | Cannot be linked to a Data Subject |
Customer-configurable retention applies to Consent Records and operator-controlled data where the product supports it. CapchaCloud-controlled data (operational logs, security signals, billing) is retained per the table above.
When deletion is triggered (Customer request, account termination, expiration of retention window), CapchaCloud: (1) removes the data from active databases and storage within 90 days of the trigger; (2) issues confirmation on written request to support@serviceautomations.ai (subject: “Deletion confirmation”).
Backups are immutable for their retention window. Data in backups is deleted on the normal backup rotation cycle, typically within 30–90 days of deletion from active systems.
Data subject to legal hold (preservation order, litigation, regulatory inquiry, BAA-related retention requirement) is retained beyond the standard window. CapchaCloud will document the basis for the hold and resume deletion when the hold expires.
CapchaCloud may retain de-identified data indefinitely. CapchaCloud commits not to re-identify de-identified data except as permitted by law.
End User Data Subject Rights requests for data Processed on a Customer’s behalf are routed to the Customer as Controller (DPA §8). For data CapchaCloud Processes as Controller (operator data), Customers and Data Subjects may submit requests directly:
Customers may export their data via the dashboard or documented API at any time during the Service term and within the 30-day Export Window after termination. Exports are provided in machine-readable form (JSON or equivalent). See Terms §18.
support@serviceautomations.ai — use clear subject lines (“DSAR”, “Deletion”, “Security”).
End of data retention and deletion policy. Last updated: May 15, 2026.