Delete account

Detailed game-log database entries use a one-week calendar-date cutoff, checked by a daily cleanup job. In normal operation this keeps roughly seven to eight days of records; scheduling or queue delays can postpone removal. Only the ten most recent profile-match-history entries remain as new results are recorded. Processed challenge-progress batches are scheduled for removal after seven days. These cleanup rules do not erase the separately stored full games, account statistics or wallet history.

Game authentication tokens currently expire after one week; password-reset and account-deletion confirmation links normally expire after 60 minutes. Expiry prevents further use but is not a promise that the underlying record is deleted at that moment. Likewise, marking an account inactive after 14 days does not delete the account or its collection.

Core account data, collection, progress and full match records are retained for as long as needed to maintain the account and provide the game, without a fixed expiry based solely on the record’s age. This does not override the shorter cleanup rules above, applicable erasure rights or the need to review whether inactive or obsolete records remain necessary. Confirmed account deletion removes the departing player’s identifiable match data.

We retain support correspondence, including received and sent messages and attachments under our control, for 12 months after the last substantive exchange, then delete it. If specific information is needed to handle an ongoing complaint or legal claim, or to comply with a legal obligation, we retain only that information for as long as necessary for that purpose.

Daily automatic database backups have a seven-day retention period. Deletion from the live application does not rewrite earlier backups: residual data remains until those backups expire. Laravel Cloud separately documents roughly eight-day retention for MySQL binary logs recording database changes, subject to earlier cleanup when storage is running low. Backup and recovery copies are for recovery and related security needs. If a backup is restored, previously completed erasures must be reapplied before the restored data returns to normal use.

Hosting application and access logs have up to one-day retention under our Laravel Cloud Starter configuration; a storage quota can shorten that period. Verbose bot file logging is disabled in the production configuration. Other diagnostic records, including failed-job records and diagnostic extracts, are kept only while needed to investigate and resolve the relevant fault or security incident, or for a specific legal obligation or claim. They are removed when that purpose ends; the weekly game-log cleanup does not remove all of these records. Providers may keep their own operational or delivery records under their service retention rules and legal obligations, separately from our support mailbox.

Confirmed website deletion removes the account, owned collections and progress, balances and wallet event records, authentication records, the departing player’s own match history and full games involving that player. Other players keep their own result summaries and statistics with the shared-game link removed. Related game-log database records, database queue payloads, cached game state and accessible structured bot diagnostic files are also cleaned. Delivered email, support correspondence, hosting logs and backup/recovery copies follow their separate lifecycles; they are not all erased immediately by that request. Any justified longer retention must be limited to the relevant data, purpose and duration.