Data deletion

1. In a build that contains the required control, open OneBeat and go to Profile → Delete account.
2. Follow the in-app confirmation and any direct website instructions shown by OneBeat. The website route is intended to explain the process; reading it does not submit a request.
3. OneBeat should verify the account holder, remove the data covered by the request, apply only necessary legal or security exceptions, and confirm completion.

The current build has no Delete account control and no website intake, so it cannot complete these steps yet. Do not send passwords, Clerk tokens, Spotify tokens, SSV query strings, or ad payloads through an unverified channel.

In the mobile app, Profile → Disconnect Spotify removes the OneBeat provider connection and stored Spotify token record, then clears the local Spotify App Remote session. It stops OneBeat from using that connection, but it does not delete your Clerk identity, gameplay, progression, leaderboard or reward history. It also does not delete your Spotify account or data that Spotify retains under Spotify's own policies.

• Clerk identity and the OneBeat account record.
• Convex profile, gameplay, progression, leaderboard and reward records.
• OneBeat Spotify connection and token records, plus local session cleanup.
• Advertising consent and account-linked reward records, subject to necessary fraud/security or legal retention.
• Gem balance, currency transactions and RevenueCat virtual-currency webhook records, subject to purchase replay, refund/revocation, accounting, legal or dispute retention.
• A deletion confirmation that explains any record retained by law or for security.

Spotify, Clerk, RevenueCat, Apple App Store, Google Play, Google Mobile Ads/UMP and hosting providers may retain information under their own roles and policies. OneBeat can remove the records it controls and can request provider action where the applicable agreement and law require it; disconnecting Spotify is not a command to erase a Spotify account.

OneBeat's current native gem packs are consumable purchases processed through RevenueCat and the applicable Apple App Store or Google Play environment. The OneBeat-side records include the Gem balance/ledger and the RevenueCat event ledger used to associate the authenticated Clerk app user ID with a virtual-currency event. Apple/Google and RevenueCat may retain product, receipt, store transaction, transaction-history and account records under their own policies.

If a store reports a completed purchase but the gems are not visible, do not purchase the pack again. Keep the account signed in and use the verified OneBeat purchase-support process when available, with the product and relevant store transaction reference only. The server checks the RevenueCat event ID and virtual-currency transaction ID so delayed or repeated webhook delivery cannot credit the same purchase twice.

Consumable gems are not restored by Apple's restore-purchases flow. Store refunds are decided by Apple or Google; a refund, revocation or chargeback may cause OneBeat to apply a negative server-ledger correction. If the purchased gems were already spent, the profile balance may temporarily go below zero. For Apple's product and restoration rules, see Apple's IAP overview and Apple's restore guidance.

To change consent choices, open OneBeat → Profile → Ad privacy choices when the UMP options form is available. This changes the advertising choice for the device or account context provided by the consent tool; it does not delete the OneBeat account or gameplay records.

• Add an easy-to-find Profile → Delete account initiation control.
• Provide a verified request intake and completion confirmation without requesting unnecessary credentials or identity documents.
• Delete or anonymize the account, gameplay, Spotify, advertising and device-linked records within the defined retention criteria.
• Record only the limited legal, security, fraud-prevention or dispute evidence that must remain.
• Test deletion across Clerk, Convex, provider connections and device-only state.

A completed process may retain limited records such as signed ad transaction IDs, RevenueCat event and virtual-currency transaction IDs, store transaction references, fraud-prevention evidence, security logs or dispute records when they are still necessary for replay prevention, refund/revocation reconciliation, accounting, a legal obligation or a security purpose. The retention criterion is the purpose and need for the record, not an invented fixed period. When that need ends, the record should be deleted or anonymized.