1. Request account deletion
To request deletion of your Cadenza account and its associated personal data, email cadenzaclassicalmusic@gmail.com with the subject “Cadenza account deletion request”. You can use this route without installing or opening the app.
If possible, write from the email address associated with the account and state that you want the account and its associated data deleted. If you cannot access that address, explain that in your message. Do not send your password or any session credentials.
Emailing starts a request; it does not delete the account automatically. If the button does not open an email application, copy the address above into your email service.
Confirmation needed: the support team’s ability to verify and fulfil emailed requests, identity checks, response times and deletion timeframe. This page provides a request contact; it does not claim an unverified support process is operational.
2. Delete an account in the app
- Open Cadenza and sign in to the account you want to delete.
- Open Settings → Account.
- Choose Delete my account….
- Read the confirmation, type your account email address and confirm deletion.
The implemented flow requires an internet connection. Signing out, uninstalling the app or cancelling sync alone does not delete the account. If the deletion cannot be completed, contact the address above.
Confirmation needed: verify this flow in the released application and against the production backend before using this page for a store submission.
3. What the implemented deletion removes
The account deletion function removes account-related cloud library records, listening connections, user files in its listed storage locations and the Supabase authentication account. Account-owned preference records have deletion cascades.
The library can include saved recordings, works, ratings, notes, listening events, Pins, tags and collections. The process handles cloud records; the local-copy and shared-content exceptions below matter.
4. Local copies and shared content
Android: the implemented flow keeps the working library on your device and makes it available as a local library after cloud account deletion. Deleting the cloud account does not erase other device copies or backup files you have exported. Local library removal is a separate action in the application’s library/storage settings.
Web: the web library is cloud-based. Export first if you want to retain your own copy.
Shared content: source-page metadata and public Pin images have separate cache and cleanup lifecycles. An image can remain while it is referenced by another Pin or a live cache.
Confirmation needed: exactly what remains in production logs, security backups, shared caches or any legally required records, the reason for retention, and the applicable periods. A complete retention schedule has not yet been established for this draft.
5. Deletion and Forte
Ending Forte/sync access is separate from deleting an account. The reviewed application has no completed store or web billing integration. If paid subscriptions are introduced, this page must explain how account deletion affects billing and whether any separate action is required. No additional billing cancellation step is asserted here.
6. More information
See the draft Privacy Policy for information about Supabase, library data, Pins and Encore. The outstanding operational and retention details on this page must be confirmed before it is treated as final account deletion documentation.
A question about Cadenza?