Delete account and journey data
Delete your account and journey data in the app, or request deletion by email without reinstalling it.
Effective: October 18, 2026
How to request deletion
Include the game name and your deletion request. Support will explain the minimum information needed to verify ownership. A name or email alone does not identify an anonymous account or authorize deletion of someone else’s account. Contact us even if you can no longer access the device.
The button opens your mail app. It does not send a message or delete anything automatically.
Delete in the app
Use “Delete account and journey data” in the app to review the current account’s scope and confirm your request. During processing, saving to that account and automatic creation of a new account are blocked. Completion is not reported before processing finishes. If you cannot use the app or processing fails, contact the email address above.
Data included
Deletion covers the account’s server progress, best times and ghosts, stamps and completion history, owned and equipped item links, leaderboard records and public tag, and Firebase anonymous account. Once the app confirms removal of server game data, unsent local runs for that account are cleared, even if Firebase account cleanup is still pending. A new journey does not restore deleted progress.
If the account has a linked billing identifier, we request deletion of its RevenueCat customer information. RevenueCat processes that request asynchronously. Deleting a game account is not a refund or deletion of Apple’s or Google’s transaction records, and restoring purchases does not restore deleted game progress. Pictures already saved or shared are not recalled.
Status and limited retained data
After server game data is removed, processing remains pending until any linked RevenueCat customer deletion request is accepted and Firebase account deletion is confirmed. Failed stages are retried; account and billing identifiers needed for this work remain until then. RevenueCat erasure is asynchronous, so the app’s completed status does not mean immediate erasure of every provider copy. After Firebase deletion, raw identifiers are erased, leaving hashed identifiers, receipt hash, status, and timestamps temporarily.
The receipt can check status for 24 hours after the request; this is not a guaranteed deletion time. Old authentication tokens are blocked for 70 minutes after completion. After both periods, the next deletion-related request cleans up the completed row. Unfinished jobs are not discarded merely because time has passed. The on-device deletion status and receipt are removed when you explicitly start a new journey after completion.
Game data is kept until a deletion request; support inquiries are kept no longer than 90 days after resolution. Firebase keeps IP logs for a few weeks and removes other authentication information from its live and backup systems within 180 days after user deletion is initiated. D1’s current automatic recovery window is 7 days, not a deadline for physical erasure of every copy. Separate pre-release operational backups are manually discarded within 30 days after creation, and deletion requests must be reapplied before restoration to service. See the Privacy Policy for providers and retention details.
More about data handling
For service providers and retention, see the Privacy Policy.