What changed
On August 17, 2026, Google Cloud announced that when a project is deleted, buckets with soft delete enabled are retained for a limited period instead of being immediately and permanently removed. If the deleted project is restored during that window, those buckets are restored to the state they were in when the project was deleted.
Why it matters
Project deletion has often been treated as a destructive boundary in recovery and teardown planning. This feature adds a recovery path—but also means retained storage can persist after project deletion, so operators need to understand the soft-delete window, storage charges and restoration dependencies.
Project recovery can now bring buckets back with it
Google's August 17 release notes explicitly describe the new behavior: soft-delete-enabled buckets survive project deletion for a limited time and are restored if the project is recovered within that period.
Soft delete remains time-bounded and billable
The bucket is not preserved forever. Recovery depends on the configured soft-delete retention window and Google's project-restoration timing. Retained data can continue to incur storage-related cost during the soft-delete period.
Recovery is not the same as full application restoration
Restoring the project and buckets does not automatically prove that every IAM binding, dependent service, application secret or external integration is back in a usable state. Disaster-recovery tests should include the whole dependency chain.
Teardown runbooks need clearer intent
Teams deleting projects to guarantee data destruction should verify whether soft delete is enabled and whether retained buckets contradict that intent. Teams deleting projects accidentally now have an additional recovery path to incorporate into incident response.