Currently, when you delete a site in Ploi, any existing backups of that site are left behind without any mention of them during the deletion flow. This creates two problems:

Why this is useful:

Orphaned backups consume storage silently. Backups of deleted sites keep sitting on the backup destination (S3, DigitalOcean Spaces, custom storage, etc.), costing money and cluttering storage with data that belongs to a site that no longer exists. Most users won't remember to clean these up manually — or even realize they're still there. Data hygiene & compliance (GDPR). When a customer offboards and their site is removed, the expectation is often that all their data is removed — including backups. Right now it's easy to unknowingly retain personal data in backups after a site deletion, which is a real compliance risk for agencies and hosting providers. Prevents confusion later. Orphaned backups without a linked site are harder to identify, manage, or restore months down the line.

Proposed solution:

When deleting a site, if backups exist for that site, the deletion confirmation dialog should:

Clearly state that X backups exist for this site (with total size if possible) Offer an extra checkbox: "Also delete all backups associated with this site" (unchecked by default for safety) If the checkbox is left unchecked, explicitly confirm: "Backups will be retained and must be removed manually" — so the user makes a conscious, informed choice either way

Why this needs to be clear and prominent:

The key issue is not just the ability to delete backups — it's that the user must be explicitly made aware during deletion that backups exist. Silent retention is the worst outcome: users assume everything is gone, while data and storage costs linger. A deletion flow should never leave data behind without telling the user. Making this explicit protects users from both accidental data retention (compliance/cost) and accidental data loss (if deletion of backups were silent instead), which is exactly why an opt-in checkbox with a clear message is the right approach.