Choose how PD Object Storage handles data after service termination. Revoking customer access and later deleting retained buckets are separate operations.

Review the intended retention policy

1. Open PD Object Storage → Settings.
2. Review Keep data after termination and the selected period.
3. Review Purging terminated data and deliberately choose Manual or Automatic.
4. Save before the intended future termination.
5. For an already terminated service, inspect its actual entry under Retention, including eligibility and approval state.

A policy change is not proof that an existing entry’s recorded deadline changed. Manual mode allows staff to review eligible deletion. Automatic mode can proceed without that later per-service decision. If an immediately eligible policy is configured, it provides no waiting window for recovery.

Distinguish retention controls

Termination revokes the service credentials while retaining storage for the configured process. Approve purge authorises eligible deletion. Hold stops further approval-based progress. The expanded Purge now action is a separate destructive operation with typed bucket confirmation.

Hold cannot undo deletion already performed. Retention is not an independent backup and cannot recover objects removed by an application, lifecycle expiry or an earlier purge. Keep an independently verified recovery copy where needed.

Protect a recovery decision

For an accidental termination, put the pending purge on hold, check whether deletion began, and follow original-service recovery. Do not approve a purge to investigate a connection problem.

Keep the original service, backend, retention state and action time when checking an unclear result. A saved policy alone does not prove that recovery remains possible or that deletion completed.

See the PD Object Storage WHMCS guide for related tasks, or explore PD Object Storage.