Your account.
Your choice.

Delete with your saved code

Use the account deletion code you saved from Tavli’s Settings screen. You do not need the app or a sign-in session to use it here.

This permanently removes the matching guest profile, sessions, shared online tables, and action history. Other players lose access to the shared tables that are removed. It cannot erase local saves from your devices.

A deletion code begins with tavli-delete-. Use your most recent code. Never enter a sign-in credential or nearby pairing code.

The code is sent directly to the game service. This page does not save it, place it in a URL, or include analytics.

Save a code before uninstalling

1. Open Settings in Tavli after playing online.
2. Choose Get account deletion code.
3. Copy it to a private place you can access without the app.

Anyone holding that code can delete the matching account; it cannot be used to sign in or read games. A replacement code invalidates the old one. The code remains valid while its account is retained unless replaced or used.

Delete directly in Tavli

1. Open Settings.
2. Choose Delete account & saved games.
3. Review the effect, then confirm Delete my account and saved games.
4. Keep the app connected until it confirms completion. If the connection fails, reconnect and retry.

This option also removes this device’s saved matches. You do not need a deletion code or support request to use it.

What remains

A minimal deletion record keeps the random account identifier and deletion time, so restoring a backup cannot restore the deleted profile. It contains no display name, game history, or sign-in credential. Current code hashes and deletion records are kept independently of game-database backups.

• Local saves remain until you clear or replace them, or your device removes the app’s data.
• Tavli’s existing ads-off choice and ad-limit history are stored separately on your device. The history keeps counters and timestamps plus up to 64 recent completion references; ad-attempt times leave the rolling-hour window when the history is next checked. Clearing a saved match or deleting a guest account does not reset these settings. The current app does not ask a custom age question. Removing the app’s local data removes Tavli’s local records.
• Online sign-in sessions expire after 30 days.
• If you enable game notifications, the service keeps an encrypted push-routing token, its installation and guest-profile binding, your preference, and recent activity times. Registrations expire after 30 days without refresh. Event and delivery records are removed seven days after the event expires; delivered notification copies can remain on your device until dismissed. Notification preferences and the installation proof stay in secure device storage until account deletion or removal of that storage by the operating system.
• Turning off Game updates removes the installation’s server registration and pending deliveries when the device can connect. Deleting the online account removes its notification registrations, events, and delivery records. Already-submitted pushes cannot be recalled from Apple or Google. Copies in game backups follow the backup retention below; account-deletion records prevent their reactivation after a restore.
• Inactive public waiting rooms are removed after 15 minutes, other inactive waiting rooms after 24 hours, and other rooms after 30 days without an action. Cleanup runs hourly while the service is available.
• Expired guest profiles are removed once they have no remaining sessions or rooms.
• Application container logs use size-based rotation: a 10 MiB limit per file and up to three files. This is a size limit, not a fixed number of days. Application logging does not include sign-in credentials or request bodies. The app’s proxy access logging is disabled. Proxy error logs rotate daily and retain 14 archives; errors may include network addresses and request paths, but the proxy is not configured to record POST request bodies.
• Game backups run daily and retain the seven most recent successful snapshots on the same VPS. This is a snapshot count, not a promise of seven calendar days. The independent deletion ledger is copied every five minutes, retaining two complete copies on the same VPS. A disruption can prevent a scheduled copy. These are not offsite backups, and no encryption-at-rest guarantee is made here.
• The independent deletion record is applied before a restored game database can serve requests. The backup schedule does not guarantee recovery without loss of the latest changes.
• Minimal deletion records are retained indefinitely by default. They hold a random account identifier and deletion time, with no display name, sign-in credential, or game history.
• Support correspondence is deleted from the publisher’s mailbox 90 days after the request is resolved. This describes the publisher’s handling of the mailbox, not a guarantee about the mail provider’s own backup deletion schedule.
• The periods above describe Tavli’s records, not Apple’s or Google’s own service retention. Providers apply their own retention and deletion rules, including security and legal requirements. Deleting a Tavli account does not delete provider-held records. See Google’s data retention policy and Apple’s privacy policy.

Lost both the app and the code?

Guest accounts have no email or password login. A display name is not proof of ownership. If you still have the original app session, delete there or generate a new code.

Otherwise, contact [email protected] for help understanding the account’s expiry and retention. Support cannot safely delete an account based only on a shared display name. Do not send your code or sign-in credential by email.

Sessions expire after 30 days. Expired guest profiles are removed once no sessions or rooms remain. Read the privacy policy for more about room retention and the information Tavli uses.