Account Deletion

How to Request Deletion

Ballroom Booking users can request account deletion through this public page. In-app self-service deletion is planned for the mobile app, but irreversible backend deletion is not enabled until the final retention model and account ownership rules are approved.

Request channel: dance@foxballroom.com Include the email address used for Ballroom Booking, the participating studio name, and a clear request to delete or deidentify your account information. Do not send passwords, complete card numbers, or card security codes.

What May Be Deleted

• Ballroom Booking login credentials and active sessions, after identity verification and workflow implementation.
• Direct account profile information that is no longer required.
• Push-notification tokens and preferences.
• User-owned profile photos and support attachments that are not needed for an active dispute, security matter, or legal obligation.
• OAuth connections and platform-issued refresh tokens, once a supported revocation flow exists.
• Other personal information not required for the retention purposes described below.

What May Be Retained

• Payment, tax, accounting, invoice, audit, refund, chargeback, and dispute records.
• Fraud-prevention, security, abuse-investigation, and legal-claims records.
• Records needed to enforce agreements and protect legal rights.
• A participating studio's legitimate or legal need to maintain attendance, service, transaction, waiver, or client-history records.
• Backup copies until they age out through normal backup rotation.

Processing Window

• Active-system deletion should generally be completed within 30 days after a verified request once the approved workflow exists.
• Encrypted backup copies should generally age out within 90 days through normal backup rotation.
• Payment, tax, invoice, and accounting records may be retained for the period required by law, commonly up to seven years.
• Security logs may be retained up to 12 months unless needed for an incident.

Studio-Managed Records

Deleting a Ballroom Booking login does not automatically require a participating studio to delete every record that the studio independently controls or is legally required to retain. Users may also contact the studio about studio-controlled records. Ballroom Booking will reasonably assist the studio where required.

Recommended V1 Implementation Plan

• Immediate app-store acceptable flow: public request page, support intake, identity verification, manual review, session revocation where supported, and documented retained-record categories.
• Later self-service workflow: in-app Account > Privacy & Security > Delete Account with recent-auth challenge, explicit confirmation, deletion-request status, cancellation window if implemented, and completion notice.
• Retention model: introduce an AccountDeletionRequest record, audit trail, retained-record reason codes, deidentification markers, S3 object review, provider-token revocation, and tenant-scoped processing.
• Test plan: public route accessibility, authenticated deletion request creation, tenant isolation, idempotency, retry behavior, retained payment/history records, OAuth/session revocation, and profile-photo/support-attachment handling.