Skip to content

Limits & Quotas

Data retention

Overview

Retention determines how long data remains available and when it is deleted. Confirm the schedule that applies to your purchased service and deployment; this page does not establish a default retention period or promise a self-service legal-hold feature.

Treat test inputs, source snapshots, execution logs, screenshots, reports, audit evidence, support records, and backups as distinct data categories. Their purposes, owners, storage locations, and deletion processes may differ.

Step-by-step procedure

Create a retention inventory

For each category, record its purpose, sensitivity, storage location, responsible owner, required retention, and the source of that requirement. Include copies exported to issue trackers, chat tools, object storage, and model providers.

Confirm the applicable schedule

Review the agreement, DPA, security documentation, and configuration available for your deployment. Ask the account team to clarify active data, backup expiry, account closure, and deletion verification before relying on a particular period.

Prepare authorized exports

Where export is supported, verify the format, scope, permissions, and completeness using a small sample. Protect the destination and preserve the context needed to interpret evidence after the source system changes.

Handle exceptions and deletion

Coordinate legal preservation duties with your legal team and Zof through the applicable process. Record the scope and duration of any agreed exception. Verify deletion in each system you control; deleting a source record does not necessarily remove exported copies.

Key concepts

Retention schedule
A documented rule defining how long a data category is kept and the event from which the period is measured.
Legal preservation
A legal duty to preserve relevant information. Confirm the actual mechanism and responsibilities; it is not proof that a product has a legal-hold control.
Backup expiry
Removal according to the backup lifecycle, which may differ from deletion in an active service.

Best practices

  • Collect only the evidence needed for the stated purpose.
  • Review retained artifacts for credentials and personal data before exporting them.
  • Assign owners to retention exceptions and periodically reassess whether they remain necessary.

Common issues

Evidence no longer available
Check the agreed retention schedule, source environment, permissions, and any authorized archive. Ask support about the specific record; do not assume expired data can be recovered.
Copies survive source deletion
Review exports, notifications, integrations, and customer-managed backups against their own retention rules.

Was this page helpful?