Cleanup
What Standard removes after a task, what it keeps, and when cleanup counts as complete.
What Standard removes after a task, what it keeps, and when cleanup counts as complete.
Standard separates the result you keep from the temporary resources used to produce it.
Cleanup covers the task's temporary workload state and resources, including the working state and decrypted inputs it held. Completion does not establish cleanup; the separate cleanup status records whether the required removal checks passed. It does not imply a dedicated machine was destroyed. Temporary permissions issued for the task, such as its key-access grant, expire on their own schedule.
| Kept | By whom, and under which rules |
|---|---|
| Original inputs | The owners, in their own encrypted storage. Cleanup never deletes them. |
| Permitted results | Their recipients, under the applicable retention rules. |
| Execution evidence | Authorized recipients, so they and their auditors can re-verify. |
| Account, billing and operational records | Standard, managed separately from task contents. |
Cleanup has its own status, separate from the task's result:
Treat cleanup as complete only when its status is confirmed. Pending cleanup is not confirmed cleanup.
Cleanup cannot recall copies of a result that recipients already hold. It also does not prove that every physical trace in memory or backups was erased, and it is never reported as proof of that.
A Space can be reused for later tasks. A later task must use its own authorized inputs; reusing a Space does not authorize access to an earlier task's private working state.