Right to erasure is one DELETE, and no bucket keeps a copy

A customer invokes their right to be forgotten. On a shared-database SaaS this is a forty-table cascade, a ticket to check the S3 lifecycle rules, and a quiet hope that the managed database's automated backups age out on schedule.

Here the customer was a container. Their files, their SQLite database, their logs, their snapshots: all on the disk of the server you rent. You delete the container. The snapshots were copy-on-write deltas on that same disk, so they go with it. There is no provider-held backup to wait on, because Hoody never held one; snapshots live on your server.

You reply to the request with a timestamp and the container ID that no longer resolves.