Data Retention and Deletion

This page defines how long Tenali data is retained, who can trigger deletion, and how deletion requests are validated.

Data Classes

• Live call transcript fragments
• Post-call summaries and extracted action items
• Uploaded/connected source documents
• Integration sync metadata and audit events

Retention Model

• Workspace data follows contract-level retention policy.
• Customers may request shorter retention windows where contractually supported.
• Deletion policies apply to both active and archived records unless legal hold exists.

Deletion Paths

1. User-level delete for personally owned sources.
2. Admin-level delete for organization artifacts.
3. Support-assisted delete for scoped exceptional requests.

Verification Requirements

• Requestor identity must match authorized role.
• Deletion scope (records, time window, systems) must be explicit.
• Completion confirmation should include timestamp and request id.

Exceptions

• Legal hold or incident investigation obligations may pause immediate deletion.
• Required compliance logs can be retained separately as permitted by policy.