Taicho legal
Data Retention, Deletion, and Export
Proposed lifecycle rules and the operational state of customer-data controls.
- Status
- Draft — legal approval required
- Effective date
- Effective date pending legal approval
Proposed schedule pending approval and implementation
| Data class | Proposed period | Current implementation state |
|---|---|---|
| Account, workspace, leads, content, campaigns, automations | Subscription term plus approved deletion window | Export/deletion workflow not yet launch-ready |
| Encrypted CRM and integration credentials | Until disconnect, revocation, or account deletion | Tenant-bound encryption implemented; rotation evidence incomplete |
| Operational request, job, and audit records | 90 days unless security or contract requires longer | Retention enforcement requires operations approval |
| Privacy-filtered cloud telemetry | 30 days | Exporters implemented; providers not fully launch-configured |
| Local attribution ledger | 180 days | Configured value; purge verification pending |
| Database and graph backups | Approved backup retention window | Off-host encrypted backup and restore drill pending |
| Email suppression records | As needed to honor opt-out and delivery obligations | Deletion exceptions require legal approval |
| Billing, tax, and legal records | Period required by applicable law | Market-specific period pending counsel |
Deletion
Verified deletion requests must be scoped to the correct organization, preserve required suppression or legal-hold records, revoke integrations, delete or anonymize active stores, and expire backups on the approved schedule.
The customer-facing workflow and production deletion rehearsal are not complete. This document does not claim otherwise and cannot be approved for launch until UX-12 and the backup controls close.
Export
A verified export must use a portable documented format, contain only the requesting tenant's data, exclude secrets and other tenants, be encrypted in transit and at rest, expire promptly, and produce an audit record.
There is no launch-ready customer export route in the current candidate. Contractual commitments must reflect that state until implementation and two-tenant testing pass.
Requests and identity verification
Requests go to Privacy contact pending legal approval. Taicho will verify identity and authority, record scope and deadlines, coordinate with the customer controller where applicable, and document completion or a lawful exception.