Room for trust.

What Tavli uses

Tavli is free to play, with computer, same-device, Wi-Fi, Bluetooth, and online modes and occasional advertising through Google AdMob. Computer and same-device games do not require an online account. There are no in-app purchases, chat, or real-money gambling.

Starting with version 1.0.2, Tavli includes optional Firebase Analytics and Firebase Remote Config on iOS and Android. Earlier versions may not include these services or the Usage analytics setting.

Local preferences and saved matches

Your chosen name, language preference, settings, saved game, and scores stay on your device so you can resume. A host can save a nearby table locally.

Optional usage analytics

If you enable Usage analytics, Firebase receives screen and feature interactions, gameplay measurements, an app-instance identifier, app/device information, and bounded diagnostic categories to improve gameplay and reliability. Names, online account identifiers, credentials, table or deletion codes, full board snapshots, and raw error messages are excluded.

App configuration

Firebase Remote Config processes a Firebase installation identifier, app/device information, and network connection information to select and deliver public app settings. This service runs on iOS and Android even when optional Usage analytics is off. Valid settings are cached on your device.

Ad privacy and limits

Ad-attempt times, counters, limited recent-match references, and an existing ads-off choice from an earlier version are stored on your device to decide whether ads are allowed and prevent repeated interruptions. Tavli does not collect your date of birth or send these records to the ad service.

Online guest profile

A chosen display name, random account identifier, and sign-in session let you join and recover online games. Your opponent receives your display name and game information.

Deletion codes and records

If you request a deletion code, only its hash and random account identifier are stored in a database kept separately from game backups. Replacing a code replaces its hash. After deletion, a minimal record retains the random identifier and deletion time so restoring a backup cannot restore the account.

Online game records

Board positions, dice, moves, scores, room membership, and timestamps keep games consistent and allow reconnection. Saved action results prevent the same action from taking effect twice.

Optional game notifications

If you enable Game updates, a device push token, random installation identifier, registration proof, operating-system platform, permission state, preference, and recent activity times route online table alerts and avoid interrupting play. The server associates the installation with your guest profile and encrypts the routing token at rest. The proof stays in secure device storage; the server stores its hash.

Nearby play

Your confirmed peer receives the names and game information needed to play. Nearby game traffic goes between the two devices rather than through the online game service.

Connection information

The game service uses source network addresses and request counters to operate and prevent abuse. Hosting and support services may keep operational records as described below.

Support requests

If you contact support, your email address and the information you choose to send are used to answer your request.

Why information is processed

The online profile and game records are used to provide the games and reconnection features you request. Where data protection law requires a legal basis, this processing is necessary to perform the agreement to provide that service. Connection safeguards and limited diagnostic records support the legitimate interests of keeping the service reliable and preventing misuse. Support correspondence is used to answer your request, and information may also be processed when needed to comply with an applicable legal obligation.

Advertising helps fund the free game. Its processing supports ad delivery, measurement, fraud prevention, diagnostics, and privacy-choice management. Where consent is required for device storage, identifiers, or advertising processing, the applicable choices are requested before those uses. Permission to play online is not consent to tracking.

Optional usage analytics measures app use with your consent to improve gameplay and reliability. Remote Config supports app functionality by delivering configuration settings; its installation-identifier processing is separate from the optional analytics choice.

Optional usage analytics and app configuration

Your usage analytics choice

Usage analytics is off by default. Enable or disable it in Settings → Usage analytics. Declining it leaves gameplay available. After you opt in, Firebase Analytics uses an app-instance identifier to measure sessions, screen views, feature and settings interactions, gameplay, recovery, and diagnostic categories. Gameplay measurements may include mode, computer difficulty, dice, checker moves, cube decisions, outcomes, scores, and durations. Tavli does not attach your display name, online account identifier, credentials, invitation or deletion codes, URLs, raw errors, or complete board snapshots.

Tavli disables Analytics advertising storage, advertising user data, ad personalization, and advertising-identifier collection. Usage analytics consent is separate from notification permission, AdMob privacy choices, and Apple tracking permission. Remote settings cannot enable Analytics without your local opt-in.

Turning usage analytics off stops future app analytics and resets the local Analytics identifier and pending Analytics data. It does not erase events already received by Google. Account deletion also resets the local Analytics identifier, but does not identify or remove historical Analytics events held by Google. Google applies its own processing and retention rules; contact the publisher about requests relating to those records.

Remote Config and cached settings

Firebase Remote Config runs on iOS and Android even when Usage analytics is off. The Firebase SDK uses a Firebase installation identifier, app/device information, and network connection information to choose and retrieve public configuration values for app functionality. The installation identifier is separate from your online Tavli account and from the optional Analytics identifier. These requests can occur without an online game account or notification permission.

Settings can control new-match defaults, feature availability, turn timing, and stricter ad limits. Tavli starts with the latest valid cached settings, or built-in defaults on a new installation, and retains valid settings when fetching fails. Remote configuration cannot override your privacy choices or the rules of a match already in progress, and cannot weaken the app’s advertising safeguards.

The local configuration cache remains until replaced or the app’s local data is removed. Turning off usage analytics or deleting a Tavli guest account does not delete Firebase’s Remote Config installation identifier or provider-held configuration records. Firebase describes its installation-identifier retention and deletion in its privacy information.

Firebase is operated by Google and may process information outside the game server’s country. See Firebase privacy and security information, Google’s privacy policy, and Google’s data retention policy.

Advertising and your privacy

When ads can appear

An ad can appear after a newly completed full computer, same-device, or online match, before the result controls appear. There are no ads during turns, between games within a multi-point match, when resuming, or in Wi-Fi and Bluetooth play. The first eligible completed match is free of ads. Later attempts are at least ten minutes apart and at least ten minutes after the local ad history begins, with a maximum of three attempts in a rolling hour. If an ad is unavailable or the result cannot be saved, that opportunity is skipped.

Privacy setup and previous preferences

The current app opens directly in the lobby and does not ask a custom age question. Applicable regional ad-privacy choices appear outside gameplay. If an earlier version saved an ads-off choice, Tavli continues to honor it. Every game mode remains available regardless of privacy choices.

Privacy setup can contact Google before any ad is shown, including while the first match is still free of ads. Changing consent affects future requests and cannot undo information already collected or unload an advertising SDK initialized earlier in the session.

Non-personalized ads and Google’s information use

Tavli requests non-personalized ads (NPA) and disables publisher ad personalization through Google’s Publisher Privacy Treatment (PPT) setting. It also disables Google’s publisher first-party identifier. These settings limit personalization; they do not mean no data is processed. Non-personalized ads can use context, such as approximate location, and identifiers may still be used for frequency limits, reporting, and fraud prevention where permitted. Google explains non-personalized ads and Publisher Privacy Treatment.

Google Mobile Ads may process your IP address and approximate location, device or app identifiers, ads viewed and interacted with, app interactions, crash reports, and performance and diagnostic information. Google uses this information for advertising, measurement, analytics, and service operation. Tavli does not attach your display name, guest-account identifier, credentials, room codes, dice, moves, or scores to ad requests. Optional Firebase usage analytics is described separately above. See Google’s advertising data disclosure.

Google’s User Messaging Platform (UMP) manages applicable privacy messages and choices. It processes consent information and technical information, including approximate location, interactions, and performance data, to support those features. Google’s privacy policy describes its information use and controls.

Regional choices and optional iOS tracking permission

Players are shown applicable regional privacy messages through UMP at the lobby or settings, outside gameplay. Open Settings → Ad privacy choices to review the available options, change consent, or exercise an available regional opt-out. Refusal does not block gameplay; depending on the applicable choices, Google may still permit limited ads. Tavli checks the SDK’s ad-serving permission before initializing advertising. That permission is not permission to track.

On iPhone and iPad, Tavli may separately ask through Apple’s App Tracking Transparency prompt whether your advertising identifier may be used for cross-company advertising measurement. This is optional. If you allow it, that use remains subject to your regional privacy choices; all Tavli ad requests still remain non-personalized. If you deny or restrict tracking, Google does not receive the iOS advertising identifier in ad requests. Other disclosed network, advertising, and diagnostic processing can still occur. See Google’s guidance on ads and the iOS advertising identifier.

To change Apple’s permission, open your device’s Settings → Privacy & Security → Tracking. Withdrawing consent affects future processing and does not undo processing that already occurred. All game modes remain available regardless of your ad privacy or Apple tracking choices.

Optional game notifications

Turn on Settings → Game updates, or choose Notify me when ready at an online table, to request system notification permission. Alerts can tell you that your opponent joined or that your online table needs a move or a response to a double. There are no marketing notifications in this version. Declining notifications leaves every game mode available. Notification permission is separate from advertising consent and Apple tracking permission.

The notification service is used on your request and, where required, with your consent. Recent foreground activity and the table you are viewing are sent to Tavli while notifications are enabled so the service can suppress distracting alerts. The app suppresses foreground system banners and does not automatically switch an active game when you tap a notification.

Tavli’s server sends the device-routing token, a generic alert, and a random event reference directly to Apple Push Notification service on iPhone/iPad or Firebase Cloud Messaging on Android. Tavli does not include names, pairing codes, account credentials, board positions, moves, or scores in push payloads. The app checks the current signed-in profile before opening a notified table. Firebase also processes installation identifiers needed for Android delivery. Enabling notifications does not enable optional usage analytics.

Turn off Game updates in Tavli or use the device’s notification settings to stop alerts. If Tavli is offline, server opt-out is retried when you reconnect. An alert already submitted to a provider may still arrive; system settings can stop its presentation immediately. Alerts are best-effort and can expire or arrive late.

Apple and Google process notification information under their service terms and may process it outside the game server’s country. See Apple privacy, and Firebase privacy and security.

Permissions and security

Wi-Fi and Bluetooth permissions are used to discover and connect to another player. Some Android versions may request a location-related permission for nearby discovery; the game does not use geographic coordinates. The app does not request your contacts, microphone, or photo library.

The native app keeps its online sign-in credential in operating-system secure storage. Online traffic uses HTTPS in release builds. Choose a display name you are comfortable sharing with your opponent. Do not share your sign-in credential or account deletion code.

Storage and service providers

Baris Ceviz publishes Tavli and can be contacted at [email protected].

The game service uses a Contabo VPS. The publisher identifies its hosting location as France; game backups are kept on the same VPS. Game data and deletion records use separate durable storage.

Requests pass through Cloudflare’s global edge network before reaching the game service. Edge processing is not limited to the game server’s country.

Incoming support mail for [email protected] is processed by Google. Google also provides the app’s advertising, consent, optional Analytics, and Remote Config services, which communicate separately from the game service. Providers receive the information needed for their respective services. Cloudflare and Google may process information in countries other than the game server’s location, under their applicable service terms and privacy policies.

More about provider processing: Cloudflare privacy policy and Google privacy policy.

How long information stays

• 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.

Your choices

You can clear saved local games and delete your guest account in Settings. Account deletion removes the online profile, sessions, rooms involving that profile, saved action records, and associated notification registrations and delivery records from the active service. Opponents lose access to those removed rooms.

The account deletion page explains deletion in the app and how to submit a saved deletion code without the app. Web deletion cannot erase local saves from your devices.

Deleting a Tavli guest account or local match does not delete Google’s advertising or consent records, revoke Apple’s tracking permission, or reset your device’s ad privacy and frequency-limit settings. Use the ad privacy and device controls above and Google’s privacy controls for the information Google holds.

For questions about your information, or to request access, correction, or deletion, contact [email protected]. We may need to verify that a request concerns your account before acting. Do not send a sign-in credential, deletion code, or pairing code by email.

Depending on the law that applies to you, you may also have rights to restrict processing, object to processing, receive a portable copy of your information, and complain to a data protection authority. Contact the privacy address above to exercise an applicable right.