This page explains how to delete your NumberChallenge account and the personal data attached to it. There are two ways: delete it yourself from inside the app, or request it by e-mail. Both do the same thing.
Deletion cannot be undone. Your device continues with a fresh, empty guest profile. If a match is still in progress you have to finish it first — that is so your opponent's match is not abandoned mid-game.
If you cannot reach the app (lost phone, app uninstalled), send your request to ikarhan@gmail.com. So that we can find your account, include at least one of:
@username.Requests are completed within 30 days at the latest, and you are notified once it is done (KVKK art. 11/13, GDPR art. 17).
Deleting your account removes your identity and every personal record tied to it. The records of matches you played are also part of your opponents' game history, so they are not removed entirely: your name in them is replaced with "Silinmiş oyuncu" (deleted player) and the record can no longer be linked to you.
| Deleted | Retained (anonymised) |
|---|---|
Your sign-in (e-mail, password, Google link, sessions) · your display name and @username ·
your rating, league and statistics · achievements · daily streak and hint tokens ·
notification registration (device token, language, time zone) · purchase records ·
error and usage events · your secret numbers from matches · rooms you created ·
your season results
|
The played matches themselves (date, mode, moves, outcome) — in your opponent's game history, with "Silinmiş oyuncu" where your name was |
Copies in routine server backups disappear on their own within the backup cycle (35 days at the latest).
If you bought the ad-free version, deleting your account does not refund it — refunds are handled by Google Play. However, because your purchase record is deleted too, you can restore the purchase on a new profile using the same Google Play account.
No. Uninstalling only removes the local data on your device; the account record on the server stays. Use one of the two paths above to have the server-side data deleted.