Workflow Data Retention
Definition. The policy governing how long a workflow retains its inputs, intermediate state, outputs and logs, balancing operational need against data protection obligations. Retention is a legal requirement and a cost driver, and it is often left undefined.
How it works. Define retention per data class, from the legal basis and the operational need. Retain what is needed for audit and dispute resolution, and delete the rest on a schedule. Ensure deletion covers derived copies, including logs, caches and backups. Document the policy and test that deletion actually occurs.
Example. A workflow retains every input document indefinitely, accumulating 4 TB and including personal data beyond its purpose. A retention policy sets 90 days for inputs, 7 years for decision records and 30 days for logs. Automated deletion reduces storage by 78 percent and removes personal data that had no basis for retention. A test confirms that deletion runs and that derived copies are included.
Use case. Retention policy is required for any workflow handling personal data, and it is a legal obligation in most jurisdictions. It is also a significant cost control.
Warnings. Retaining data indefinitely creates legal exposure and cost. Never delete data needed for an open dispute or audit. And never assume deletion from the primary store covers backups and caches.
Limitations. Retention requirements conflict, since audit may require long retention while data minimisation requires short. Deletion from backups is also technically difficult and often deferred.