Data deletion

Deleting PicBunch data: working draft.

The current studio requires password confirmation to delete an event or account. A release policy still needs to explain every deletion path, verification step, timeline, and backup exception.

Event and account deletion in the current product

A signed-in host must confirm the event name and current password to delete one event, or confirm account deletion with their password, from the studio. Access closes first; background maintenance verifies account removal and then purges the related database records, media, and exports. The release checklist must verify partial-failure recovery and any limited operational or backup retention.

Requests that still need a published route

A monitored support route for account or privacy requests that cannot use the signed-in control, including identity verification.
Requests about a specific guest photo or event.
Legal holds, fraud and security records, billing records, backups, and other justified exceptions.

Before this page can be final

Publish a monitored request contact and a clear verification process.
Confirm deletion and backup timelines against the real production systems.
Align the product controls, privacy notice, terms, retention jobs, and support playbook.