Retention Policy
Retention Policy
Retention in Docsift is designed to distinguish between transient processing artifacts and the customer’s core finance workflow records.
Purpose
Effective date: 2026-03-23. This page summarizes how Docsift approaches retention across customer workflow records, processing artifacts, and security or audit evidence.
Operational queue artifacts
Docsift uses background processing jobs for extraction, retries, warnings, and maintenance. Succeeded or canceled queue artifacts may be deleted after the configured retention period to keep the operational system manageable.
The current runbook states that old processing jobs and related processing attempts can be cleaned up after the configured retention window, while core business records are not deleted by that maintenance routine alone.
Customer workflow records
Primary business records such as document headers, line items, attachments, exports, and approval or audit history are retained according to the customer relationship, customer instructions, legal obligations, and the operational capabilities of the service.
Because these records often support finance, accounting, and audit workflows, they are treated differently from transient background queue artifacts.
Security, support, and backups
Security logs, access events, support records, and limited backup materials may be retained for a reasonable period where needed to secure the service, investigate incidents, resolve disputes, or comply with law.
Deletion requests
Customers seeking deletion, export, or other lifecycle actions for service data should contact hello@docsift.com or use the applicable commercial support channel. Deletion timing may depend on legal obligations, backup cycles, and whether the requesting party has authority over the relevant data.