A practical starting point for how long operational records, workspace data, and support traces should be retained and reviewed.
This page is approved for publication as the current retention and deletion policy summary. It should be updated if operational, tax, finance, backup, or support retention requirements materially change.
Last updated: May 15, 2026
Jobs, bookings, customer communication history, billing records, audit trails, and support records may need different retention periods based on business, tax, and service requirements.
MyTitan surfaces the operational records, but the operator still owns the final retention policy and deletion decisions.
The operator should keep the published retention windows for customer data, audit history, backups, and finance records aligned with real operating requirements.
If refunded or reversed commercial events affect allowance or billing state, the product reflects that operational truth instead of silently masking it.
