Skip to content
Browse documentation
TrustReview1 min

Data lifecycle

Retention, export, deletion grace periods, legal holds, revocation, and evidence that may outlive workspace content.

On this page

  1. Prepare a removal request
  2. Retention and export
  3. Deletion boundary
  4. External review remains external

Prepare a removal request

Before removing a workspace or connection, identify the reports you need to retain and any legal retention requirements with your administrator. Download only exports that are available and authorized.

Removing a Costframe connection and revoking the cloud identity are separate operations; confirm both through their supported controls. Ask support about the applicable retention process rather than treating a missing screen as proof that every copy has been erased.

Retention and export

Workspace exports and retention jobs are governed operations with explicit availability and failure states. An export request is not the same as an available artifact.

Deletion boundary

A workspace deletion request starts a governed lifecycle with a grace period. Request acceptance does not prove that every retained record or external copy has been erased.

Review the confirmed deletion status and applicable retention terms; provider revocation and external exports remain separate responsibilities.

External review remains external

Customer-specific legal holds, statutory retention and backup restoration need an agreed process with the responsible administrator and privacy or legal owner. Product controls do not replace those obligations.

Find your next task

Browse setup, operation and recovery guides ↗Recover from a failed connection, audit or export ↗Ask a question with the safe support reference ↗

Related docs