How to request deletion
To delete your account, use Settings → Account Info → Delete Account in the game while signed in to the account concerned. You do not need to send your account ID separately when using this feature. If you cannot access the game, you can request deletion at [email protected]. Include the game name and your account ID if you know it. We may request additional information to identify the account and verify ownership; deletion may not be possible if we cannot verify these. Never send passwords, sign-in codes, authentication tokens or full payment-card details.
Your choices and deletion
The account-deletion process requests deletion of the PlayFab account and cloud data, removes the associated Challenge profile/run data, and invalidates stored Apple sessions. Some provider-side operations complete asynchronously. Deleting a game account does not itself refund purchases or erase the store’s own transaction records.
The in-app account-deletion function does not immediately erase separately stored Azure analytics. Those records otherwise follow the retention periods above. Contact us to request deletion of related personal data; we will verify the request and explain the scope and timing of processing, including any applicable retention exception.
Retention
These are expiry targets for the custom Azure records, not a promise that every copy is erased at the exact expiry time. Scheduled cleanup can be delayed. Firebase, platform authentication, store records and infrastructure logs have separate retention settings and provider policies. Minimal deletion/security markers may remain to prevent duplicate processing or account reactivation.
- Account, cloud-save and Challenge data: retained to provide these features until account deletion is processed, subject to the exceptions below.
- Custom Azure presence and request-limit records: a 1-day expiry target.
- Custom Azure sales detail: a 2-day expiry target; transaction deduplication records: 60 days.
- Custom Azure gameplay analytics, account-level daily activity and buyer-level records: a 90-day expiry target.
- Custom Azure account analytics summaries: 2 years after the last observation. These summaries use hashed account identifiers and are not treated as fully anonymous.
- Sales daily aggregates without individual account identifiers: approximately 2 years.
Changes and contact
Depending on applicable law, you may request access, correction, deletion or restriction of processing, or withdraw consent where processing relies on consent. Contact [email protected]. Signing out does not by itself stop installation-based analytics, and opening this policy is not consent to data collection.
We update this page when our practices change and revise the date above. Where required, we provide additional notice or obtain consent. For privacy questions and requests, contact Brilbox at [email protected].