Data Retention Policy

Applies to users, intake, messages, generated files, deliverables, audit/security events, payment metadata, logs, metrics, uploads, backups, synthetic reports, and launch evidence.

Draft retention defaults for accounts, projects, generated files, audit events, logs, backups, launch evidence, deletion requests, and legal holds.

Account, project, message, deliverable, payment, audit, and security event metadata should be retained during beta unless an approved deletion or legal hold procedure applies.

Operational logs and metrics should be retained for short operational windows, while release evidence and backup artifacts should be retained according to launch governance needs.

Deletion requests should be logged and reviewed. If deletion is supported later, it must handle project records, audit events, backups, payment metadata, and legal hold exceptions safely.

Legal hold is currently a documented placeholder and must be operationalized before public production.

Beta defaults should preserve audit/payment/security evidence long enough for support and release review.

Do not implement irreversible deletion until restore, audit, legal hold, and backup behavior are reviewed.

Backups and launch evidence may outlive primary records under operational policy.

Irreversible deletion is not implemented.

Legal hold process is a placeholder.

Retention periods need legal approval.