Choose what should happen to storage after a service is terminated. PD DigitalOcean Spaces separates revoking service access from later deletion of retained buckets and objects.

Set the policy before termination

1. Open PD DigitalOcean Spaces → Settings.
2. Review Keep data after termination and select the intended retention period.
3. Review Purging terminated data and choose Manual or Automatic deliberately.
4. Save and review the actual service’s entry under Retention when it is terminated.
5. Check its eligibility time and approval state rather than relying only on the current global setting.

Manual approval lets staff review deletion after the window elapses. Automatic purging can make eligible data proceed without that later staff decision. A zero-day retention choice makes data eligible immediately; it is not a recovery window.

Understand access and deletion separately

Termination revokes the service’s matching keys while retaining its storage for the configured process. Retention is not an independent backup and does not recover objects already deleted by an application, cleanup rule or earlier purge.

On Retention, Approve purge authorises eligible deletion, while Hold stops further approval-based progress. The expanded Purge now action is a separate destructive operation with typed bucket confirmation; do not use it to investigate access or provisioning.

Protect a recovery decision

For a cancellation mistake, put the relevant purge on hold and establish whether deletion has already begun. Hold cannot undo earlier deletion. Follow the original-service recovery guide before creating another order or changing credentials.

Keep an independent verified copy of required data and review retained entries regularly. A saved policy alone is not proof of a complete backup or a successful purge.

See the PD DigitalOcean Spaces Blesta guide for related tasks, or explore the module.